failed laod xml error 0xc00ce556

after i completed working with all my packages finally in my master package i was trying to set ssis->logging

i came up with this error with all my packages how to get back my packages..

Microsoft visual studio is unable to load this document:Failed to load XML due to error 0xC00CE556 "Invalid at the top level of the document. Line 1099, Column 1". This happens when loading a package and the file cannot be opened or loaded correctly into XML document. This can be the result of either providing an incorrect file name to the LoadPackage method or the XML file specified having an incorrect format.

How can i solve this problem please me

Curious, do you use Source Safe or any source control software?|||

I have the project in my local machine.

Everything package and the master package which call the child packages where working just fine.

What i did was after doing all my work in the master package i was try to set ssis logging and all my packages came out with this error...just couldnt open any of my packag...all my packages which i have r the same error..i am just redoing everything...

any help is appreciated...

|||Woops! It looks like the files are corrupted... don't you have copy previous to the changes? I have never see such error. Sorry.

Fail to call child package

Have a parent package that calls many child packages (over 30) for a daily data warehouse update. On any given day, it randomly fails to call a child package with the following error:

Error 0x800706BE while preparing to load the package. The remote procedure call failed.

Its not failing the same package each day. I need a better explanation of this error message.

Environment: SQL2005 Enterprise Dec2005 RTM on Itanium64 with Windows DataCenter.

Are all the Execute Package tasks in the parent package configured identically? Where are the child packages stored?|||Yes, all Exec Package tasks are set up the same. All packages are stored in MSDB on our DataWarehouse server. Because we have such a large volume of packages (200), we are using folders to separate the packages. The parent package calls children in the Dimensions and various other folders. The call failures span many of the children folders, so there doesn't seem to be a pattern.