Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How can I resolve "Runtime Error 3146 ODBC Call Fail

Status
Not open for further replies.

btturner

Programmer
May 17, 2001
175
US
QUESTION: How do I modify ODBC driver configuration???

--> After exactly "5" minutes, I am receiving this error msg on my ACCESS screen: RUNTIME ERROR 3146 ODBC CALL FAILED

Process includes:
--> I'm invoking a SQL 2K stored procedure REMOTELY from an ACCESS command button

--> I connect OK to the remote server & the SP runs to successful completion (SP runs for approx 30 minutes)

(fyi, the SQL SP invokes xp_cmdshell, then runs DTSRUN api successfully)
 
is it possible, that this runtime-error occures if I am not able to write to the database (no write-rights)? Could that be?
txs bart3
 
3146 is a generic failure to connect message. You really need to examine the complete error message in order to know the cause. It is likely that the problem is caused by a remote timeout on the server. The default timeout is 300 minutes which is exactly 5 minutes.

Excuting a stored proc to execute a package via xp_cmdshell and DTSRUN seems like a complex way to perform this. Why not executing the package from VBA in Access? See the article at SQLDTS.com for instructions and samples of executing packages from VB.

Terry L. Broadbent - DBA
Computing Links:
faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions in the SQL Server forum. Many of the ideas apply to all forums.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top