I've been trying to establish a
OLEDB Connection to an
Informix Dynamic Server. (Version IBM Informix Dynamic Server Version 12.10.FC12WE)
A program, which will be used by my company, requires
OLEDB and doesn't support
ODBC. The colleague,who is currently tasked with managing the implementation, has a lot of other work piled up and so the implementation will be delayed. In the meantime, I've been tasked to figure out how to properly configure the Windows 10 Client PC (which will run the program) for the connection. I have very little experience with databases, so I've searched for about 2 weeks for answers in various documentations and forums. So far, I had mixed success.
What has already been done:
coledbp.sql- script has been run against the
sysmastertable on the database
Informix Client SDKand
Microsoft Data Access Componentshave been installed on the Client PC.
setnet32the registry entries for
host:porthave been set.
- The driver
ifxoledbchas been registered.
32-Bit) have been created and tested (they work fine).
For all my tests I've been using the Connection String:
"Provider=ifxoledbc;Data Source=mydatabase@myserver;User ID=myuser;Password=mypassword;
First I tried to test the connection with an
.udl-File. I select the
IBM Informix OLE DB Provider and enter the data source and userdata. When I test the connection I get an Error like:
"Initialisation of the provider failed. Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done."
From what I could find, there are many possible reasons for this error, and I don't know if can get a more specific error message somehow.
Microsoft OLE DB Provider for ODBC Drivers and the
ODBC-datasource for the Server the test connection worked.
In Microsoft Excel (
32-Bit) I also tried both the first mentioned Connection String and the Connection String, which is built when entering the infos in the
.udl settings. Same Error with both cases.
For my next test I used a
.vbs - script, which was presented in the
IBM Informix Developers Handbook:
On Error Resume Next set conn=createobject("ADODB.Connection") conn.connectionstring = "Provider=ifxoledbc;DataSource=mydatabase@myserver;UserID=myuser;Password=mypassword;" conn.open If Err Then WScript.Echo "Error!! Open"+conn.Errors(0).Description Else WScript.Echo "Connected" conn.close end if
This results once again results in the "multi-step"-Error.
The last thing I tried was using the
Rowset Viewer of
MDAC. I used the exact same input as with the
.udl - File. But to my surprise it managed to connect! (It returned the error "Unknown Interface", but still worked) It correctly read the entries I set with the
setnet32-Tool. (I checked this by temporarily removing one of the Entries, which resulted in an additional error and no connection)
Now I have a few questions:
- Is there anything additional to configure on the Client PC?
- How does the Viewer succeed, where every other test fails?
- Is there any way to get a more accurate error code?
- Are there major flaws in my tackling of the problem?
I appreciate every suggestion anybody can give me.