Failed to Create instance of DOMDocument

[mbeckey]

Toady all of our replication jobs started failing with the following error

Code: Select all

Error: Errror code: 0x80040154 Failed to Create instance of DOMDocument.  Has anyone seen this error before?

[veremin]

Hi, Mark.

Unfortunately, I can’t tell you anything regarding what was the reason of this error, someone else might shed a light on it.

However, I, probably, can propose you a solution - previously people have reported that such issue can be solved by restarting veeam proxy service.

Hope this helps.

Thanks.

[mbeckey]

v.Eremin

Thanks for the reply I just got off the phone with support and they supplied a hot fix for the issues. I am seeing the jobs completing now.

KB Article: http://www.veeam.com/KB1671

[jbarrow.viracoribt]

All of my replication jobs are failing all of a sudden. Error is as follows:

3/5/2013 9:01:47 AM :: Error: Error code: 0x80040154
Failed to create instance of DOMDocument

[jbarrow.viracoribt]

That KB talks about version 6.1, I'm running 6.5 already.

[veremin]

Hi, Jonathan. As a workaround, you can try to restart veeam proxy service and see whether it works.

If it doesn’t, then, please keep working with our support team on investigating this issue and update the topic with a found solution.

Hope this helps.
Thanks.

[jbarrow.viracoribt]

Proxy reboot, replication looks to be working again. I wonder what went wrong?

[veremin]

Nothing to say at the moment. Probably, only the debug logs will explain what were the reasons of the issue you got.

Thanks.

[jbarrow.viracoribt]

Gotcha. I opened a case with the support team (00186933) and uploaded my logs. I hope that has the details they need.

[ErikSi]

Also had this message when trying to restore a VM with distributed switches to a vm with no connections.
perhaps your VM has also distributed switches ?

[jbarrow.viracoribt]

Also had this message when trying to restore a VM with distributed switches to a vm with no connections.
perhaps your VM has also distributed switches ?

We're not using distributed switches.

[jbarrow.viracoribt]

The issue returned today. Looking at my jobs from last night at about 5:42pm they all started dying again.

I just rebooted my proxy, let's see if that fixes it again.

[jbarrow.viracoribt]

Working again after the proxy reboot. I wonder why I keep having to do that?

[veremin]

Did you get any answer regarding this from our support team?

Thanks.

[jbarrow.viracoribt]

Did you get any answer regarding this from our support team?

Thanks.

No. Case 00186933. It was pretty much closed after I stated that the reboot fixed it last time. Now that this has reappeared again in such a short period of time we probably need a deeper look.

[veremin]

Now that this has reappeared again in such a short period of time we probably need a deeper look.

Yep, I'd suggest to reopen the case (or create a new one) to continue investigating the causes of this issue with support.

Thanks.

[tominmiami]

i have about 12 instances of Veeam running for 12 different customers and am beginning to see this error more and more often. It seems to have just start in the past few weeks. A reboot helps, but is not an acceptable resolution.

[foggy]

The best way to address this is to create a support case and provide debug logs for investigation.

[pawel.podolski]

hey all,
Since yesterday, I noticed the same problem in their environment (on all tasks that until yesterday to work properly).
I have Veeam Backup & Replication: Enterprise edition 6.0.0.164 (64bit)
Can you suggest how to solve this problem?

[foggy]

Paweł, have you tried to restart Veeam Proxy Service? If this doesn't help, the most efficient way to investigate technical issues like that is to contact our support team directly. Thanks.

[veremin]

6.0.0.164

Also, it definitely stands to reason to upgrade your VB&R instance to the most up-to-date version, because a variety of improvements have been implemented, and numerous issues have been addressed since that time.

Thanks.

[pawel.podolski]

Paweł, have you tried to restart Veeam Proxy Service? If this doesn't help, the most efficient way to investigate technical issues like that is to contact our support team directly. Thanks.

Hi all,
After rebooting Veeam Proxy Service, everything is back to normal. In any case rebooted the entire system.
It seems that so far is good. I'll have to take to update Veeam to ver. 6.5 Regards.

[veremin]

I'll have to take to update Veeam to ver. 6.5.

The best strategy, indeed.

Should any additional help be needed, feel free to contact us. Thanks.

[maverick964_uk]

We have veeam 6.5 with update 3 installed.

this morning we started getting these errors:

Veeam Error code: 0×80040154 Failed to create instance of DOMDocument

It would seem that restarting the proxy service may help or rebooting the veeam server/proxy too.
This is deemed a workaround but the problem could re-appear.....

Is there a hotfix to resolve this issue??

thanks

[foggy]

Mike, there's not much information in the support case mentioned in this thread earlier, so please open your own case for investigation. If there is any hotfix available for this issue, you will be immediately notified by our technical specialists. Thanks.

[maverick964_uk]

many thanks Alex. We will log a case...

[masonit]

many thanks Alex. We will log a case...

We have also seen this error now. What did support say?

\Masonit

[foggy]

Mike hasn't provided his case ID yet, so I cannot provide more information about the issue. It would be great if you could open your own case and communicate with support directly. Thanks.

[kevinnaughton]

Just had this error on all my jobs. Found this thread, and also found this KB article stating hot fix is available from support that applies to v. 6.5.0.144 (which is what I have). Just FYI for anyone else experiencing this.
http://www.veeam.com/kb1767