Im003 Native Error Code
Contents |
make sure that
Specified Driver Could Not Be Loaded Due To System Error 126 Oracle Odbc Driver
the spelling is correct.Note: Most addresses are case sensitive. For information specified driver could not be loaded due to system error 8 sage on IBM offerings, start from the IBM homepage. For information on printing systems, start from the Infoprint Solutions
Specified Driver Could Not Be Loaded Due To System Error 126 The Specified Module Could Not Be Found
Company homepage.* For information on ThinkPad notebooks, ThinkCentre desktops and other PC products, start from the Lenovo homepage.* Search the IBM Web site. Get assistance This option lets you send an information request and tell us specified driver could not be loaded due to system error 127 about a broken link. You will receive an e-mail from us to help you find what you need. Requested uid value cannot be empty * Links notated by a grey asterisk (*) will take you to web sites for the following companies that sell former IBM products. Printing systems are now products of InfoPrint Solutions Company. ThinkPad notebooks, ThinkCentre™ desktops and other PC products are now products of Lenovo. Self-help resources Locate your IBM Easy Access site Support & downloads Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
OpenLink Lite; Oracle 8i; ClearQuest; Oracle 9i; 1214987 Technote (troubleshooting) Problem(Abstract) This technote how to resolve the error: SQLDriverConnect error 126, that can occur when using the IBM Rational ClearQuest 2003.06.12 (or earlier)
Sqlstate Im003
Web server. Cause Using Oracle as the back-end database and logging in through the ClearQuest
Specified Driver Could Not Be Loaded Due To System Error 126 (sql Server)
Web, can cause the following error to appear:
Unable to logon to the ORACLE database
The vendor error im003 specified driver could not be loaded due to system error 1114 error message was:
SQLDriverConnect: RETCODE=-1,State=IM003,Native Error=160
Specified driver could not be loaded due to system error 126
(OpenLink Lite for Oracle 8i (32 Bit)).
Logon Again
Note: It is possible to login http://www.ibm.com/support/docview.wss?crawler=1&uid=swg21570765 to ClearQuest on the Web server computer using the native ClearQuest client. There are a few known problems related to this error: The Microsoft Windows IUSR account for the IIS server needs to be in the administrator group. Registry permissions on the Oracle directory are too restrictive. Allow IIS to control password should be cleared and the password for the anonymous user may need to be updated. The command is trying to use the http://www.ibm.com/support/docview.wss?uid=swg21214987 OpenLink Lite for Oracle 7 instead of the OpenLink Lite for Oracle 8i or later Resolving the problem VERIFY WEB SETUP Using the Rational Software Server Products Installation Guide under the section "Configuring ClearQuest Web", verify that ClearQuest web server is configured correctly. CHECK IUSR ACCOUNT Add the Windows IUSR account to the local web servers administrators group. Open the Control Panel and select Administrator Tools > Computer Management > Local Users and Groups > Groups and double click Administrator. Add the IUSR account to the Administrator group. Re-start IIS VERIFY REGISTRY DIRECTORY PERMISSIONS Modify the Windows registry Open the registry editor (Start > Run and type regedit) on the web server. Go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI Go to the Security menu > permissions. Make sure that the IUSR and Everyone accounts have full control to the Oracle directory. Restart the server. ALLOW IIS TO CONTROL PASSWORD SETTINGS Clear Allow IIS to control password do the following: 1. Go to the web server and open IIS 2. Right click your virtual directory and go to properties 3. Go to the Directory Security tab 4. Under Anonymous access and authentication control, click Edit. 5. Under 'Anonymous access,' click 'Edit' again. 6. Clear the box that says 'Allow IIS to control password.' Now to update the password for the anonymous user, do the foll
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker http://stackoverflow.com/questions/10383822/odbc-lib-specified-driver-could-not-be-loaded Support
MQSeries.net Forum Index » WebSphere Message Broker Support » Unable to create broker using 64 bit ODBC driver Unable to create broker using 64 bit ODBC driver « View previous topic :: View next topic » Author Message CT Posted: Sun Jun 11, 2006 10:04 pm Post subject: Unable to create broker using 64 bit ODBC specified driver driver NewbieJoined: 05 Apr 2002Posts: 3 I'm upgrading from MQSI 2.1 to WBIMB Ver 6 running on: ·AIX 5.3 ML 4 64 bit kernel ·DB2 8.1 FP 11 ·MQ 5.3 CSD 12 ·WBIMB 6 CSD 1 Everything works fine if I use Db2 and ODBC 32 bit I'm trying now to run WBIMB on 64 bit but all my trials were failed. The procedure I followed to specified driver could switch to WBIMB 64 bit is: 1. upgrade db2 instance to 64 bit by the command db2iupdt –w 64 2. configure ODBCINI64 to point to a copy of odbc64.ini after configuring that copy by my new DSN (Now we have old 32 bit DSN in ODBCINI and the new 64 bit DSN in ODBCINI64) 3. execute the .profile 4. I decided to create a new broker using an existing database, but I got the following error: **************************** BIP2321E: Database error: ODBC return code '-1'. The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error. Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration. BIP2322E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Data source name not found and no default driver specified''. The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Data source name not founhere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ODBC lib Specified driver could not be loaded up vote 2 down vote favorite I am trying to install ODBC drivers and I am running into brick walls. [root@Crux pkg]# isql -v [IM002][DataDirect][ODBC lib] Data source name not found and no default driver specified [ISQL]ERROR: Could not SQLConnect [root@Crux pkg]# isql -3 SUBS2A [IM003][DataDirect][ODBC lib] Specified driver could not be loaded [ISQL]ERROR: Could not SQLConnect My INI files are as follows; odbcinst.ini [ProgressOpenEdge] Description = ODBC for Progress OpenEdge Driver = /usr/dlc/odbc/lib/pgoe1023.so ;Setup = /usr/dlc/odbc/lib/pgoe1023.so FileUsage = 1 odbc.ini [SUBS2A] Driver = ProgressOpenEdge Description = Fail DatabaseName = SUBS PortNumber = 4000 HostName = 192.168.1.2 LogonID = SYSPROGRESS Password = SYSPROGRESS APILevel = 1 ConnectFunctions = YYN CPTimeout = 60 DriverODBCVer = 03.50 FileUsage = 0 SQLLevel = 0 UsageCount = 1 ArraySize = 50 DefaultLongDataBuffLen = 2048 DefaultIsolationLevel = REPEATABLE READ StaticCursorLongColBuffLen = 4096 [ODBC] InstallDir = /usr/dlc/odbc Trace = 0 TraceFile = odbctrace.out TraceDll = /usr/dlc/odbc/lib/odbctrac.so UseCursorLib = 0 I have already made sure all dependencies are loaded properly via ldd. UPDATE OUTPUT OF: strace isql -v http://pastebin.com/tXFY4vVt OUTPUT OF: strace isql -3 SUBS2A http://pastebin.com/Yu5e54mR OUTPUT OF: /tmp/odbctrace.out http://pastebin.com/0kgvNdWv Thanks linux odbc drivers openedge progress-db share|improve this question edited May 10 '12 at 14:11 asked Apr 30 '12 at 12:36 PolishHurricane 1,61651839 Never mind. I was suffering from a brain-cramp. –Tom Bascom May 3 '12 at 10:33 Have you tested network connectivity on the specific TCP port ? For instance with nc 192.168.1.2 4000 –Yves Martin May 4 '12 at 13:25 check the drivers for compatibility issues with your system's a