Skip to Content
author's profile photo Former Member
Former Member

SolMan 7.1 Upgrade - Cannot Parse XML file

Hi guys

I'm trying to upgrade from Solution Manager 7.01 to 7.1 but i get this error that i can not have any info on (tried logs, SAP notes and google, absolutely zero hits).

ERROR: Scanning of download directory failed with the following error: More that on top level tag Cannot parse XML file "S:/.../MOPZ_XML_FILE.xml"

Any help?

Thanks

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    Posted on Aug 26, 2013 at 02:55 AM

    Hi Pedro,

    It looks like the XML file has some unwanted characters which is leading to parsing error.

    Could you explain the process of how did you create and copy this XML file to required server.

    Basically incase you copy the file from windows to Unix some end of line characters get introduced.

    Alternatively you may regenarate this XML file once again and copy it to the server which is being upgraded.

    Hope this helps.

    Regards,

    Deepak Kori

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 26, 2013 at 03:13 AM

    Hi,

    can you please check that all the settings in SMSY are correctly maintained for SOLman.

    Please check that SLD is running as the validation happens using SLD.

    Next thing can you try on another PC or browser.

    Hope the directory is accessible and has write permission to the S: directory.

    Thanks

    Rishi Abrol

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 26, 2013 at 06:35 PM

    I had the same problem during a SolMan 7.1 upgrade just a couple of weeks ago.

    In my case, the download folder (including the xml file) was on a network share that I had mounted as a drive for the sidadm user on the SolMan host. But SUM did not seem to be able to read anything from that drive. But it worked, when I put in the UNC name of the share instead. So, instead of using Z:\downloads, I used \\fileserver\sharename\downloads, and it worked just fine.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 26, 2013 at 06:05 PM

    Hi Pedro,

    What are you trying to do?

    Please let me know.can you attached the XML File.

    With Regards

    Ashutosh Chaturvedi

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 30, 2013 at 10:58 AM

    Hi all, and thanks a lot for your help. I managed to get over the situation. Here is what i have done:

    -> I applied an pre-upgrade snapshot to the machine (this is a pure sandbox system, so i had no problems with this)

    -> Cleaned the upgrade files directory (all of them: XML, SARs). The files were there before the snapshot, so i deleted them

    -> Then, i noticed that i forgot to put the upgrade export in the directory (I don't think that this was the cause of the problem, but who knows...)

    -> I recreated the XML file from solution manager

    -> I re-copied all the upgrade files to a central directory on the upgrade host.

    -> Started SUM from scratch (the snapshot didn't allow me to retake the old one).

    This second time i runned SUM, no problem arised.

    One important thing: when i was deleting the files XML, SARs, i noticed that there were more XML files on the directory than the MOPz one. I am not sure now that the problem referred to the MOPz file, because i cannot recall the log error exactly. Also i had already applied the snapshot to the VM, so I could not look at the logs again.

    These other files, i have no idea what they were. But they could be the source of the problem.

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.