How to Properly Configure ODBC DSN for DB2 access on Windows 2003 x64 using IIS
Posted on 2009-04-03
Trying to configure the ODBC DSN (using IBM DB2 ODBC Driver v 9.05.00.808) to connect an IIS Crystal Reports report to a DB2 database. The server is a Windows 2003 Standard x64 with IIS 6.0 installed fully patched. DB2 is v8.1 (or 8.5) running on Linux.
We configure the DSN and test it and it says it Connected Successfully (both as x32 and x64 bit) BUT we get the following error in the Application Log:
The description for Event ID ( 4 ) in Source ( DB2 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:
2009-04-03-07.42.26.186000 Instance:DB2 Node:000
PID:3316(odbcad32.exe) TID:3604 Appid:none
RAS/PD component pdLogInternal Probe:20
ADM14000E DB2 is unable to open diagnostic log file
"C:\PROGRA~1\IBM\IBMDAT~1\db2\db2diag.log". Run the command "db2diag -rc %s"
to find out more.
We have been unalbe to locate this "db2diag" program anywhere so this is all we get.
Since the test ran fine in the ODBC Administrator, we tried running our reporting tool in IIS and get the same error message again AND it cause a lock up in IIS where the application pool has to be restarted after you KILL the PID for that service.
This is only my second time using ODBC stuff but first time I'm having to connect to a DB2 database. Any assistance in either websites, online books, or just thoughts would be appreciated. OH please don't send me to IBMs site either unless you know its 100% workable. I've spent the last 2 days combing the beast and I've pretty much given up on them.