Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Run-time error '3246', Clients cannot connect to database

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2003-05-15 : 07:24:18
Greg writes "I am running SQL Server 2000(SP2) on a Win2k Server(SP3)box. I am having trouble with end users being able to login on Monday mornings. When they try and log into the database they get this error: "Run-time error '3246': Connection object cannot be explicitly closed while in a transaction". When they hit ok on that error another error pops up that states: "Run-time error'-2147217871 (80040e31)':[Microsoft] [ODBC SQL Server Driver]Timeout Expired". As I stated earlier this error only happens on Monday mornings. The only thing that I have found that works is restarting the SQL Services, then the users can log into the database. Any help would be greatly appreciated."

franco
Constraint Violating Yak Guru

255 Posts

Posted - 2003-05-15 : 08:10:16
Try to investigate with profiler to find if there is some problem with the application.
Seems like there is a transaction not properly closed by your app.
HTH

Franco
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-05-15 : 12:36:00
You probably have a fairly busy server on Monday mornings. You should analyze what is occurring with SQL Profiler as franco mentioned. From this, you will be able to tell which queries are the culprits. From that, you will probably need to make code changes or add indexes.

Tara
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2003-05-15 : 16:36:36
Sounds like a similar problem, or is that you?

http://www.sqlmag.com/Forums/messageview.cfm?catid=3&threadid=15405



Brett

8-)
Go to Top of Page
   

- Advertisement -