I am running into this error on a regular basis, but any posts I have managed to find that sound similar all seem different in one key regard - it does not happen consistently in my case. Here's the error: The details in the error list are: Error 1 Error loading XXXXX.dtsx: The connection type "OLEDB" specified for connection manager "XXXXX" 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. C:\XXXXX\XXXXX.dtsx 1 1 Error 2 Error loading XXXXX.dtsx: Error loading value "<DTS:ConnectionManager xmlns:DTS="www.microsoft.com/SqlServer/Dts"> <DTS:Property DTS:Name="DelayValidation">0</DTS:Property> <DTS:Property DTS:Name="ObjectName">direcTORY</DTS:Property> <DTS:Property DTS:Name="DTSID">{EF828D74-FC39-4A9B-BB51-D4D61508B9" from node "DTS:ConnectionManager". C:\XXXXX\XXXXX.dtsx 1 1 Error 3 Error loading 'XXXXX.dtsx' : The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails. . C:\XXXXX\XXXXX.dtsx 1 1 --- The package is being called from another package which runs 10 packages in order, and I get these kinds of errors randomly on different packages in the parent package, and sometimes not at all. When I close the package and re-open it, it will always load fine. The package also executes fine when it is called from the parent package, it just doesn't display it or any debugging information, but I can see from the database that it has in fact run successfully. The error window that pops up in the pic above causes the rest of the parent package execution to halt until the OK button is pressed, but otherwise the execution will continue on afterwards. I tried clearing out my TFS directory and re-doing the checkout, and that seemed to work at first as I ran through the package about 5-6 times without getting an error, but I am now back to getting the error every 1-2 tries. I have seen several posts indicating that the error message means the package is corrupt - but that would not appear to be the case if it is working off and on. Any suggestions?

Do you have multiple developers working on these packages? If so then you might want to make sure that everyone is playing with the same version/SP level of the tools. If you open up the dtsx file you should see an entry like this near the top that will tell you what version the last person who saved the package was using: DTS:LastModifiedProductVersion="11.0.2100.60" or this format in 2008 and older <DTS:Property DTS:Name="LastModifiedProductVersion">10.50.1600.1</DTS:Property> Chuck Pedretti | Magenic North Region | magenic.com

We did have multiple developers working on it, but since I started running into this error it's just been me that has been working on it. Myself and the other dev were also working on it on the same machine, so I don't think it would be a version issue with BIDS. TFS history also shows that the package I most recently ran into the error on has only been modified by me for more than a year.

I also think resetting the package guids may help: http://bidshelper.codeplex.com/workitem/24379Arthur My Blog

Then the next question is - what types of OLEDB connections are you using and is it possible that you have recently loaded a new driver or removed an existing one? The connection type "OLEDB" specified for connection manager "XXXXX" is not recognized as a valid connection manager type.Chuck Pedretti | Magenic North Region | magenic.com

ArthurZ, the problem actually happens on different packages all the time - so I'm not sure the GUID would be the issue either. The package will also open fine after the problem has occurred, without any modifications being made to it. Chuck, we're almost exclusively using the Native OLE DB\SQL Server Native Client 10.0 provider. To my knowledge that is the same driver we have used since the beginning, and I don't believe there have been any additional drivers installed on this server recently - but it is a development server, so it's always a possibility one of our other developers installed one. As I siad - the weird thing to me is that although package XXXXX.dtsx had the problem this time around, it will work fine the next time, and we'll run into the issue on another package. It seems entirely random. I have 3 sets of packages that are all run by a main package, with a total of about 100 packages - and it seems I run into this issue at least once every couple of runs when I run through all of them. It's difficult to test whether the issue occurs on other machines as well, as the data-set we're running these packages on is quite big. I did run it remotely with a subset of the data from a different machine and I didn't run into the issue, but like I said - sometimes it occurs, sometimes it doesn't.

I understood you execute the package locally by pulling it off a remote storage, therefore this could be due to a connectivity issue, namely your network stability.Arthur My Blog

hey Arthur, I was trying the reset GUID and actually ran into the error when it reloads the package after the reset. I continued on doing the rest of the packages in the first bunch though, and I've run through twice without hitting the error - I'll continue to test and see if the issue persists and if not I'll do the rest of the packages. Thanks for all the input and the quick responses by the way, everyone...

D'Oh! Ran into the issue again shortly after posting... back to the drawing board.

The package is executed on the local machine, all dtsx files are stored on the local machine, and all database connections are to the local machine.

1. I'm not sure if you need to configure the file path of your child package, because you call them from main package. Sometimes, all packages exist in TFS folder, but you run pakcage locally, if you need to reconfigure the file path of child package, package will validate these changes. So are child packages and parent package sharing the same connection at that time? Or you set localhost for them, because if you run packages on the server, the localhost means server, if you run packages locally, the localhost means your current local server. 2. Can you try to set the package property - DelayValidation to true (Default value is false - it will validate package everytime when you open your package). Hope it helps! Vote if it's helpful! Simon MSN:simonlv@live.cn Skype:simonlvpin

The package is executed on the local machine, all dtsx files are stored on the local machine, and all database connections are to the local machine. You may be missing updates or a service pack. If not, consider repairing the SQL Server installation. Arthur My Blog

So far, setting the DelayValidation property to true on each of the packages appears to be at least getting around the problem - is there a way to manually trigger the validation at design time though?

Well, it was good while my luck lasted - but unfortunately the error still occurs with delay validation set to true on all of the packages. I was hoping to avoid a repair/reinstall as it's going to take us several weeks to coordinate downtime for this particular development server. I'm not sure there's any other option at this point though. If anyone has any other suggestions I'd love to hear them!

We pretty much gave up on this, and moved to SSIS 2012. The issue does not occur there with the same packages.