|
-
Sep 6th, 2000, 09:29 AM
#1
Thread Starter
Fanatic Member
I am invoking a stored proc (using ADO)
and the error returned is "TimeOut Expired!"
What's going on? and what can I do to fix it???
Your help is sincerely appreciated...
-
Sep 6th, 2000, 10:00 AM
#2
I am not sure how it worked but i fixed this problem a couple of days back in one of my applications by closing an open recordset involving some of the tables referenced by the stored proc.
-
Sep 6th, 2000, 11:02 AM
#3
Frenzied Member
Either your command (most likely) or your connection is timing out. Luckily, you can set both:
dim g_Db as new ADODB.Connection
g_Db.CommandTimeout = 1800 'about 30 mins
g_Db.ConnectionTimeout = 1800
-
Sep 6th, 2000, 03:16 PM
#4
Thread Starter
Fanatic Member
Thanks a lot both
Thanks to you both...
I'll look into both possibilities
Thanks a mil
-
Sep 7th, 2000, 08:38 AM
#5
Thread Starter
Fanatic Member
Thanks
Both of you were right...
There was at least one instance of each
In one case, a recordset had access to a table
(and locked it) and access was denied to another
instance trying to access it... (Indefinite postponement
situation known as 'deadly embrace or deadlock'
Clearing it out worked
The other instance... (I did increment the timeout
for both the connection and the command to 3600
and the 2 cases where it was failing was fine)
Thanks again...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|