Azure-Deployment to Stage Ignores Service Configuration

Question

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

and here are my configuration settings:

Then, when I publish, I configured the deployment as follows:

It all worked like 2 weeks ago. But now it is deployed to VS and when I look at the Azure Service configuration area, it looks like this:

I played a little with "Development Update ..." - a checkmark on the second screen, but the result is the same.

Therefore, it ignores all the settings that I made, and simply will not convert my configuration to ine, which I called "CloudStage". My current Web PI tells me that I am using the Windows Azure SDK for .NET (VS 2013) 2.3. I do not understand.

Edit A few more things I observed:

• WADLogsTable and WADWindowsEventLogsTable are automatically created in staging storage.
• I disabled Remote Desktop because it was one of the changes I made to monitor the event log (which was not useful here)
• I manually changed the connection strings to Azure Portal, but it seems that the worker is completely unaware of the repository (it rebooted without success).

Edit

I learned something else. Here you can see the deployment of my service:

See the warning sign on the left? If I go to my error list, it will be shown:

This warning is pointless because it tells me that I did everything right. My * .Local.csfg files point to local storage. So that?!?

Answer 1

So, it turns out that the problem is entirely on the client side. My Visual Studio (now with SDK 2.4) is doing something wrong. I installed a new installation with everything you need :-( and there it works fine. I will try to determine if one of my extensions causes the strange "Object reference not set ..." error.

Repair-Installation VS does not solve the btw problem.

Answer 2

That seems weird. Please check in ServiceConfiguration.CloudStage.cscfg to check the expected values. Have you tried updating any other property, such as "Enable Remote Desktop"? Is this updated during deployment? You must select the Update Deployment check box in the publish dialog box. Now, when deploying to an existing cloud service, it should ask you if you want to replace it. If you get an object reference error every time you right-click on a project, there may be a problem with configuring the Azure SDK.

Answer 3

Now I'm a little further. I have done this:

• Removed all services in Azure.
• Removed all storage accounts in Azure
• Removed my service project completely from the solution (and not the library containing the working logic).
• Added storage accounts in Azure.
• Additional services in Azure.
• Re-added the project to the solution and added the working logic inside it.
• Create all the materials for publication again.
• Published.

The first publication ends as described in my question. After I checked the option "Development Update ..." in the properties of my worker, he finally moved on to the scene!

Now I realized that WADLogsTable is still empty. I hit the instance directly in server-explorer and selected "Update diagnostic settings ...". There was a Transmission Period option that was suddenly set to No. This explained to me why my table was empty, and after I returned it to "1", my table was full again!

Another funny thing: when I right-clicked my Cloud project in the solution, I get "The object link is not installed in the instance ...". When I just click on it to the left and select Build-> Publish, it will work.

I just hope I can help someone with this. Let's see if it is stable now.

Edit : Yesterday it worked - today it’s the same problem: - (.

Answer 4

When you get the " Object reference not set to an instance.. " for the CloudService project , you usually have some kind of mismatch. Maybe the setting in ServiceConfiguration not defined in ServiceDefinition . It may also be that there is a publishing profile defined in the .ccproj file for CloudService that does not exist. It can also cause problems with various configurations.