P
POL8985
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
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