The connection type "OLEDB" specified for connection manager "Microsoft OLE DB Provider for SQL Server" is not recognized as a valid connection manager type. - DTSX packages keep saying corrupted

Hello all.  I am having a problem on our SQL 2005 box where anytime I try to open a dtsx file which used to open fine is now saying:

Error loading Update_OEM_PartNumbers.dtsx: The connection type "OLEDB" specified for connection manager "Microsoft OLE DB Provider for SQL Server" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.        D:\SQLSSIS\Update_OEM_PartNumbers.dtsx      1      1      

Any idea how I fix this?  All of the packages say the same thing now.
sbornstein2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

brejkCommented:
Try to open your DTSX file in any text editor and look for ConnectionString property of your connection manager. Then check what provider name is given in this connection string. If it's not SQLOLEDB.1 or SQLNCLI.1 then try to modify it by simply overwriting the existing values (make some backup copy of the file before).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sbornstein2Author Commented:
it says now SQLNCLI.1.   I was reading an article that something is probably wrong with registry keys which I checked by running this program but still no dice.

http://support.microsoft.com/default.aspx?scid=kb;en-us;913817

ran the program but no invalid keys came up.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.