Windows Azure - The current service model is out of sync

When I run a Windows Azure web role on my local developer fabric, I get the following error:

>The current service model is out of sync. Make sure both the service configuration and definition files are valid.

One of my colleagues hit this issue and after a bit of playing about, 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 were in sync it all worked.

A tip would be to use the GUI in Visual Studio to add new settings to both at the same time. The GUI can be accessed by right clicking the web role and selection properties. This should open up a window. Click the Settings tab on the left.

For me, this was caused by my azure project having been copied from one PC to another (going from Win 7 to Win 8.1 in the process). I am using VS 2013 Community edition on both, but I had upgraded from Azure 2.4 on Win7 to Azure 2.5 on the Win 8.1 machine.

If you unload the azure project and edit the csproj file, you just need to make a small edit (e.g. adding a comment) and save it, so it re-writes itself. This fixed it in my case (where I'd spent ages checking for errors in the CSDEF and CSCFG files). Once I re-saved the csproj file, it worked fine.

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

Going over the files manually was a pain. There's an easy way to discover the descrepancies:

1. In the Solution Explorer, right-click one of the Roles that make up your Cloud Service and click 'Properties' in the context menu.

2. The Role properties window will open up grey with an error message saying: > "Invalid Service Definition or service configuration. Please see the > Error List for more details".

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

I followed all the answers here and it still didn't work eventually I restarted Visual Studio and it worked.

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

What worked for me was to:

1. Make sure the Cloud Services .cscfg and .Local.cscfg files were identical (unless you need your Local.cscfg to have some differences for debugging purposes),
2. Make sure the .csdef file had definitions that matched the .cscfg files, and then
3. Close the project and delete its Cloud Services .ccproj.user file.

After reloading the project, all was well.

The error can occour when there is no actual fault in the service configurations. If it occours and everything seems to be correct, instead of restarting visual studio, simply unload the azurecloud project (rightclick: unload proecjt

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

My problem was incorrect certificate definition in csdef file.

Had this issue - no errors though. I have found that for some bizarre reason the if the setting:

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

was commented out, then the workerrole would not launch.

For me the problem was that the Wifi I was using blocked the PORT Azure is using, changing Wifi solved that problem.

For me, the issue turned out to be an inconsistency between the vmName value I had assigned to one of my roles in my various environments. I have a *.cscfg files for my development, test, and production environments. Each of these had a role definition that was supposed to be along the lines of

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

but one had an entry like

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

and that, apparently, was enough to trigger the error.