WMI method call failed

[ROSA]

When trying to define the backup job (File level backup), after selecting Next I get this error message:
WMI method call failed
Critical error

I've searched the forum and the suggestion on this problem is to open a support case.
When clicking on the "Submit Case" button I get "WMI method call failed"
What now?

[Mike Resseler]

Hi,

Can you PM me with your email address? I will ask support to contact you directly (but please note this is without SLA so we will contact you when an engineer is available)

Thanks
Mike

[ROSA]

Done.

[Mike Resseler]

Hey,

I notified support with an email with your data. From the moment there is availability they will contact you. Please follow up with the case ID and result afterwards in this forum

Thanks
Mike

[svecmarek]

Hello,

When I create the backup job (File level backup), after selecting Next I get this error message:
Critical error - WMI method call failed

When I try set backup repository I get Critical error - Failed to load Veeam Agent for Windows licence. WMI method call failed.

I cant open a support case.
When clicking on the "Submit Case" button I get "WMI method call failed"

Thanks

[Dima P.]

Hi svecmarek,

Try to rebuild WMI. If that won’t help PM me you contact email address. Thanks.

[ROSA]

Case # 02083266

[Dima P.]

ROSA,

Per case details support team set a webex session with you. Did that help? Thanks.

[ROSA]

The session just ended.
Sadly not ...

[Dima P.]

ROSA,

Unfortunately, can’t see any case details regarding last webex. Did you try to rebuild WMI repository with support engineer? Check the link above it should have detailed explanation on how to do that.

[ROSA]

I've tried rebuild WMI already before the session - it did't help.

Aleksandr tried really hard.
He tried rebuilding WMI, WMIDiags, a WMI diag/debug tool (I don't remember the name and can't find it), sfc, different versions of .NET framework even Endpoint backup v1.5 and a lot of other things (registry, logs, etc.).
In the end of the session he suggested running chkdsk /f /r, which I did, but it didn't help.

It seems to me that the problem is in the Windows WMI not in VAW
The interesting thing is, I have a second almost identical server, where the VAW runs without a problem.

I would like to ask for advice - should I close the case, even when it's not solved?

[Mike Resseler]

Rosa,

I will leave that open to the support engineer and your good judgement. It indeed seems like an issue with WMI and not with VAW. You can propose him to close and see what he says about it but maybe he wants to escalate or try a few other things. It is difficult for me to give you an answer as we were not involved in the call.

PS: If WMI is really broken, you are going to run in bigger problems with that server and workload rather sooner than later so keep that in mind and maybe look at migrating the workload to a new server

[ROSA]

I've asked and the ultimate solution is a reinstall of the OS.

It's a "not so important server" and there is no other problem besides VAW.
But I'll keep in mind, that when something on this server starts acting strange, then reinstall is the right solution.

[Dima P.]

ROSA,

Thanks for the heads up! Just in case you still want to get WMI fixed, here is a detailed MS article (slightly different from the previously shared instruction).

[ROSA]

Thanks for the tip, I'll definitively give it a shot.

[svecmarek]

WMI works without problem with other software (monitoring, powershell query, ...). When I set up new job in VAW

Code: Select all

(Process id 9464)-> Error in event log "Id = {01AB6C40-F800-0000-C0A2-A944DA9CD201}; ClientMachine = xxxx; User = NT AUTHORITY\SYSTEM; ClientProcessId = 9464; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\cimv2 : select * from Win32_OperatingSystem; ResultCode = 0x80041032; PossibleCause = Unknown".

When I restart service VAW ->

Code: Select all

Id = {01AB6C40-F800-0000-C4A1-A944DA9CD201}; ClientMachine = xxxxx; User = NT AUTHORITY\SYSTEM; ClientProcessId = 9464; Component = Core; Operation = Start IWbemServices::ExecNotificationQuery - root\cimv2 : select * from Win32_DeviceChangeEvent where EventType = 2  or EventType = 3; ResultCode = 0x800706ba; PossibleCause = Could not send status to client

[Dima P.]

Hi Marek,

I am sorry, can you please clarify your issue? You can’t configure backup job and get WMI error or these event log entries are the only problem? Thanks.

[svecmarek]

When trying to define the backup job (File level backup or Volume level backup). It seems that the agent can not retrieve information about the system. Retrieves only the size of the disk and the files on it. Disk is labeled with a question mark

[Dima P.]

Thanks. Have you tried to rebuild a WMI? Check this KB article for more details. If that’s not working, kindly open a support case and share the case ID.

[ROSA]

Some interesting news.
I have done a P2V (VBox) conversion of the server and on the virtualized server VAW works without a problem.
I assume it's a hardware and/or driver problem ...

[ROSA]

It seems I finally solved it.
The was some garbage (special characters) in the server Serial Number / Product ID: instead of the Serial Number / Product ID:.
I wrote the correct Serial Number / Product ID: from the sticker in the BIOS and it seems the error is gone ...