Could not get the Microsoft Azure storage account settings - c#

I'm trrying to publish an ASP.NET MVC project to azure.
In other computer i do this without problems, but in mine I don't.
The following error appears when publishing in Visual Studio 2013 :
Could not get the Microsoft Azure storage account settings for
'account-name' needed to configure an application module.
Please check your network connection and verify that the account exists.

Is your project using Azure SDK 2.6 but you also have Azure SDK 2.7 installed? I had the same error and upgrading my cloud project to Azure SDK 2.7 seemed to fix it.

Related

Azure API app not visible in Azure portal after publishing

I published my ASP .NET Web API 2 project to Azure as an API app. I used Visual Studio 2013 and got this lovely screen after publishing.
But the API app is no where to be found in my Azure portal.
I looked in my Visual Studio Server Explorer and it is there.
I got the same result as yours after publishing the API app, it's just not listed when clicking Browse > API Apps. Although it says "Web, Mobile and API apps are now in one list", it obviously doesn't work as it says.
Anyway, you can alternatively find your API app in the resource group which you specified in the publishing profile:
Or, just right click the API app in Server Explorer and select "Open in Management Portal" option to open it in the portal:

Azure App Services isn't available

I've been trying to use Azure as Mobile App service and in the tutorial it is given to choose this :
Whilst when i try to follow it shows this :
Can anyone help ? Thank you :)
The Azure Visual Studio tooling, however, should be upgraded to version 2.8.1 or later...
https://azure.microsoft.com/en-us/downloads/
https://azure.microsoft.com/en-us/documentation/articles/app-service-api-whats-changed/
As Thiago suggested, you will have to install the latest Azure SDK to get the option.
If not, then you can select the Import option. This will require you to provide the publishsettings file.
You can download the publishsettings file from the Azure Portal. Here is a sample image: http://i.stack.imgur.com/YV2OQ.jpg
Once you have imported it, the IDE will pick the deployment endpoints from the file and you will be able to publish the App.
NOTE: Mobile Apps have the same deployment as the Web Apps. The IDE doesn't have the tooling to pick Mobile APPS from the subscription. Until then you will have to use the Import option in the VS deployment wizard.

Azure Blob Storage Emulator Error [duplicate]

For some reason my DevStorage account has stopped working. I get a 400 Bad Request error on every request to DevStorage (both Blob and Table). I can browse DevStorage with Azure Storage Explorer, though.
This is really strange, because I'm not aware of changing anything to the environment.
I have re-installed Azure SDK 2.1 (July 2013). Even after a clean install, it does not work. When I deploy the cloud service to Windows Azure, it works fine. Running it in the emulator doesn't.
I actually use the same code as the samples to connect, but I'll post it anyway.
// Storage account
var storageAccount = CloudStorageAccount.Parse(
CloudConfigurationManager.GetSetting("StorageConnectionString"));
// Blob client
var blobClient = storageAccount.CreateCloudBlobClient();
// Container
var cloudContainer = blobClient.GetContainerReference(container);
cloudContainer.CreateIfNotExists();
Value of StorageConnectionString is UseDevelopmentStorage=true.
Container is lowercase, letters only (e.g. 'pictures').
I run Visual Studio 2012 as administrator.
Any help would be much appreciated!
Did you by any chance install the latest version of Storage Client library (3.0.0.0) which was released yesterday? That could be one reason why your code stopped working because the latest version of library doesn't work with storage emulator (Scroll down to the bottom of this post: http://blogs.msdn.com/b/windowsazurestorage/archive/2013/11/27/windows-azure-storage-release-introducing-cors-json-minute-metrics-and-more.aspx). If you look at the detailed error message, you will see One of the request headers is invalid.
UPDATE: 03-Feb-2014
Please download Storage Emulator 2.2.1 Preview which has support for latest storage client library. More information about this release can be found here: http://blogs.msdn.com/b/windowsazurestorage/archive/2014/01/27/windows-azure-storage-emulator-2-2-1-preview-release-with-support-for-2013-08-15-version.aspx.
UPDATE: 15-Apr-2014
If you're using SDK Version 2.3, then there's no need for installing Storage Emulator 2.2.1. Storage Emulator in version 2.3 fully supports Storage client library 3.x.
I had the same problem with Azure Storage Emulator 3.0.0 which came from Azure SDK 2.3 on VS 2013 update 2.
To solve the problem I started the Web Platform Installer and searched for Storage Emulator then ran the Azure SDK 2.3 (VS2013) and it installed Storage Emulator 3.2.0.0 which fixes the problem.

Publish History in Windows Azure Websites

How can i check the Publishing History of Windows Azure Websites. We are publishing our application using Publish Profile in Visual Studio 2012. We are using Code First Approach of Entity Framework
Last night someone changed the DB or Application from Production server but we are unable to check the History...
I dont think you can check the publish history, if you are using publishsettings file.
But you can use most of the version controls repositories like Git, TFS, Dropbox etc., and integrate automated deployments to azurewebsite from them. In that case deployment history will be maintained by Azure itself and you can view the history on Azure Portal.
Check out this ref for Git Deployment

Azure 400 Bad Request on every request

For some reason my DevStorage account has stopped working. I get a 400 Bad Request error on every request to DevStorage (both Blob and Table). I can browse DevStorage with Azure Storage Explorer, though.
This is really strange, because I'm not aware of changing anything to the environment.
I have re-installed Azure SDK 2.1 (July 2013). Even after a clean install, it does not work. When I deploy the cloud service to Windows Azure, it works fine. Running it in the emulator doesn't.
I actually use the same code as the samples to connect, but I'll post it anyway.
// Storage account
var storageAccount = CloudStorageAccount.Parse(
CloudConfigurationManager.GetSetting("StorageConnectionString"));
// Blob client
var blobClient = storageAccount.CreateCloudBlobClient();
// Container
var cloudContainer = blobClient.GetContainerReference(container);
cloudContainer.CreateIfNotExists();
Value of StorageConnectionString is UseDevelopmentStorage=true.
Container is lowercase, letters only (e.g. 'pictures').
I run Visual Studio 2012 as administrator.
Any help would be much appreciated!
Did you by any chance install the latest version of Storage Client library (3.0.0.0) which was released yesterday? That could be one reason why your code stopped working because the latest version of library doesn't work with storage emulator (Scroll down to the bottom of this post: http://blogs.msdn.com/b/windowsazurestorage/archive/2013/11/27/windows-azure-storage-release-introducing-cors-json-minute-metrics-and-more.aspx). If you look at the detailed error message, you will see One of the request headers is invalid.
UPDATE: 03-Feb-2014
Please download Storage Emulator 2.2.1 Preview which has support for latest storage client library. More information about this release can be found here: http://blogs.msdn.com/b/windowsazurestorage/archive/2014/01/27/windows-azure-storage-emulator-2-2-1-preview-release-with-support-for-2013-08-15-version.aspx.
UPDATE: 15-Apr-2014
If you're using SDK Version 2.3, then there's no need for installing Storage Emulator 2.2.1. Storage Emulator in version 2.3 fully supports Storage client library 3.x.
I had the same problem with Azure Storage Emulator 3.0.0 which came from Azure SDK 2.3 on VS 2013 update 2.
To solve the problem I started the Web Platform Installer and searched for Storage Emulator then ran the Azure SDK 2.3 (VS2013) and it installed Storage Emulator 3.2.0.0 which fixes the problem.

Categories