SSIS, "Class Not Registered" error...deployment or permissions issue?

Question

Post reply

SSIS, "Class Not Registered" error...deployment or permissions issue?

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply

tan110 Newbie Points: 0 More actions · Answer 1

Where in package properties, do I set run In 64bit = false?

Arcturus Newbie Points: 0 More actions · Answer 2

After going thru the long list of replies I tried to run it thru CMD

I modified the job to use cmdexec step and : C:\Program Files (x86)\Microsoft SQL Server\90 \DTS\Binn\DTExec.exe /f "Package Path" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW

And it executed just like you are having a piece of Cake.

Thanks for the Inputs.

tvramanadhan Newbie Points: 0 More actions · Answer 3

Hi I am Ramesh from Chennai, India.

I am also facing the same problem but I am using data source as Excel file. Error displayed as below...

FirstLine:

"[Excel Source [17]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009"

SecondLine:

[Connection manager "Excel Connection Manager"] Error: 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".

Can any one help me....?:hehe:

hubertp2@sbcglobal.net Newbie Points: 0 More actions · Answer 4

Thanks for the info on set 64bit run to false, that fixed my SSIS issues!

amirhh2000 Newbie Points: 0 More actions · Answer 5

First of all I hate SSIS2005 ... it has too many bugs ... (preferably use 2008R2 or 2012)

Things you can check are as follows:

1. Make 64bit false

2. Delay validation = False (in the body of package and on all objects)

3. EncreptionMethod = SensitiveWithPassword

4. If you changed number 3 reopen your data connections and re enter username password to be encrypted with the new method.

5. SQL Agent Service account has access to your Excel/Access datafile location

6. Create the SQL Job from SSMS2005 not SSMS2008/2012

7. be patient ...

Cheers

Amir

zhasan Newbie Points: 0 More actions · Answer 6

I am able to run the SSIS package just fine by itself, and I am using my sql account. The issue happens when I add it to the SQL server agent to execute, that's when my package fails.

Any thoughts?

amirhh2000 (3/24/2014)
First of all I hate SSIS2005 ... it has too many bugs ... (preferably use 2008R2 or 2012)
Things you can check are as follows:
1. Make 64bit false
2. Delay validation = False (in the body of package and on all objects)
3. EncreptionMethod = SensitiveWithPassword
4. If you changed number 3 reopen your data connections and re enter username password to be encrypted with the new method.
5. SQL Agent Service account has access to your Excel/Access datafile location
6. Create the SQL Job from SSMS2005 not SSMS2008/2012
7. be patient ...
Cheers
Amir

erinehartjr Newbie Points: 0 More actions · Answer 7

I'm not sure if this was ever fixed, but ever time I've run into this error all I've needed to do was load the driver from the following link, and my packages run great.

deborah.long Newbie Points: 0 More actions · Answer 8

It's a two-fold process to over come this error, but both very simple fixes. I used this post to solve the issue. - http://microsoft-ssis.blogspot.co.uk/2012/09/swtich-package-from-64bit-to-32bit.html

intvfan Newbie Points: 0 More actions · Answer 9

in the lower left of the validate screen is a Check Box to run 32 Bit.

This worked for me!

Changing the setting under DEBUG to 64Bit False did not work for me.

Alt7777777 Newbie Points: 0 More actions · Answer 10

Hello, just in case this is helpful, I had exactly the same issue, and upgraded the OLE DB provider on the machine I deployed to, and it finally worked.

https://www.microsoft.com/en-us/download/confirmation.aspx?id=56730

SSIS, "Class Not Registered" error...deployment or permissions issue?

Cookies on SQLServerCentral