Troubleshooting installation, configuration, or operation problems

This section describes how to resolve problems that you might encounter when installing, configuring, or using HCL Informix® OLE DB Provider.

Tip: If the problem you are experiencing does not match one listed here, or the proposed resolution does not work for you, contact Technical Support.

HCL Informix OLE DB Provider not registered
When you attempt to connect to the HCL Informix data source, a message says that HCL Informix OLE DB Provider is not registered.
Class not registered
When you attempt to connect to the HCL Informix data source, the message Class not registered opens.
Cannot establish a connection
You cannot establish a connection.
Database not found
A connection attempt fails; a message says that the database is not found.
The oledbversion table not found
When the application attempts to fetch schema information, a message says that the table oledbversion was not found.
Nonalphabetic MBCS characters generate syntax errors
When you issue an SQL statement against an MBCS database (for example, SJIS-S), the HCL Informix server returns a syntax error if the statement includes table or column names containing MBCS characters not classified as alphabetic in the locale.
Server-side cursor fails to update records
If you open a server-side cursor (adUseServer) on an SQL command (adCmdText), attempts to perform an update fail with an ADO provider not capable error.
Attempt to use provider from web server or other server fails
An attempt to use OLE DB Provider from the web server or from a process that runs as a distinct user fails. The typical error message that is displayed is ADO cannot find the provider.
Cannot connect to transaction manager
A connection attempt fails, a message says that the application cannot connect to the transaction manager.
Driver not found error
When you attempt to run tracing, the server returns an error stating that the driver cannot be not found and might not be installed properly.
Errors for stored procedures
When a stored procedure with a return value is run using theHCL Informix OLE DB Provider, errors returned by the procedure are not returned to the application.
Known issues with OLE DB .NET bridge
In a .NET application, when calling stored procedures that take no parameters, the OledbCommand attribute "CommandType" does not function as expected.

Parent topic: Informix OLE DB Provider Guide