Sunday, February 19, 2012

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 save it but I 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

Has anybody seen this issue resolved? I am experiencing the exact same issue.|||

hi guys,

Probably not very helpful for you but a few months ago I suffered the same and my solution was make a DTSX from the beginning...

|||

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.

|||

Everybody,

If you have any recordset object exists/present in your migrated DTS 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

|||

This seems to have solved my problem but I have some further testing to do.

Great catch. Thanks for responding to this.

|||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.|||Thank you! It helps!

No comments:

Post a Comment