Servers are 2005 SSIS servers at SP3. Packages are stored on File System. I updated the query on one of the workflows this particular package uses. I'm the original creator of the package too. It's a simple package that executes a query and outputs the result in xml to a text file. I've been able to update the query in the package before and import the updated dtsx file to the SSIS server on at least 2 previous occasions. However, today when I tried to import an updated version I'm getting the following error after confirming that I want to overwrite the existing package in the SSIS file system storage. =================================== Element not found. (Exception from HRESULT: 0x8002802B (TYPE_E_ELEMENTNOTFOUND)) (Microsoft.SqlServer.DTSRuntimeWrap) ------------------------------ Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName) at Microsoft.SqlServer.Dts.ObjectExplorerUI.ImportPackageAsAction.ImportPackage(ImportPackageAsForm dlg) =================================== Element not found. (Exception from HRESULT: 0x8002802B (TYPE_E_ELEMENTNOTFOUND)) (Microsoft.SqlServer.DTSRuntimeWrap) ------------------------------ Program Location: at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToDtsServer(IDTSPackage90 pPackage, IDTSEvents90 pEvents, String bstrPackagePath, String bstrServerName) at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName) I've done several searches on google but have found nothing that tells me why I'm suddenly unable to import the updated package or how to overcome this problem and I don't understand the error output as I'm still a SSIS newbie. Can someone clarify for me what is going on? Here's the sequence that triggers the error above: Log into the server integration services engine via SSMS. Right click on package to be updated and selected Import. Selected File System for package location. Gave path to updated dtsx file. Left package name the same. Left Protection Level untouched. Hit OK, server does some thinking and tells me that the package already exists and then asks me if I want to overwrite it. I click on Yes I get the error above. I've tried doing the import on three different SSMS 2005 clients with the same result.

Delete the package in question and then just add the updated as if it would be the new one. I hope you used the same BIDS build/version to update that package.Arthur My Blog

I get the same error after deleting the package and re-adding as new.

Try to register a dummy package, see what is happening. I suspect the versions of either SSIS or BIDS are not the same. PS: Also make sure to tell us if there are more errors than that. Arthur My Blog

In the end it had nothing to do with the package at all. Uninstalling and reinstalling the MSXML6 msi on my workstation fixed my problem.