Unauthorized / Service Unavailable ??
Barry Fitzgerald
that was just set up a couple of weeks ago. Everything except the web
server seems to be acting properly. There is a default.htm page set up on
the default web site and also a .NET app in a virtual directory. The site
works fine for a little while and then when I go the next page of the site I
get a page that says Service Unavailable. I have never seen that before
coming from IIS and it is not one of my pages?? Clicking the back button
and then going forward by resubmitting the page sometimes works and sometime
doesn't. After a while the site simply refuses to allow any annonymous
entry (not authorized error). If I try to access localhost, I get a page
not found error. If you reboot the server, everything works again except for
the occaisional Service Unavailable page. I though I had this working a few
days ago but I think it was just that I rebooted.
Any idea what is going on here? Could this be something the isp is doing to
us? Where would a "Service Unavailable" page come from?
--
Barry Fitzgerald
Wei-Dong Xu [MSFT]
Thank you for posting in MSDN managed newsgroup!
So far as I know, this issue may be related to the application pool of your site. By default, the IIS6 will run in IIS6 worker process isolation mode
(WPIM) which means the IIS web site and asp.net web application will run in the worker process not the inetinfo process or DLLhost.exe as in IIS5
or before. I'd suggest you can check the property of the default web site and in the "Home directory", you will find the used application pool for
the default web site in the "application pool" listbox. It will be "Default web sites" application pool by default. You can locate the application pool
under the "Application pools" node of IIS mmc. The IIS6 documentation will provide the information for you regarding the WPIM and the
configuration of application pool. You can also obtain the information from Microsoft.com. Please go to:
Worker Process Isolation Mode
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/standard/ca_wpim.asp?frame=true
Configuring Application Pools
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/standard/ca_cfgapppools.asp?frame=true
For the "service/unavailable" error, I'd suggest you can find the application pool of your asp.net by checking the "Home directory" property from
the virtual directory's property. If the application pool used by asp.net is the same to the default web site, I'd suggest you can create one new
application pool only for the asp.net web application and then configure it for your scenario. Moreover, the asp.net web application running in IIS6
WPIM will ignore the <ProcessModel> property in asp.net configuration file. In WPIM of IIS6, all the configuration elements can be set in the
related application pool porperty.
Furthermore, you may check the event viewer and IIS log for any related error message. If you find some, it will be appreciated you post them in
the thread.
Please feel free to let me know if you have any further questions.
Does this answer your question? Thank you for using Microsoft NewsGroup!
Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
Wei-Dong Xu [MSFT]
Furthermore, I'd also suggest the kb article 812614 introduces the security settings of IIS. You may check your asp.net web application to see
whether the application has performed some opeartions which need higher privilege. This way, you can check the "identity" tab of the related
application pool to set the identity from "Network Services" be default to "Local service" or Local system. In addition, you may find more information
fro the IIS6 documentation with the phrase "Predefined Accounts". Please go to:
812614 INFO: Default Permissions and User Rights for IIS 6.0
http://support.microsoft.com/?id=812614
Barry Fitzgerald
errant entry in the dns tables that may have been causing problems. We also
had pcAnywhere running and disabled that. That seems to have stopped the
unauthorized access error, I am not sure why either of those would cause
that problem. I also had set the number of web site connections to 5. When
I set it to unlimited the Service Unavailable error stopped occurring. I do
not understand why that would happen. This is a test site with no .com
address. No one has created a new account id. I would think that once a
session starts it would hold it's connection. I will do some testing to see
how many connections are required to make the site function. Can you get me
some info on why they connections would cause this problem for a aspx site?
Thanks
--
Barry Fitzgerald
"Wei-Dong Xu [MSFT]" <v-w...@online.microsoft.com> wrote in message
news:EgRWsfiv...@cpmsftngxa07.phx.gbl...
Wei-Dong Xu [MSFT]
Thank you for replying and the mroe information regarding the troubleshooting!
This error is often caused by the application pool error. If we set IIS6 to WPIM, each request to the IIS will be sent by HTTP.sys to the related
worker process and be processed by the worker process. If some errors cause the worker process down, the "service unavailable" error will be
thrown. From this view, I suggested you could troubleshoot this issue with the configuration of application pool(the UI management of the settings
for worker process) in the above message.
Generally speaking, there will be some reasons which will cause the worker process down. In most scenarios, it is not very easy for us to locate the
culprit. Perhaps you should capture one memory to analysis.
From your troubleshooting message, this issue may be related to the connection limitation. In default setting, IIS6 will enable "HTTP keep-Alives".
You can find this from the "web site" tab from the "web site" property(the "web sites" node in the IIS mmc which settings is for web site). If one
client connects to the IIS, IIS will keep this connection for a short time. This way, if the customer come back immediately, this connection will be
reused which will reduce the connection time and give a quick response for web requests. Then after 5 connections are used, IIS6 has met the
limitation in your scenario, then there is no bandwidth for the 6th request. IIS6 will report an error "service unavailable".
For your scenario, I'd suggest you may set the bandwidth limitation for each web site instead of connection number. The bandwidth limitaion can be
set globally for every site or for each site. You can right click for the "Web sites" property or for each site's property. In performance tab of the
property window, please specify the bandwidth limitaion for your web site(s).