Monday, December 11, 2006
Service Unavailable error and IIS 6.0
Today I experienced very strange behavior from my local IIS 6.0. Everythime I accessed some web site previously working sound, I kept on getting this empty page saying "Service Unavailable". When I saw that all of my Web sites part of my current project are showing this same message, I tried to open a stand-alone and completely different Web app, but again the same message. Ok, that's was a clear indication that there was something wrong with the IIS6 installed on my local box. I hit the Internet and found the following KB article on MSDN site (link). This just rang up a bell that the problem can be rooted in the app pools I've been using. And it was a true suggestion - I had to change the identity under which my default ASP.NET 2.0 app pools were using (since the old one was not valid anymore). And now I have one greatly working IIS 6.0 up and running...
Subscribe to:
Post Comments (Atom)
3 comments:
Could you please tell me how to do it?
Could you tell me how to change teh identity of teh applicaiton pool?
Start the Internet Information Services Manager (IISMGR). Then, make sure your IISMGR is connected to the right machine (if you want to administer your local IIS, then you are connected on default, but if you want to configure some other machine, you have to connect to it manually).
Within IISMGR, expand the left side tree view and go to "Application Pools". Then find the app pool you want to modify. Right click on it and choose Properties form the menu. The dialog that shows up has a tab named "Identity", where you specify the account information that this particular app pool will be using.
Post a Comment