This blog post explains what to do if you get any of the following exceptions when trying to install Windows Azure (or you may get the 2nd exception below when you do F5 for your first Windows Azure project in Visual Studio 2010)
- Fatal error during installation!
- “There was an error attaching the debugger to the IIS worker process for URL …..” in Visual Studio 2010.
If you are using the WebPI for installing Windows Azure, you may fumble upon the following nasty error!
If you do get this, follow the instructions below and you should be good:
- Uninstall existing versions of azure installation (do this from add/remove programs)
- If IIS 7.0 and few of its components are installed and you feel you might have messed with that earlier, do turn those features off. (Control Panel à Turn windows feature on/off)
- Ensure that you the highlighted portions below are unchecked:
- Click ok.
- Restart the machine once asked for.
- Open the Turn Windows Feature on/off again and ensure you have the below selected. (from the above highlighted portions in red- in the figure)
- IIS7 with ASP.NET
- Static Content, IIS Management Console and HTTP Redirection.
- WCF HTTP Activation
- Once this is done, double check if all requirements are in order-
Supported operating systems: Windows 7, Windows Server 2008, Windows Server 2008 R2.
Note: Windows 7 Home Basic is not supported.
- Required Software:
- Microsoft Visual Studio 2010 Professional or above OR Microsoft Visual Web Developer 2010 Express. (only when installing the Windows Azure Tools)
- SQL Server 2008 Express Edition.
- IIS7 with ASP.NET and WCF HTTP Activation, Static Content, IIS Management Console and HTTP Redirection.
- IIS URL Rewrite Module 2.0
- ASP.NET MVC 3 Tools Update
- Windows PowerShell
- Hotfix: Enable Windows Azure IntelliTrace on 32-Bit OS (not required for x64 OS).
- .NET Framework 3.5 (only for Windows Server 2008)
- You can now go to downloads section of windowsazure.com- (https://www.windowsazure.com/en-us/develop/downloads/)
- Click on the install button ( for .net in my case- see below):
- The fatal error should now go away. And the tools and libraries should now be installed properly.
- We generally tend to think WebPI is magical and it will automatically take care of everything, but sometimes it may not (cases when IIS is messy and if you installed IIS after .Net framework 4.0 etc). The above steps take not more than 15 mins and you should be up and ready.
You may also have to follow the above steps when you get the below exception in Visual Studio- “There was an error attaching the debugger to the IIS worker process for URL …”.
At least after a day’s research thats what I ended up doing. This error in Visual Studio essentially means that IIS is messed up in terms of app pool mode or WAS installation is not proper. Best is to follow the above instructions and it’s faster than any other approach unless you want to guess what was installed in what order and repair it using that approach step by step.
Hope this helps…