Tuesday, 10 May 2016

There was an error attaching the debugger to the role instance

Another great Azure error when debugging on my local machine. I tried clean, rebuild, restart windows etc. and I knew that I had not changed anything in the project that was previously debugging OK to make it break - what gives?

When trying to debug, the azure emulator would start up and then you see the weird error above (plus extra stuff) and it shuts down again.

Thanks to this article, I saw a hint that you can look into the iis configurator log and look for errors:

Just type %UserProfile%\AppData\Local\dftmp\IISConfiguratorLogs\IISConfigurator.log into your explorer bar and press enter.

Inside mine, I saw the line: Adding access to users IUSR and NT AUTHORITY\NETWORK SERVICE to path C:\Users\luke\Documents\Visual Studio 2013\Projects\etc immediately followed by Exception:System.InvalidOperationException: This access control list is not in canonical form and therefore cannot be modified.

Weird error, basically some kind of permission thing obviously. I think it means that the permissions on the project directory are not the same across all of the sub-folders, which must have happened due to some crash or other.

I went to the folder in question, edited the security settings in the properties and applied them to the folder. At this point, I had an error with an aspnet_client folder that was denied permission to update settings, despite being a local admin (thanks Microsoft)! I found the folder, manually deleted it, giving my "consent" to the process and after that, it all ran up OK. Obviously, if the folder is important, you might have to do something more long-winded to reset its permissions but you get the idea.
Post a Comment