nworks workflow problem

[maekee]

Hi,

I have a thing that is pretty irritating.
Using nworks MP 5.5.2.533

Am getting this Event in my enviroment about 20 times every day from different servers.

The Registry Probe could not connect to the registry of the computer '.'.
Error: 0x800706bf
One or more workflows were affected by this.
Workflow name: nworks.VMware.VEM.VirtualCenter.Discovery
Instance name: SERVER.DOMAIN.COM
Instance ID: {FA9C2448-0BBC-1AC5-1CFE-3D2EFC96FEB2}
Management group: MG1

And its only from nworks.VMware.VEM.VirtualCenter.Discovery no other Workflows.
So please.. help my figure out why i recieve this.

Thanks
/Maekee

[bigmak]

Hi Maekee,

Please check that you can connect to the registry (using regedit) on one of the failed servers locally, especially to the HKLM\SYSTEM\CurrentControlSet\Services subkey.

The error 0x800706bf (The remote procedure call failed and did not execute) means that you may expirience problems with the registry.

Are there any other errors on these servers for any another workflow?

Regards,
Dmitry

[maekee]

Hi Dmitry,

Found two other Workflows that also reports with the same Event.
And these are:
"nworks.VMware.VEM.Collector.Discovery" and
"nworks.VMware.VEM.MCServer.Discovery"

Have opened regedit locally on the server and connected to the Services-hive without any problems.
Have event connected locally from the management server (that communicates with the agent)
from within Regedit.exe to the servers registry from File - Connect Network Registry... and it works. (Event down to services)

If the local registry were a problem i would probably see a whole more lot of Workflows failing than these three nworks-workflows.

If i check all these events the last 24 hours i get 19 hits from 14 servers.
If any of these mashines would have a WMI-problem or Registryproblem i would see them coming back the whole day right?

Any more tips? Do i need to do something to make sure these 31901-Events stop coming.

/Maekee

[bigmak]

Maekee,

Does the Action Account used to run premises workflows have sufficient rights to access registry on these servers?

I would recommend you to open case with our support.

Regards,
Dmitry

[maekee]

Its Local System

[nan0x1]

Any news on this issue?

I have the same problem and I'm currently troubleshooting it. I might got a lead: when I restart the McAfee Framework and McShield services on the affected servers, the alerting seems to stop from those particular servers.
I'm still verifying it to be sure...

[nan0x1]

I was too quick, it doesn't solve this problem. Sorry.

[Irina Simkina]

Hi all,

please contact our support regarding this to investigate the problem and find the solution.

Thank you,
Irina