Must I Restart IIS?

[Rick Lemons]

While coding .aspx pages and testing them in IE, I sometimes get the error
"Server Error in '/' Application". There is really no error. I have found
that if I restart IIS and reload the same page everything works. My question
is: Is there another way I can cause IIS to re-load whatever has gone bad
without shutting down all web sites with a restart?

I've tried stopping/starting the site, unloading just the offending
application and those methods don't work.

Thanks

[JPL]

Is the Internal Server Error coming from IIS or ASP.Net?
If its from ASP.Net it will be formatted and have pretty
colors and much coolness ;)

I recommend you find out what is causing the server error
instead of just mitigating with a restart.

JPL

-----Original Message-----
While coding .aspx pages and testing them in IE, I sometimes get the error"Server Error in '/' Application". There is really no error. I have foundthat if I restart IIS and reload the same page everything works. My questionis: Is there another way I can cause IIS to re-load whatever has gone badwithout shutting down all web sites with a restart?

I've tried stopping/starting the site, unloading just the offendingapplication and those methods don't work.

Thanks
.

[Andrea Williams]

I have encountered the same problem. I don't know what caused it either....
As I am relatively new to ASP.NET, I don't know how to troubleshoot an issue
like this, so I restarted my IIS too. All the sudden I was getting errors
that weren't there before and couldn't find a cause programmatically.
rebooted, errors went away. It's only happened once so far.....

I'll be interested to see what others have found.

Andrea
"Rick Lemons" <ri***@cdldata.com> wrote in message
news:uN**************@TK2MSFTNGP11.phx.gbl...

While coding .aspx pages and testing them in IE, I sometimes get the error
"Server Error in '/' Application". There is really no error. I have found
that if I restart IIS and reload the same page everything works. My question is: Is there another way I can cause IIS to re-load whatever has gone bad
without shutting down all web sites with a restart?

I've tried stopping/starting the site, unloading just the offending
application and those methods don't work.

Thanks

[Hans Kesting]

"JPL" <jp*****@hotmail.com> wrote in message
news:02****************************@phx.gbl...

Is the Internal Server Error coming from IIS or ASP.Net?
If its from ASP.Net it will be formatted and have pretty
colors and much coolness ;)

I recommend you find out what is causing the server error
instead of just mitigating with a restart.

Yes, but sometimes finding this error can be very difficult:
I frequently get errors from the asp.net system that first say there is
an error in machine.config (I have *never* changed anything there)
and lower down that the system could not access some dll of my application.
This dll usually has not changed since the last succesful run.
Sometimes a rebuild "fixes" this problem. This seems to me that the
error is not in *my* code but somewhere in the .Net system
or the operating system.

If the rebuild doesn't fix it, then I usually close Studio, kill
aspnet_wp.exe
process and remove all my dll's. Then a complete rebuild and then
it works (usually).

Hans Kesting

[Rick Lemons]

It is an ASP.NET error. I get the pretty color page. There is no error to
find out anything about. I've looked and looked and being unable to find
anything I re-started IIS and it goes away. Sometimes I can make a change
that could not possibly cause an error and I get the general error page on
the next load. I simply re-start IIS and reload the same page (with no
change) and it's OK. As a matter of fact, once I get this non-error error, I
can't even load any .aspx pages. Even ones that I haven't touched in days
give the same error page. Once IIS is reloaded, all the pages work again.
It's like things get out of sync or something.

There is no error to fix, I have customErrors mode="On". I think the error
is even before it checks this parameter. Most error give me a description
but not this type.
"JPL" <jp*****@hotmail.com> wrote in message
news:02****************************@phx.gbl...

Is the Internal Server Error coming from IIS or ASP.Net?
If its from ASP.Net it will be formatted and have pretty
colors and much coolness ;)

I recommend you find out what is causing the server error
instead of just mitigating with a restart.

JPL

-----Original Message-----
While coding .aspx pages and testing them in IE, I

sometimes get the error

"Server Error in '/' Application". There is really no

error. I have found

that if I restart IIS and reload the same page everything

works. My question

is: Is there another way I can cause IIS to re-load

whatever has gone bad

without shutting down all web sites with a restart?

I've tried stopping/starting the site, unloading just the

offending

application and those methods don't work.

Thanks
.

[Rick Lemons]

Yes. I get that a lot too. Sometimes I have to do a complete rebuild instead
of just building the member I'm working on. When that doesn't work an IIS
restart usually clears it up.
"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:eX**************@TK2MSFTNGP12.phx.gbl...

"JPL" <jp*****@hotmail.com> wrote in message
news:02****************************@phx.gbl...

Is the Internal Server Error coming from IIS or ASP.Net?
If its from ASP.Net it will be formatted and have pretty
colors and much coolness ;)

I recommend you find out what is causing the server error
instead of just mitigating with a restart.

Yes, but sometimes finding this error can be very difficult:
I frequently get errors from the asp.net system that first say there is
an error in machine.config (I have *never* changed anything there)
and lower down that the system could not access some dll of my

application. This dll usually has not changed since the last succesful run.
Sometimes a rebuild "fixes" this problem. This seems to me that the
error is not in *my* code but somewhere in the .Net system
or the operating system.

If the rebuild doesn't fix it, then I usually close Studio, kill
aspnet_wp.exe
process and remove all my dll's. Then a complete rebuild and then
it works (usually).

Hans Kesting