Transports and Interfaces: Siebel eBusiness Application Integration Volume III > Using Siebel OLE DB Provider >

Troubleshooting OLE DB

This section describes common connection problems when using OLE DB. Consult the Windows Event Log to view the details on other OLE DB and Siebel OLE DB Provider errors.

Error

Initialization of the data source failed with following error:

Check the database server or contact your database administrator. Make sure the external database is available, and then try the operation again. If you see this message again, create a new data source to connect to the database.

Cause

You have selected an invalid .cfg file in your Connection string or the .cfg file you have selected has not been updated to support OLE DB.

Sample Problem Code

QueryType=OLEDB
Version=1
Connection=Provider=SiebelOLEDB.Provider.1;Persist Security Info;Data Source="c:\siebel\client\bin\enu\uagnet.cfg,ServerDataSrc";
CommandType=Default
CommandText= select * from LabRowset

Solution

Check to make sure you have set the Security Info parameter in your connection string.

Error

The query did not run or the database table could not be opened and you received the following error:

Check the database server or contact your database administrator. Make sure the external database is available and has not been moved or reorganized, then try the operation again.

Cause

The database name in your .cfg file is not set correctly or the name of the table in your query is incorrect.

Sample Problem Code

QueryType=OLEDB
Version=1
Connection=Provider=Siebel OLEDB Provider.1;Persist Security Info=True;Data Source="c:\siebel\client\bin\enu\siebel.cfg,ServerDataSrc";
CommandType=Default
CommandText= select * from LabRowset

Resolution

Check to make sure that the Provider parameter is set correctly and also that the table used for the CommandText is a valid table.

Error

SQL Query Analyzer error message. The following error is generated in the SQL Query Analyzer when the Object Manager on the Server is not initialized:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SiebelOLEDB.Provider.1' reported an error. Provider caused a server fault in an external process.

Cause

This error typically occurs when Object Manager is not initialized or may be related to SQL Server caching of the OLEDB datasource or to the servers not being successfully restarted.

Sample Problem Code

n/a

Resolution

Restart the servers.

Error

Test connection failed because of an error in initializing provider. 0x80040e73

Cause

Failure to set the DataSource property in the [Siebel] section correctly generates this error when testing the connection. You also get an entry in Windows Event Log regarding this failure.

Sample Problem Code

n/a

Resolution

Check your connection in the Siebel.UDL file and test it by providing the correct username and password. Also in the .cfg file, make sure the DataSource property in the [Siebel] section is set to the correct data source—for example, set to Sample for Sample database.

Problem

Receiving "Could not process object select * from GPTest2" error message

Description

If you did not make the custom OLE DB available to the Siebel Server Object Manager, you see the following error when you run the query:

Sample Problem Code

Solution

Make sure that you have copied the latest .srf to the Server\objects directory and have restarted the server. These actions make the custom OLE DB available to the Siebel Server Object Manager.

Problem

Provider "SiebelOLEDB.Provider.1 supplied inconsistent metadata for a column. Metadata information was changed at execution time"

Description

The length of the columns in the two applications does not match.

Sample Problem Code

Solution

When SQL Server reports inconsistent metadata, the user can modify the field length in the rowset definition in Siebel Tools.

Problem

Unable to query SODP using MSSQL Query Analyzer

Description

When a connection is established with one type of connection string and then another connection is attempted with a different type of connection string, it fails on the second connection attempt, and generates the following error message:

Error message with MSSQL: OLE DB provider "siebelOLEDB.Provider.1"reported an error. Provider caused a server fault in an external process.

Sample Problem Code

n/a

Solution

Restart the MS SQL Server.