I use Umbraco 4.5.2 for Dot Net 3.5. The problem is whenever I try to create a package of the site, I am just able to give the name of the package. But when I press next, BOOM, I get the following error:
Root element is missing.
Description:
An unhandled exception occurred during the execution of the current web
request. Please review the stack trace for more information about the error and
where it originated in the code.
Exception Details:
System.Xml.XmlException: Root element is missing.
Source Error:
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.
Hi John, it's probably not much help, but I've seen this error before without CMS Import being installed; it was only on a test install, but can't remember the actions before hand. I'm guessing you've checked the createdPackages.config and installedPackages.config files to ensure the xml is valid ?
Why CMSImport got the blame?? ;-) It's an bug in 4.5.x. According to this thread you it is becuase the /App_Data/packages/created/createdPackages.config file is empty. Open it add the following xml snippet to it
Unable to create an Umbraco Package!
I use Umbraco 4.5.2 for Dot Net 3.5. The problem is whenever I try to create a package of the site, I am just able to give the name of the package. But when I press next, BOOM, I get the following error:
Root element is missing.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Xml.XmlException: Root element is missing.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
IE also shows an error:
Message: Can't execute code from a freed script.
Please help....
I have exactly this issue too.
Another google search brought up a reference to CMS Import with this error. I am using this too. Could they be related?
Any ideas out there?
Hi John, it's probably not much help, but I've seen this error before without CMS Import being installed; it was only on a test install, but can't remember the actions before hand. I'm guessing you've checked the createdPackages.config and installedPackages.config files to ensure the xml is valid ?
thanks Hendy - I removed the CMS Import package and still have the error
I'll check those
Hi,
Why CMSImport got the blame?? ;-) It's an bug in 4.5.x. According to this thread you it is becuase the /App_Data/packages/created/createdPackages.config file is empty. Open it add the following xml snippet to it
and save the file. Then you can create packages again.
Cheers,
Richard
PS I'm interested in the google search you are referring to
sorry Richard - I thought it was unlikely
the post is here:
http://forum.umbraco.org/yaf_postst8475_Root-element-is-missing.aspx
from
http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=%22System.Xml.XmlException:+Root+element+is+missing%22+umbraco+package
i have checked the two xml files and they are as they should be
not sure what to do next
Maybe Umbraco can't open them, file permissions?? and if that isn't the case could you post your createdpackagesconfig file?
this is createdPackages.config
it has Network Service full control (the site is running as this id)
i get this error now when I try and create a package as a JavaScript popup
unsupported node - [objectHTMLInputElement]
hep,
The solution:
/App_Data/packages/created/createdPackages.config file is empty. Open it add the following xml snippet to it
Worked perfect for me - would high-five Richard Soeteman big time, but karma aint on my side ;)
/Soren
quite agree - have high five'd richard on your behalf :)
i'm still getting this error - no idea why - it's not this - but it must be something
next move for me is to start beta testing 4.6 juno and see if it still happens with this
is working on a reply...