Enterprise Manager : XML parsing error

[wksantiago]

We just installed and upgraded Veeam Backup 4.0 and Enterprise Manager on the same machine.

We can log in to Enterprise manager with no problem.

We were able to add a Backup Server but when we manually start collecting it gives us the following errors:

Time Type Information
10/29/2009 10:47 Success Data collection job started.
10/29/2009 10:47 Success [10.11.40.174] Retrieving data...
10/29/2009 10:47 Error [10.11.40.174] XML parsing: line 1, character 4607, illegal name character
10/29/2009 10:47 Error [10.11.40.174] Data collection failed.
10/29/2009 10:47 Success Data collection job finished.

We cannot see any VMs or Jobs

Thanks,

[mdornfeld]

Along this line... I swear it worked fine in Beta3, but it appears to be broken now.

I get this error when checking status: "Backup Servers"
XML parsing: line 16, character 91, semicolon expected

I also notice that when I update the config, the backup status is not updating immediately even when I hit the refresh. For instance, I went into the configuration -> backup servers and edited my config and gave it a whole new name. Seems to take a few minutes to update.

[Gostev]

William, did you use some special chars anywhere?

We will need the service log to be able to say for sure what is causing this, you can find the log path listed on the Configuration|About page of the web UI, for me it is:
C:\Documents and Settings\Administrator\Local Settings\Application Data\Veeam\Backup\VeeamBES.log

Matt, please send us these logs too, we will investigate your problem as well. Have you upgraded from BETA3 by any chance?

[mdornfeld]

Beta3 I ran on a VM. This install is a straight update from the Veeam 3.1 release on my production box. I'll get the logs over. 3 things that I noticed that may or may not help.
1. I never rebooted after installing IIS (production box is Windows 2003 R2)
2. On install, DNS was actually screwed up for my production box. I have since fixed it with no luck.
3. The local "administrator" user on our box is renamed.

I would reboot right now, but I have a job running.

I'll get the logs over.

[Gostev]

We've identified the issue, thank you for the logs. It is indeed due to presence of special symbols, developers forgot to "escape" some of those properly. We will prepare a hot fix for this issue, and support will send it to you once it has been verified.

[Gostev]

William, please do not post the logs here - instead, please send the logs to support@veeam.com.
This way, you are also tracked as having the issue, and will get the fix once available.

[wksantiago]

Great!

Thanks and sorry for the log thing!

[Gostev]

The fix is already available, if you are having this issue - please contact support!

[mdornfeld]

Put the fix in my implementation. I had to remove the backup server from the configuration and re-add it to get it to register as healthy, but everything is working well now.

[satheesh]

Hi! I too have this problem. Any solution available?

[Gostev]

Yes, check out my previous post

[satheesh]

Ok - I've sent an e-mail to support... Thank you!

[TechHead]

Any news on a fix for this?

Thanks,


Simon

[mdornfeld]

Yes Simon. Contact Support and they'll get you the fix.

[Gostev]

Fixed in version 4.1