Windows Azure - current service model out of sync

Question

When I run the Windows Azure web role in my local developer framework, I get the following error:

"The current service model is not synchronized. Verify that the service configuration files and definitions are valid.

What ideas might come up?

Answer 1

One of my colleagues hit this problem, and after a short conversation the problem was that the two service configuration files (cloud and local) had a different number of settings.

When he updated the configuration files so that they synchronized, it all worked.

The board will use the graphical interface in Visual Studio to add new parameters at the same time. The GUI can be accessed by right-clicking the web role properties and selection properties. This should open a window. Click on the "Settings" tab on the left.

Hope this helps

Answer 2

For me, this was due to the fact that my azure project was copied from one computer to another (from Win 7 to Win 8.1 in the process). I use VS 2013 Community Edition for both, but I upgraded from Azure 2.4 on Win7 to Azure 2.5 on a Win 8.1 machine.

If you unload the azure project and edit the csproj file, you just need to do a little editing (for example, add a comment) and save it so that it overwrites itself. This was fixed in my case (where I checked the age by checking for errors in the CSDEF and CSCFG files). As soon as I re-saved the csproj file, it worked fine.

Answer 3

I followed all the answers here, and it still didn't work, in the end I restarted the visual studio and it worked.

I believe the solution was a combination of one or more answers here + restarting VS

Answer 4

What worked for me was:

• Make sure that the cloud services files .cscfg and .Local.cscfg identical (if you do not need your Local.cscfg to have some differences for debugging purposes),
• Verify that the .csdef file contains definitions that match the .cscfg files, and then
• Close the project and delete its .ccproj.user cloud services .ccproj.user .

After rebooting the project, everything was fine.

Answer 5

This happened to me because in one of my cloud configuration files (.cscfg) there were some key-value pairs that were defined in ServiceDefinition.csdef.

Moving files manually was painful. There is an easy way to detect discrepancies:

• In Solution Explorer, right-click one of the roles that make up your cloud service and click Properties on the shortcut menu.

  

• A gray color appears in the role properties window with an error message:

  "Incorrect service definition or service configuration. Error list for more details."

• Open the "Error List" window, and in some cases you should be able to see a list of specific discrepancies, complete with the file and property names.

  

Answer 6

An error can occur if there is no actual malfunction in the service configurations. If this happens and everything seems to be correct, instead of restarting the visual studio, just unload the azurecloud project (rightclick: unload proecjt

Answer 7

I had the same problem and tried several answers on this page, including modifying the project file. At first, I made sure that there were no errors or inconsistencies in the cscfg and cfdef files. What finally resolved this for me is to do as Danfromisrael believes: restart VS.

Answer 8

He solved my problem by restarting VS as suggested by @danfromisrael.

Thanks danfromisrael.

Answer 9

Please cross over the ServiceConfiguration.Cloud.cscfg and ServiceConfiguration.Local.cscfg files. My problem was that I added the configuration to Local.cscfg , but forgot to add the same to Cloud.cscfg

Answer 10

I also had this problem. My problem was the wrong certificate definition in the csdef file.

Answer 11

If this problem - no errors. I found that for some bizarre reason, if the parameter is:

 <Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="UseDevelopmentStorage=true" /> 

was commented, then the worker did not start.

Answer 12

May help others:

For me, the problem was that the Wi-Fi that I used blocked the use of PORT Azure, changing Wifi solved this problem.

Answer 13

For me, the vmName problem in the mismatch between the vmName value I assigned to one of my roles in different environments. I have * .cscfg files for my development, testing, and production environment. Each of them had a definition of a role that was supposed to correspond

  <Role name="HardWorker" vmName="SomeName">...</Role> 

but one had a record like

  <Role name="HardWorker" vmName="SomeOtherName">...</Role> 

and this, apparently, was enough to cause an error.