Warning Failed to parse the XML

Hi all

I got the same warning.
Anyone an idea?

Greetings
 Christian

Hi all,

I got the same warning.

Do not you know where could be a problem?

Thank you

Same issue here. Would appreciate an update from Acronis Engineers. The job states it succeeded, but it is hard to believe when warnings are in it like this

Hello all,

Thank you for using [[http://www.acronis.com/enterprise/ | Acronis Corporate Products]]

This error message doesn't influence the backup file integrity. We are aware of the problem, but this case needs an additional attention. If somebody is ready to provide us with several diagnostic files, please let me know about it via PMs. I will create a separate case and redirect it to QA.

Please don't forget to make the reference to this forum thread.

Thank you.

Same issus problem, but i can't do the backup....a windows with this message appear.Any solution ?

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Détails des entrées de journal
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Type : Erreur
Date et heure : 14/10/2009 16:01:29
Plan de sauvegarde : [Aucune]
Tâche : [Aucune]
Code : 3 866 625(0x3B0001)
Module : 59
Propriétaire :
Message :
Echec lors de l'analyse XML.
Informations additionnelles :
--------------------
Code d'erreurs : 1
Module : 59
LineInfo : 7679e7b9a7eb6817
Champs : line : 10, column : 3885, $module : c:\Program Files\Acronis\BackupAndRecovery\mms.exe
Message : Echec lors de l'analyse XML.
--------------------
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hello Michel,

Thank you for using [[http://www.acronis.com/enterprise/ | Acronis Corporate Products]]

What is the source for the backup operation? Do you try to backup a partition or your data folders?

Please download Acronis Report utility available here and run it, create a report and attach to your post.

This would provide us with detailed information on the hard disk partition structure.

Thank you.

Has this issue been resolved yet? (v10 Build 11133)

I am getting a similar error message with a different scenario. I am trying to re-add an agent to AMS. The agent was removed from AMS using the delete_machine_by_name.vbs. I also verified that there are no policies associated with the agent in question. When trying to add the machine back into AMS, it appears to add the machine but it does not show up on the All Physical Machines list. When checking the AMS log, the "Failed to parse the XML" message is listed numerous times. After trying again to add the machine to AMS and getting a message that stated "The machine has already been registered", the log has recorded the XML error 12 times within 10 minutes.

Any new info would be greatly appreciated.

Thank you.

Sent to Acronis Tech Support this morning in regards to the ticket I had open for this issue. Fell free to try this process if you are still having the problem. Please post results if you do.

<>

Hello David,

Thank you for posting your question, I will be happy to help. Please accept our apologies for the delay with the response.

It looks like the Acronis Agent was not added to the Acronis SQL instance correctly. Manually remove the ghost copy of the Acronis Agent from the Acronis SQL instance. Please see this article on how to do it.

Oleg,

Thank you for taking the time to reply to this thread.

As indicated in my post from 1/15/10, I have already resolved the issue at hand. And....guess what! Without completely rebuilding my AMS server! (for the 4th time).

It really seems that the entire AMS platform needs to be improved in regards to communication with the agents. The agents themselves seem to run great on their own. Most of my major issues seem to be when the AMS server isn't properly reading the status from the agents or the AMS just simply "flakes out".

And for the record, those of us in an Enterprise environment really do not wish to solve every issue by rebuilding the AMS server, deleting all of our backup policies, installing the latest build, or reinstalling agents for no apparent reason.

...rant over...

Thank you for taking the time to assist in the forums. We may rant at you a bit, but in the end, we do realize that you do have a thankless job and you try to help as best as you can.

DS

Hello David,

Thank you for your notes, they are really appreciated. 

Certainly, we are aware of the issues concerning the AMS, and our developers and QA team are working to improve it.

In most cases the current malfunction is caused by Microsoft XML Parser, it can be damaged or not up-to-date. To prevent this from happening in the future one should make sure that Windows is up to date.

Reinstall Microsoft XML Parser.

Please do not hesitate to ask additional questions if the provided information is not clear or you need a further assistance. 

Thank you. 

Hey guys not sure if you have fixed your problems yet but I was having the same problem! I had maybe one log event every minute or so... got out of control. I removed the machine from AMS went to the client machine and did the following: http://kb.acronis.com/content/7921

Re-added the Machine to AMS and it works fine.... There was just no way I could even think about removing our SQL server and starting from scratch. Production woulda stopped on multiple levels. This fix worked for me I hope it works for ya'll.

Matt

Phillips Painting

IT Manager

Hi Matt,

This did the trick for me, thanks! Also not an option to halt production at my org to dink around with time-consuming (and likely ineffective) re-installs. I appreciate you posting your solution.

Jack