Bringing up a SQL Server in an isolated environment, but it was part of a Windows Failover Cluster and SQL Availability Group? It will likely be faster just to clean up the cluster configuration on the node and build a new single node failover cluster and single node availability group. (Note: you do not have to reinstall the OS, the solution is much simpler than that).
1. Start PowerShell under Administrator
2. Run “Import-Module FailoverClusters”
3. Run “clear-clusternode”
I may come back and walk through the whole process, such as first disable the Always On Availability Groups in SQL configuration manager and all that, but the above was the missing piece for me when the AGs and WFC would not respond or let me do anything through the GUIs.
Make sure that the “Distributed Transaction Coordinator” Service is running on both database and client. Also make sure you check “Network DTC Access”, “Allow Remote Client”, “Allow Inbound/Outbound” and “Enable TIP”.
To enable Network DTC Access for MS DTC transactions
Open the Component Services snap-in.
To open Component Services, click Start. In the search box, type dcomcnfg, and then press ENTER.
Expand the console tree to locate the DTC (for example, Local DTC) for which you want to enable Network MS DTC Access.
On the Action menu, click Properties.
Click the Security tab and make the following changes: In Security Settings, select the Network DTC Access check box.
In Transaction Manager Communication, select the Allow Inbound and Allow Outbound check boxes.
There may be many reasons you might need to generate a unique identifier or time stamp in your power apps. Some examples include:
To track user activity: Unique identifiers allow you to track and monitor user activity, including login information, form submissions, and other interactions.
To create custom reports: Unique identifiers enable you to generate custom reports, analyze user data, and easily identify trends and correlations.
To store user information: Unique identifiers are the perfect way to store user information, such as names, addresses, contact numbers, and more.
To improve data accuracy: Unique identifiers help to ensure that data is accurate and up-to-date.
To identify records: Unique identifiers make it easy to quickly identify and locate records in a database.
To secure data: Unique identifiers can be used to secure data and prevent unauthorized access.
To trace an event through a multi step automated process such as a flow, web service, or database.
So, if you are looking to create a unique ID and/or timestamp in Power Apps, then following code should help you out!
This code uses the Today(), Now(), and Text() functions in Power Apps to create a unique ID string based on the current date and time, and pads with leading zeroes. To use it, simply copy and paste it into your Power Apps app and assign it to a variable, replacing ‘varID’ with your own chosen variable name.
The resulting ID string will look something like this: 20230216215633, where the first 8 characters are the current date (yyyymmdd) and the last 6 characters are the current time (hhmmss).
We hope this code helps you create a unique ID and timestamp in Power Apps!
Open Visual Studio Code to an empty folder in lowercase with no spaces. Then open the “View”->”Explorer” window and the Terminal window. In this example I’m using C:\proj\
Visual Studio Code
To see if you have node installed, at the terminal prompt type:
PS C:\proj> node -v
v16.13.1
And you should see the version number returned.
Next enter
PS C:\proj> npx create-react-app .
to create the basic files and folders, download and install components needed to develop a React app.
To run the application use
PS C:\proj> npm start
To compile the application for deploying to web site use
In this lesson we will look at setting up a development environment for the WAX blockchain. Examples used will be primarily for those using Windows 10, but steps are adaptable to any platforms that Docker supports.
You can then run the following from a command prompt to get the wax development container
c:\>docker pull waxteam/dev
Step 2
Create a folder to store your project files in. In this example we are using C:\projects\wax.
Open a cmd prompt and change directory to that folder path.
Step 3
Run the following command at the cmd prompt to start up the WAX container in interactive mode. The waxteam/dev is a local development environment including a local blockchain,
c:\>docker run -it --name waxdev -v c:\projects\wax:/wax waxteam/dev bash
The container waxteam/cdt is for creating and compiling smart contracts.
c:\>docker run -it --name waxcdt -v c:\projects\wax:/wax waxteam/cdt bash
Step 4
In WAX container in interactive mode you can run bash command like ls
root@de932f6fabf7:/# ls
and change directory to /wax
root@de932f6fabf7:/wax# cd /wax
Step 5
You can now test connectivity with the cleos wallet commands and get back JSON responses
This is a barebones walkthrough for developing a blockchain decentralized app (Dapp) for Etherium (ERC-20) based tokens. Goal is to go through all the steps needed to set up initial environment and build a first contract that compiles, deploys, test, and can interact with via web3.js Javascript in a web browser.
Step 4: Truffle Develop Console
In this step we will look at the Truffle console before starting testing. Be sure to complete Steps 1 to Step 3 before attempting this step.
1. At the command line in the project folder type:
truffle develop
This will start a development blockchain server and generate 10 test wallets. (NOTE: this is not real Etherium and will not work on MAINNET)
truffle develop
2. You are now in the Truffle development console. You can use the generated public and private wallet keys to test your DApp transactions.
3. You can also compile your project in the console with the command “compile”
truffle(develop)> compile
compile …
4. You can deploy your project in the console with the command “deploy”
truffle(develop)> deploy
deploy …
In the next step we will create a test package and run the test from the console.
The Windows Server Failover Clustering (WSFC) resource control API returned error code 5057. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see “System Error Codes” in the Windows Development documentation.
At command prompt enter:
NET HELPMSG for 5057
You will then see that 5057 means “The cluster IP address is already in use.”
You can then ping – a the IP addresses and see which ones are in use.
This is a barebones walkthrough for developing a blockchain decentralized app (Dapp) for Etherium (ERC-20) based tokens. Goal is to go through all the steps needed to set up initial environment and build a first contract that compiles, deploys, test, and can interact with via web3.js Javascript in a web browser.
Step 3: Creating Variables and Functions
In this step we will add comments, state variables and functions to our contract. Be sure to complete Step 1 and Step 2 before attempting this step.
1. Comments can be designated in two ways. Use the // for single line and /* */ for multiline comments
// this is a single line comment
/*
use this for
multiline comments
*/
2. State variables are variables whose values are permanently stored in the blockchain. You can declare a state variable in the body of the contract. Visibility can be public, internal or private for state variables. A public state variable gets an automatically generated “getter” function.
Each statement ends with a semi-colon “;”
Also we will be using the datatype “uint” (not to be confused with ‘unit’) which stands for unsigned integer.
Add the following to the body of your contract.
//contract state variable
uint myVariable = 0;
State variable declaration
3. Functions are the bits of code that do something.
If the function reads but does not make any changes to the state of the contract it can be declared as a “view” function. If the function only acts on the input and does not read the state of the contract it can be declared as a “pure” function. These designations are important as they can help reduce the cost of Etherium to process the contract.
Visibility can be external, public, internal or private for functions.
Also, a common convention is to add an underscore to function parameters to avoid confusion between state variables at the contract scope and parameters in the function scope.
Add the following two functions to the body of your contract below the constructor.
function setMyVariable(uint _x) public {
myVariable = _x;
}
function getMyVariable () public view returns (uint) {
return myVariable;
}
10. Now save the file (in most editors is shortcut keys “Ctrl + s”). Now return to the Command Prompt window and compile your contract.
truffle compile
You should get results like the following. If you get any errors be sure the file is located in the right folder, the code matches, and the file has been saved.
