Praveen M's Blog

Error: "Class not registered"

PRAM — Tue, 31 Mar 2009 07:18:00 GMT

We have an SSIS package which connects to FoxPro Database. When we run the package, it gets the data from FoxPro database, Sorts it and uploads the data back to the SQL Server. The package works fine when we try to run through BIDS or from Command Prompt (DTExec). However when we schedule the package as a JOB it fails with the below error message

Date 3/1/2009 10:39:00 PM
Log Job History (****)

Step ID 1
Server ****
Job Name SSISTest
Step Name Step1
Duration 00:00:02
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: . ...ersion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started: 10:39:00 PM
Error: 2009-03-01 22:39:01.82     Code: 0xC0202009
Source: Package Connection manager "\\SSISTest\Foxpro"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available.

Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error
Error: 2009-03-01 22:39:01.82 Code: 0xC020801C Source: Data Flow Task FoxPro [1]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "\\SSISTest\Foxpro" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error
Error: 200... The package execution fa... The step failed.

"Class not registered" usually means that an activex control in not registered.

Make sure you have installed Microsoft OLE DB Provider for Visual Foxpro on the server. If you have not installed then you can download the provider from the below link
Microsoft OLE DB Provider for Visual FoxPro 9.0 https://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en

When you install Microsoft Visual FoxPro, the installation process appears to default to 'Just Me', which would only install the provider for the user doing the installation. When we log in to the machine as the user that performed the installation using the 'Just Me' option, we can run the package in BIDS without a problem. However, when the package is configured to run as a job using a different user, the job fails with the above error.

To resolve this issue uninstall the Microsoft Visual FoxPro Oledb Provider from Add/Remove Programs. Then, perform the installation again, ensuring that the 'Everyone' option is chosen.

HTH

Tables/Procedures are not listed under Data Connections in a .net application connecting to DB2 Data Source

PRAM — Thu, 12 Feb 2009 08:00:00 GMT

I was working with a Customer where he has developed a Windows application connecting to DB2 Data Source using IBM iSeries OLE DB Provider. The connection was successful. When we expand the tables/Procedures under data connections we don’t see any objects listed. No Error Messages as well!

After working for some hours we came to know that the schema information was omitted in the connection string.

Here is how you can resolve this issue.

1. Create a new Data Connection or modify your existing connection

2. Click on Change button under add Connection wizard

3. Select from Data Source and Choose .Net Data Provider for OLE DB

4. Click OK

5. Select IBM DB2 UDB for iSeries IBMDASQL OLE DB Provider

6. Enter your User name and Password

7. Check Allow Saving Password and select the Initial catalog

8. Click on Advanced Button

9. Under Default Collection you need to type the Database name (Schema information) which is present in your DB2 Database.

10. Click OK à Test connection à Click Ok

11. Now Right Click on the Data Connection and click Refresh.

12. Expand tables. Ahh.. You will see all the tables listed!

Screenshots

Invalid use of schema or catalog for OLE DB provider "SQLNCLI" for linked server ""

PRAM — Mon, 09 Feb 2009 19:09:00 GMT

We have a Linked Server from SQL Server 2005 instance to SQL Server 2000 instance. The linked server works fine. However if we try to Query a Linked Server through Four-Part name then it fails with the below error message

SELECT *

FROM LinkServer.Northwind.dbo.Shippers

Error Message

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "SQLNCLI" for linked server "" reported an error. The provider did not give any information about the error.

Msg 7312, Level 16, State 1, Line 1

Invalid use of schema or catalog for OLE DB provider "SQLNCLI" for linked server "". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema..

Inorder to resolve this, check if "zero level only" property for SQLNCLI oledb provider is set to 0. If it

is 1 (or ON), 7399 error will occur. Make sure its unchecked.

To set the "zero level only" property, go to

SQL Management Studio-> "Server Object" -> "Linked Servers" -> "Provider"

right click on “SQLNCLI” and go to property and uncheck the “zero level only” property

click on “OK” and restart the SQL Server service.

You can also change this setting through registry

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Providers\SQLNCLI

LevelZeroOnly

If we set it to 1 then only level 0 OLE DB Providers are allowed. If it is 0 (default), all levels of OLE DB provider are allowed. So the value specifies whether all OLE DB providers are supported or just those that are compliant with the level 0 OLE DB interface.

The other workaround is to use OPENQuery instead of Four-Part Query