Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2012-10-05T13:57:18Z by SystemAdmin
SystemAdmin
SystemAdmin
17917 Posts
ACCEPTED ANSWER

Pinned topic Microsoft OLE DB Provider for ODBC Drivers error '80004005'

‏2012-10-05T10:54:57Z |
Windows version : Windows Server 2008 R2
DB2 UDB version : DB2 v 9.5 fixpack 4 (64 bit)

I am facing problem with Microsoft OLE DB Provider for ODBC in my dev environment.

<%
Dim adoCon
Set adoCon = Server.CreateObject("ADODB.Connection")
adoCon.Open "Driver={IBM DB2 ODBC DRIVER};Database=XXXXXDB;HOSTNAME=LOCALHOST;PORT=50000;PROTOCOL=TCPIP;UID=DB2ADMIN;PWD=xxxxxxxxxxxxx*"
%>

Simple ASP program to connect database hitting error because of Microsoft OLE DB Provider for ODBC problem.

This program has worked up to yesterday since a year.

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
MicrosoftODBC Driver Manager Data source name not found and no default driver specified
/xxxxxxxxxxxxxxxxx/connection.asp, line 4

Please let me know how to resolve this issue.
I am reproduced the same issue with EXcel using Microsoft OLE DB Provider for ODBC.

I am able to connect database with 'IBM OLE DB Provider for DB2 - DB2COPY1' .

Opened Excel ->Data->Import External Data->Import Data->New Source ->Other/Advanced
Select Microsoft OLE DB Provider for ODBC

But in case of 'Microsoft OLE DB Provider for ODBC' hitting the following error message.

Test Connection failed because of an error in initializing provider.
MicrosoftODBC Driver Manager Data source name not found and no default driver specified

IT is working fine on my production environment.

Thanks,
Manoj
Updated on 2012-10-05T13:57:18Z at 2012-10-05T13:57:18Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    17917 Posts
    ACCEPTED ANSWER

    Re: Microsoft OLE DB Provider for ODBC Drivers error '80004005'

    ‏2012-10-05T13:57:18Z  in response to SystemAdmin
    After re-installed IBM thin client, it is working fine now.