Wierd error on web server

Hi,

I develop an ASP.NET application based on a ajax framwework (Visual
WebGui)
When I install the application on the client web server, after few
days, when I try to access the application, the server answers with an
error message like this

"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 application event log of
the web server. Please review this log entry to discover what caused
this error to occur."

This happens ONLY on client server. It never hgappened on my develop
or test server (where I test the app before deploying)

The solution I found is to stop and restart the WWW service from
Services control panel

Does anyone knows what is the reason for this. The app is installed
onto a virtual directory of the main website of the client server.
Main website is a simple html only, static web. And the server serves
it ok, even when it gets the error above on my app.

Please help

Thanks
Bogdan

Re: Wierd error on web server

What is the message logged in the application event log?

You should not restart WWW service. It should be enough to restart the
application pool.

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


"bz" skrev i meddelandet
news:33f01fd3-d3b5-44e9-9df5-c4c047658e83@i29g2000prf.google groups.com...
> Hi,
>
> I develop an ASP.NET application based on a ajax framwework (Visual
> WebGui)
> When I install the application on the client web server, after few
> days, when I try to access the application, the server answers with an
> error message like this
>
> "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 application event log of
> the web server. Please review this log entry to discover what caused
> this error to occur."
>
> This happens ONLY on client server. It never hgappened on my develop
> or test server (where I test the app before deploying)
>
> The solution I found is to stop and restart the WWW service from
> Services control panel
>
> Does anyone knows what is the reason for this. The app is installed
> onto a virtual directory of the main website of the client server.
> Main website is a simple html only, static web. And the server serves
> it ok, even when it gets the error above on my app.
>
> Please help
>
> Thanks
> Bogdan

Re: Wierd error on web server

On Dec 2, 8:14 am, bz wrote:
> Hi,
>
> I develop an ASP.NET application based on a ajax framwework (Visual
> WebGui)
> When I install the application on the client web server, after few
> days, when I try to access the application, the server answers with an
> error message like this
>
> "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 application event log of
> the web server. Please review this log entry to discover what caused
> this error to occur."
>
> This happens ONLY on client server. It never hgappened on my develop
> or test server (where I test the app before deploying)
>
> The solution I found is to stop and restart the WWW service from
> Services control panel
>
> Does anyone knows what is the reason for this. The app is installed
> onto a virtual directory of the main website of the client server.
> Main website is a simple html only, static web. And the server serves
> it ok, even when it gets the error above on my app.
>
> Please help
>
> Thanks
> Bogdan


You should not need to restart the WWW Service to fix this. One only
needs to recycle/restart the appropriate Application Pool.

Is the app using the same or different Application Pool as the main
website.

If they are using the same Application Pool, then when you get
"service unavailable" for ASP.Net application it means that the
ASP.Net application was not fast enough to process its requests. You
should check on the ASP.Net queue size to make sure it is large enough
for your needs to temporary buffer requests, and also profile the
ASP.Net application to make sure it performs well under load -- for
example, make sure it can actually handle concurrent requests.

If they are using different application pools, then you should make
sure that there is no Event Log entry corresponding to the application
pool servicing your ASP.Net application. If there is an event log
entry, please report it -- it likely indicates the cause of your
"service unavailable" issues and you will need to debug it to know
what is causing issues. If there is no event log entry, then do the
same analysis as if they are using the same Application Pool,
mentioned earlier.

"service unavailable" tend to show up only under load. You will have
to show proper load and perf testing on your test servers to be sure
that your code is not the issue. Just because you cannot reproduce it
does not mean your code does not cause it.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: Wierd error on web server

Thanks, I didn't knew abbout application pool. I'm just developer and
had to do just now with installing app on Win2003 server

The app was in default pool, and there was an error in Applications
EventLog

"It is not possible to run two different versions of ASP.NET in the
same IIS process. Please use the IIS Administration Tool to
reconfigure your server to run the application in a separate process."

So I created a separate AppPool and configured my app to run into
that.

I configured the App pool to recycle the worker process ate every 60
min or 1000 requests. Is this ok, the valkues are much smaller that
defaults, but with this I hope if this occurs again, at least the app
will be enabled again in max one hr. It's not the best approach, I'm
sure, but just a trmporary workaround

Is there any better way?

> Is the app using the same or different Application Pool as the main
> website.
>
> If they are using the same Application Pool, then when you get
> "service unavailable" for ASP.Net application it means that the
> ASP.Net application was not fast enough to process its requests. You
> should check on the ASP.Net queue size to make sure it is large enough
> for your needs to temporary buffer requests

How should I do this?

> and also profile the
> ASP.Net application to make sure it performs well under load -- for
> example, make sure it can actually handle concurrent requests.

App is not a heavy load application, and under about 10-20 users
simultaneously all works ok (it is an app intended onbly for internal
users, not a publicly available website)

> If they are using different application pools, then you should make
> sure that there is no Event Log entry corresponding to the application
> pool servicing your ASP.Net application. If there is an event log
> entry, please report it -- it likely indicates the cause of your
> "service unavailable" issues and you will need to debug it to know
> what is causing issues. If there is no event log entry, then do the
> same analysis as if they are using the same Application Pool,
> mentioned earlier.
>
> "service unavailable" tend to show up only under load. You will have
> to show proper load and perf testing on your test servers to be sure
> that your code is not the issue. Just because you cannot reproduce it
> does not mean your code does not cause it.

What suggestions can you give me to locate the issue ?

Thank you
Bogdan


>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //- Ascunde citatul -
>
> - Afi=BAare text =EEn citat -

Re: Wierd error on web server

Temporary workarounds are temporary. I think that recycling every hour
or 1000 requests is aggressive because every recycle causes the next
request to suffer the CLR startup latency as well as loss of any
application-level state. You will need to balance performance with
reliability.

Look up Visual Studio Tools like "Application Center Test" and "F1
Profiler" on how to load and perf test one's code prior to production.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//






On Dec 3, 6:29 am, bz wrote:
> Thanks, I didn't knew abbout application pool. I'm just developer and
> had to do just now with installing app on Win2003 server
>
> The app was in default pool, and there was an error in Applications
> EventLog
>
> "It is not possible to run two different versions of ASP.NET in the
> same IIS process. Please use the IIS Administration Tool to
> reconfigure your server to run the application in a separate process."
>
> So I created a separate AppPool and configured my app to run into
> that.
>
> I configured the App pool to recycle the worker process ate every 60
> min or 1000 requests. Is this ok, the valkues are much smaller that
> defaults, but with this I hope if this occurs again, at least the app
> will be enabled again in max one hr. It's not the best approach, I'm
> sure, but just a trmporary workaround
>
> Is there any better way?
>
> > Is the app using the same or different Application Pool as the main
> > website.
>
> > If they are using the same Application Pool, then when you get
> > "service unavailable" for ASP.Net application it means that the
> > ASP.Net application was not fast enough to process its requests. You
> > should check on the ASP.Net queue size to make sure it is large enough
> > for your needs to temporary buffer requests
>
> How should I do this?
>
> > and also profile the
> > ASP.Net application to make sure it performs well under load -- for
> > example, make sure it can actually handle concurrent requests.
>
> App is not a heavy load application, and under about 10-20 users
> simultaneously all works ok (it is an app intended onbly for internal
> users, not a publicly available website)
>
> > If they are using different application pools, then you should make
> > sure that there is no Event Log entry corresponding to the application
> > pool servicing your ASP.Net application. If there is an event log
> > entry, please report it -- it likely indicates the cause of your
> > "service unavailable" issues and you will need to debug it to know
> > what is causing issues. If there is no event log entry, then do the
> > same analysis as if they are using the same Application Pool,
> > mentioned earlier.
>
> > "service unavailable" tend to show up only under load. You will have
> > to show proper load and perf testing on your test servers to be sure
> > that your code is not the issue. Just because you cannot reproduce it
> > does not mean your code does not cause it.
>
> What suggestions can you give me to locate the issue ?
>
> Thank you
> Bogdan
>
>
>
>
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //- Ascunde citatul -
>
> > - Afi=BAare text =EEn citat -- Hide quoted text -
>
> - Show quoted text -

Re: Wierd error on web server

Thank you

Regards
Bogdan
On 4 Dec, 02:21, David Wang wrote:
> Temporary workarounds are temporary. I think that recycling every hour
> or 1000 requests is aggressive because every recycle causes the next
> request to suffer the CLR startup latency as well as loss of any
> application-level state. You will need to balance performance with
> reliability.
>
> Look up Visual Studio Tools like "Application Center Test" and "F1
> Profiler" on how to load and perf test one's code prior to production.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
>
> On Dec 3, 6:29 am, bz wrote:
>
>
>
> > Thanks, I didn't knew abbout application pool. I'm just developer and
> > had to do just now with installing app on Win2003 server
>
> > The app was in default pool, and there was an error in Applications
> > EventLog
>
> > "It is not possible to run two different versions of ASP.NET in the
> > same IIS process. Please use the IIS Administration Tool to
> > reconfigure your server to run the application in a separate process."
>
> > So I created a separate AppPool and configured my app to run into
> > that.
>
> > I configured the App pool to recycle the worker process ate every 60
> > min or 1000 requests. Is this ok, the valkues are much smaller that
> > defaults, but with this I hope if this occurs again, at least the app
> > will be enabled again in max one hr. It's not the best approach, I'm
> > sure, but just a trmporary workaround
>
> > Is there any better way?
>
> > > Is the app using the same or different Application Pool as the main
> > > website.
>
> > > If they are using the same Application Pool, then when you get
> > > "service unavailable" for ASP.Net application it means that the
> > > ASP.Net application was not fast enough to process its requests. You
> > > should check on the ASP.Net queue size to make sure it is large enough=

> > > for your needs to temporary buffer requests
>
> > How should I do this?
>
> > > and also profile the
> > > ASP.Net application to make sure it performs well under load -- for
> > > example, make sure it can actually handle concurrent requests.
>
> > App is not a heavy load application, and under about 10-20 users
> > simultaneously all works ok (it is an app intended onbly for internal
> > users, not a publicly available website)
>
> > > If they are using different application pools, then you should make
> > > sure that there is no Event Log entry corresponding to the application=

> > > pool servicing your ASP.Net application. If there is an event log
> > > entry, please report it -- it likely indicates the cause of your
> > > "service unavailable" issues and you will need to debug it to know
> > > what is causing issues. If there is no event log entry, then do the
> > > same analysis as if they are using the same Application Pool,
> > > mentioned earlier.
>
> > > "service unavailable" tend to show up only under load. You will have
> > > to show proper load and perf testing on your test servers to be sure
> > > that your code is not the issue. Just because you cannot reproduce it
> > > does not mean your code does not cause it.
>
> > What suggestions can you give me to locate the issue ?
>
> > Thank you
> > Bogdan
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //- Ascunde citatul -
>
> > > - Afi=BAare text =EEn citat -- Hide quoted text -
>
> > - Show quoted text -- Ascunde citatul -
>
> - Afi=FEare text =EEn citat -

Re: Wierd error on web server

Hi,

Can you tell me where can I find Application Center Test?
I look in my VS tools and it isn't there
I have VS 2005 as part or MSDN Professional, but I found on an article
that this is part of VS Enterprise
Can I still find, or use it somehow?

Thanks

On 4 Dec, 02:21, David Wang wrote:
> Temporary workarounds are temporary. I think that recycling every hour
> or 1000 requests is aggressive because every recycle causes the next
> request to suffer the CLR startup latency as well as loss of any
> application-level state. You will need to balance performance with
> reliability.
>
> Look up Visual Studio Tools like "Application Center Test" and "F1
> Profiler" on how to load and perf test one's code prior to production.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
>
> On Dec 3, 6:29 am, bz wrote:
>
>
>
> > Thanks, I didn't knew abbout application pool. I'm just developer and
> > had to do just now with installing app on Win2003 server
>
> > The app was in default pool, and there was an error in Applications
> > EventLog
>
> > "It is not possible to run two different versions of ASP.NET in the
> > same IIS process. Please use the IIS Administration Tool to
> > reconfigure your server to run the application in a separate process."
>
> > So I created a separate AppPool and configured my app to run into
> > that.
>
> > I configured the App pool to recycle the worker process ate every 60
> > min or 1000 requests. Is this ok, the valkues are much smaller that
> > defaults, but with this I hope if this occurs again, at least the app
> > will be enabled again in max one hr. It's not the best approach, I'm
> > sure, but just a trmporary workaround
>
> > Is there any better way?
>
> > > Is the app using the same or different Application Pool as the main
> > > website.
>
> > > If they are using the same Application Pool, then when you get
> > > "service unavailable" for ASP.Net application it means that the
> > > ASP.Net application was not fast enough to process its requests. You
> > > should check on the ASP.Net queue size to make sure it is large enough=

> > > for your needs to temporary buffer requests
>
> > How should I do this?
>
> > > and also profile the
> > > ASP.Net application to make sure it performs well under load -- for
> > > example, make sure it can actually handle concurrent requests.
>
> > App is not a heavy load application, and under about 10-20 users
> > simultaneously all works ok (it is an app intended onbly for internal
> > users, not a publicly available website)
>
> > > If they are using different application pools, then you should make
> > > sure that there is no Event Log entry corresponding to the application=

> > > pool servicing your ASP.Net application. If there is an event log
> > > entry, please report it -- it likely indicates the cause of your
> > > "service unavailable" issues and you will need to debug it to know
> > > what is causing issues. If there is no event log entry, then do the
> > > same analysis as if they are using the same Application Pool,
> > > mentioned earlier.
>
> > > "service unavailable" tend to show up only under load. You will have
> > > to show proper load and perf testing on your test servers to be sure
> > > that your code is not the issue. Just because you cannot reproduce it
> > > does not mean your code does not cause it.
>
> > What suggestions can you give me to locate the issue ?
>
> > Thank you
> > Bogdan
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //- Ascunde citatul -
>
> > > - Afi=BAare text =EEn citat -- Hide quoted text -
>
> > - Show quoted text -- Ascunde citatul -
>
> - Afi=FEare text =EEn citat -