sounds like the recompile/copy is simply resetting the app, or rather
restarting it.
What OS? 2003? try restarting the app pool if it is, just to see if that
fixes it.
There may be something with connections, pooling, not closing, etc, that may
be the source as well.
You say you dont get any error at all though huh? are you doing any
overriding to stop the error from showing?
--
Curt Christianson
Site & Scripts:
http://www.Darkfalz.com
Blog:
http://blog.Darkfalz.com
"POL8985" <pol8985@njit.edu> wrote in message
news:1107285734.468874.208710@f14g2000cwb.googlegr oups.com...[color=blue]
> The application is built using ASP.Net in VS.Net 2003 and uses a SQL
> server database.
>
> About three times a day, the ASP.Net application fail to see the
> database, yet it will throw no errors. This results in users not being
> able to log in (they receive invalid user/password messages generated
> by the application). Additionally, because the application validates
> user entries against the SQL Server database, each transaction a user
> attempts to perform will fail.
>
> What's strange is from the IIS server which hosts the application, I
> can use Query Analyzer to get into the DB!
>
> The quickest way to resolve this has been to re-compile the SLN in
> VS.Net 2003 and copy everything over to the production \bin folder.
>
> Does anyone have any ideas? This is a huge problem when 20+ users need
> to log off and log back on three times a day.
>
> Thanks:
>
> Pat
>[/color]
