LabVIEW Cloud Toolkits

Showing results for 
Search instead for 
Did you mean: 

Microsoft Azure VIs Run Error

Go to solution

I successfully applied for the Azure cloud account today, but the example in the library ran error in compilation. I quit the firewall and antivirus software, and the fault is still. When debugging, it was found that it was wrong to run to How do I solve it?

Create Container Error.PNG

0 Kudos
Message 1 of 6

For the Storage Account Name, make sure you're specifying the account name that you see in the Azure portal here:




For the Access Key, you can go to Settings > Access keys and copy the 'Key' value from either the 'key1' or 'key2' field.

DNatt, NI
0 Kudos
Message 2 of 6

Thank Darren's quick reply!


The program was run according to the following diagram, but it still did not solve the problem.I do not update the content of key1 and key2.






Storage Account Name:


Please run on your computer to see if it works OK.Thanks!


Access name.png


Create New Container.png


0 Kudos
Message 3 of 6
Accepted by topic author mcusir

Hi there,


It's really not a good idea to post these keys on a public site, this gives anyone the potential to start manipulating your Azure account. I recommend regenerating key1 and key2 ASAP. 


I see the source of the problem though. It looks like Azure toolkit's Create Host has hard coded to use the EndpointSuffix in the url to contain "". In your case, you've signed up for a Azure China account, and it has a different EndpointSuffix for the host URL. This will cause problems for other special Azure clouds (Germany, US government, China). You can fix it yourself by modifying the string constant to be instead of




Danny Funk -- Group Manager -- LabVIEW R&D -- National Instruments
0 Kudos
Message 4 of 6

Thank you for the quick and successful Reply of Danny Funk.


I have successfully created the container.I regenerated key1 and key2.

0 Kudos
Message 5 of 6

The question is about the NI Cloud Toolkit for Azure.

To open an Azure session I use the VI Open Azure

The opening parameters consist of a Storage Account Name and an Access Key.

For example :

Storage Account Name: storidddev2223

AccessKey: VjUz0XdYsr8e+B4Bxtabcdefghkly/123456778902345678923+NftIULBSk4skUA2U2i/Q==

This method works

We would like to change the identification method for a SAS Token.

Is it possible with this toolkit?


We tried the following new form of Key Access:

Storage Account Name: storidddev2223


BlobEndpoint = https: //; QueueEndpoint=https: //; FileEndpoint= ; TableEndpoint=; SharedAccessSignature=sv=2020-02-10&ss=bqt&srt=sco&sp=rwdlacupx&se=2022-03-31T17:31:16Z & st=2021-03-18T17:31:16Z&spr=https&sig=ABCDhijkRjYi7jCCoBBvYsSZ%2FlHAAAbEF9AXYZERbs%3D


Can you tell us if the error is in the format of the access key and if there is a solution to solve this problem?

What is the correct format?


Note: the storage account and access key names have been changed for confidentiality purposes.





0 Kudos
Message 6 of 6