Description: A C# web app accesses a stored proc to do a simple insert (several times per minute). Lately there has been an issue where the app times out. Then you look at the database and there are up to 100 connections trying to access the stored proc and there are Latch_EX (exclusive latches) on all but one of those connections accessing the proc.
The odd thing is that nothing ever hits the SQL error log. Only the following error makes it to the windows event log:
12/6/2005 7:38 PM : ERXPPEV2: TRID='426733233:550' LogRecord.logwrite() dbo.ppe2_insert_edit_log
Exception=[System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at com.erxnetwork.erxedit.LogRecord.logwrite()]
Are there any known bugs between ADO.Net and SQL 2000 that might explain this or is this issue a memory or I/O issue with the db server as most articles I have found suggest...those articles however note specific errors that can been seen in the SQL Error log...can't seem to find a similar issue to mine.
If anyone has any ideas, they would be greatly appreciated.
Thanks,
Bryan