Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Azure-Deployment to stage ignores service configuration

I created a cloud service and tested it successfully locally. I added service configurations for stage and production. Here is a snippet of my staging-configuration:

Service Configuration

and here my configuration-settings:

Configuration start page

Then when I publish I set up the deployment as follows:

publishing settings

All this worked like 2 weeks ago. But now he deploys in VS and when I look into Azure Service Configure area it looks like this:

Configure area in Azure after publish

I played a little bit with the "Update development ..."-checkbox on the second screen but the result is the same.

So it ignores all the settings I made and just won't tranistion my configuration to the ine I named "CloudStage". My current Web PI tells me that I use Windows Azure SDK for .NET (VS 2013) 2.3. I don't get the point.

Edit Some more things I observed:

  • No WADLogsTable and WADWindowsEventLogsTable is generated automatically in the staging storage.
  • I deactivated Remote Desktop because it was one of the changes I made to monitor the event log (which wasn't useful here)
  • I manually changed the connection strings in Azure Portal but it seems as if the worker is totally unaware of the storage (rebooted it with no success).

Edit

I recognized another thing. Here you can see a running deployment of my service:

Deployment started

See the warning-mark on the left? If I go to my Error list this is shown:

Senseless warnings

This warning is senseless since it tells me that I did everything the right way. My *.Local.csfg-files are pointing to the local storage. So?!?

like image 530
Alexander Schmidt Avatar asked May 28 '14 11:05

Alexander Schmidt


1 Answers

This seems weird. Please check the in your ServiceConfiguration.CloudStage.cscfg to verify the expected values. Have you tried updating any other property like Enabling Remote desktop? Does that get updated on your deployment? You should select the "Deployment Update" check box in the publish dialog. Now, when deploying to an existing Cloud Service, it should ask you if you want to replace it. If you get the Object reference error every time you right click on project, there might be some issue with the Azure SDK set up.

like image 171
Gaurav Avatar answered Sep 28 '22 05:09

Gaurav