|
 |
aspx_beginners thread: Re: Server Application Unavailable Error
Message #1 by "Dhiraj Murarka" <dhirajmurarka@r...> on Sat, 2 Feb 2002 05:10:11
|
|
> Hi All,
> Thanks in Advance.
> When i am executing and .aspx file i am getting the following error.
> Do suggest what is the problem with my setting.
> I had installed MDAC 2.7 and ASP.net Premium Beta2 on my mechine
> which is running on Windows 2000.
>
> The Error message which was displayed on the Browers is :
>
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web
> browser to retry your request.
>
> Administrator Note: An error message detailing the cause of this
specific
> request failure can be found in the system event log of the web server.
> Please review this log entry to discover what caused this error to occur
>
> Shyam
Message #2 by Imar Spaanjaars <Imar@S...> on Sat, 02 Feb 2002 09:55:08 +0100
|
|
Are you running ASP.NET on a Primary Domain Controller? I had the same
problem when I installed it on a PDC. Check out the following KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315158
HtH
Imar
At 05:10 AM 2/2/2002 +0000, you wrote:
> > Hi All,
> > Thanks in Advance.
> > When i am executing and .aspx file i am getting the following error.
> > Do suggest what is the problem with my setting.
> > I had installed MDAC 2.7 and ASP.net Premium Beta2 on my mechine
> > which is running on Windows 2000.
> >
> > The Error message which was displayed on the Browers is :
> >
> > Server Application Unavailable
> > The web application you are attempting to access on this web server is
> > currently unavailable. Please hit the "Refresh" button in your web
> > browser to retry your request.
> >
> > Administrator Note: An error message detailing the cause of this
>specific
> > request failure can be found in the system event log of the web server.
> > Please review this log entry to discover what caused this error to occur
> >
> > Shyam
Message #3 by "Rick J. Girling" <rick_girling@m...> on Wed, 20 Feb 2002 18:40:48
|
|
Had the same problem, the cause and solution are posted in MS knowledge
base...
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315158
Rick
> Hi All,
> Thanks in Advance.
> When i am executing and .aspx file i am getting the following error.
> Do suggest what is the problem with my setting.
> I had installed MDAC 2.7 and ASP.net Premium Beta2 on my mechine
> which is running on Windows 2000.
>
> The Error message which was displayed on the Browers is :
>
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web
> browser to retry your request.
>
> Administrator Note: An error message detailing the cause of this
specific
> request failure can be found in the system event log of the web server.
> Please review this log entry to discover what caused this error to occur
>
> Shyam
Message #4 by "Widi Pramudiya" <widi@s...> on Mon, 25 Feb 2002 08:23:57
|
|
It looks like you are running IIS on a Domain Controller.
To enable this you need to run the worker process (aspnet_wp.exe) with the
SYSTEM identity by changing your machine.config file,
like:
change the userName attribute to "System", for example like this :
<processModel userName="System" password="autogenerate" ...
Widi Pramudiya
> Hi All,
> Thanks in Advance.
> When i am executing and .aspx file i am getting the following error.
> Do suggest what is the problem with my setting.
> I had installed MDAC 2.7 and ASP.net Premium Beta2 on my mechine
> which is running on Windows 2000.
>
> The Error message which was displayed on the Browers is :
>
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web
> browser to retry your request.
>
> Administrator Note: An error message detailing the cause of this
specific
> request failure can be found in the system event log of the web server.
> Please review this log entry to discover what caused this error to occur
>
> Shyam
|
|
 |