|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Generate data entry and reporting .NET Web apps in minutes, straight from your database. Read our FREE whitepaper “Build Web 2.0 Applications Without Hand-Coding” Download now! |
|
#1
|
|||
|
|||
|
I am running a stored procedure on a MS sql server 2000 that queries (retrieves info) from several AS400 (9406 925 v5r2m0) files. after running about two weeks I get this error. We currently reboot the sql server and the problem goes away. it only seems to effect my app. other stored procreures on same sql server accessing other data files on the as400 seems to work.
OLE DB provider 'MSDASQL' reported an error. [OLE/DB provider returned message: [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed] [OLE/DB provider returned message: [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=12 - CWB0999 - Unexpected error: unexpected return code 12] OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x80004005: ]. |
|
#2
|
||||
|
||||
|
I don't have any AS400's so I don't know if I will be of much help. IBM just released a new iSeries Access for Windows service pack this month. Are you patched to the latest release? Or are your running on an older (possibly buggier) version?
http://www-1.ibm.com/servers/eserve...cess/sphist.htm |
|
#3
|
|||
|
|||
|
yes we are current.
Quote:
yes we are current on patches |
|
#4
|
|||
|
|||
|
DID YOU EVER FIND A RESOLUTION i AM HAVE THE SAME ERROR WITH ACCESS
I Am Have Similar Problems With My Application And Access Do You Ever Resolve The Problem?
|
![]() |
| Viewing: Dev Shed Forums > Databases > DB2 Development > [IBM][iSeries Access ODBC Driver]Communication link failure. |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|