Incorrect service definition or service configuration

Question

I have a standard Azure build - one web role, one work role. After the last merger, he decided that the roles were invalid. When I double-click on the role of a web role or a working role, or when I right-click and select "Properties", I get a gray screen with the inscription "Invalid service definition or service configuration." See the "List of errors" for details. However, there is nothing in the list of errors.

I cross- csdef Settings elements and tried to comment out the sections of the csdef and cscfg files, but nothing seemed to return the role. I spent half a day on this already. My question is not so much what is “wrong”, but how on earth should you find out what an error is when information is not indicated, and subsequent removal from the code draws an exhaustive gap?

Answer 1

In this case, there was nothing with the csdef and cscfg . These were wadcfgx -related wadcfgx files.

I'm on a branch using Azure 2.5; another branch is on a previous version of Azure, which uses an older version of diagnostics. By wadcfgx existing wadcfgx files and regenerating them, I was able to make the roles visible and editable again. Of course, the presence of different versions in different branches opens a very large can of worms, but so far we are stuck in this difficult situation.

Answer 2

I came across this several times (VS 2015 Enterprise). Just closing and reopening the solution solved the problem.

Answer 3

I just came across this after adding a new work role project to an existing cloud service with several existing work roles.

In my ServiceConfiguration.Cloud.cscfg , I had a <NetworkConfiguration> between the old roles and the new role. That was the problem. I just moved the <NetworkConfiguration> to the bottom, as it was before (this tag is not in my ServiceConfiguration.Local.cscfg file, which could be a problem).

This is probably not the most common cause of this problem, but I thought that I would post a message saying that someone has similar settings.

Answer 4

Check if the size of the virtual machine is specified in the Small or Extra Small configuration, as it does not support more than on the local emulator. In my case, it was installed by default for the standard VM size. I resized to Extra Small and it started working fine!