I just share this if someone else is facing the same problem. When updating links to Azure in response to forced guestOS updates 09/12/2013 (which turned off our production cloud)
If you diagnose why the web role did not start to emulate the azure cloud locally, you can check the event viewer, and in Windows Logs β Application look for the IIS Express error ... I was getting this:
Workflow for application pool "5665782e-ae77-4547-8cc2-3a7b3357602d" encountered an error "Cannot read configuration file 'trying to read global module configuration data from file' \? \ C: \ Users \ Mark \ AppData \ Local \ dftmp \ Resources \ 633952fb-10b8-4b96-b732-ad19eb835438 \ temp \ temp \ RoleTemp \ applicationHost.config ', line number' 0 '. The workflow was aborted.
It turned out that after updating the azure links using the NuGet package manager, the entries for the membership provider, role provider and session state were duplicated. We do not use default values ββfor these attributes, so this may be the cause of the problem ...
Nevertheless, check your web.config for duplicate attributes. This is one of the potential reasons for your non-claiming web role.
azure localhost
user3101454
source share