Failure saving package
Hello All,I have a package in the SQL 2000 environment that works fine. I have migrated this DTS Package to a SSIS Package using the Visual Studio 2005. After that, i made some changes in this package and now I'm trying to saveit butI am facing with this error message below: TITLE: Microsoft Visual Studio------------------------------ Failure saving package. ------------------------------ADDITIONAL INFORMATION: Invalid at the top level of the document.(Microsoft OLEDB Persistence Provider) ------------------------------ Invalid at the top level of the document.(Microsoft OLEDB Persistence Provider) ------------------------------BUTTONS: OK------------------------------ Could someone please help me with this ? Thanks in advance. Thiago
June 13th, 2006 3:21pm

Has anybody seen this issue resolved? I am experiencing the exact same issue.
Free Windows Admin Tool Kit Click here and download it now
September 25th, 2006 10:11am

hi guys, Probably not very helpful for you but a few months ago I suffered the same and my solution wasmake a DTSX from the beginning...
September 26th, 2006 10:17am

That's what I am doing at present but there are a couple of hundred of these that I need to change. If I have to build them all from scratch the project time is going to blow out considerably. The migration is not perfect (as I expected) but it does considerably speed up the conversion process. The funny thing is that a couple seem to have converted cleanly but the majority haven't. I will be putting in a support issue with Microsoft and I will report back with any findings.
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2006 4:16am

Everybody, If you have any recordset object exists/present in yourmigratedDTS workflow, please manually convert those variables datatype into Object (If you are not able to modify the recordset variables, please re-create the variables with Object datatype). After changing all the recordset variables, most probabily you should be able to save the migrated SSIS workflow. Thanks. Regards, Ezhilarasan Maharajan
October 5th, 2006 2:48pm

This seems to have solved my problem but I have some further testing to do. Great catch. Thanks for responding to this.
Free Windows Admin Tool Kit Click here and download it now
October 16th, 2006 2:42am

I've finished my testing and this has defintely resolved my problem. I also updated my MS support issue with this information so hopefully a KB article and a fix in a future SP will be forthcoming.
October 16th, 2006 6:10am

Thank you! It helps!
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2006 9:26pm

THANK YOU!!! Even 3 1/2 years later--this was the answer! I have been working on fixing a migrated package for 2 days without being able to save...hoping eventually I would replace whatever reference from the DTS world was causing this. Finally found this, and clicked on the recordset variable (that was used in my DTS looping logic, and that I am still using in my ForEach container)...and just changed the ValueType to Object and the package saved. Whew!
May 21st, 2010 7:14pm

Ditto AdamantSolver! THANK YOU!!!
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2010 10:28am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics