VMware Horizon Community
Samuel_gu
Contributor
Contributor

[HELP] The error message from Get-Monitor command-let

I am using the powershell command-let to collect the view environment information, such as, Get-connectionBroker, Get-ViewVC, Get-Pool... they are running as normal,

but when i type the comand "Get-Monitor", it shhows me that

Get-Monitor : PowershellService::GetMonitor FAILED, error=
At line:1 char:12
+ Get-Monitor <<<<
    + CategoryInfo          : InvalidResult: (vmware.view.pow...lets.GetMonito
   r:GetMonitor) [Get-Monitor], Exception
    + FullyQualifiedErrorId : PowershellService::GetMonitor FAILED,vmware.view
   .powershell.cmdlets.GetMonitor

Get-monitor error.png

Can anyone help? Do you encounter the similar problem? How to fix?

0 Kudos
5 Replies
mpryor
Commander
Commander

What do you see in the log files under c:\programdata\vmware\vdm when you run this?

0 Kudos
Samuel_gu
Contributor
Contributor

I can find this message in log,

2013-03-08T15:16:33.881+08:00 ERROR (134C-038C) <Thread-583> [jadminservice] JAdmin service invocation failed

0 Kudos
mpryor
Commander
Commander

That log line should be preceded by more detailed information in the debug log, can you post that too?

0 Kudos
mospekt13
Contributor
Contributor

It's very old post but I'm getting exactly same error. I found under logs something like this:

2020-03-02T14:06:18.247-06:00 DEBUG (141C-16F0) <Thread-1110520> [jadminservice] JAdmin service invocation failed com.vmware.vdi.logger.Logger.debug(Logger.java:44)

    at com.vmware.vdi.jadminservice.JAdmin.h(SourceFile:595)

    at com.vmware.vdi.jadminservice.JAdmin.e(SourceFile:64)

    at com.vmware.vdi.jadminservice.JAdmin$Worker.a(SourceFile:1079)

    at com.vmware.vdi.jadminservice.JAdmin$Worker.MessageHandler(SourceFile:1056)

2020-03-02T14:06:18.247-06:00 ERROR (141C-16F0) <Thread-1110520> [jadminservice] JAdmin service invocation failed

I'm totally clueless. Any help would be greatly appreciated. I use Get-Monitor to inventory all stuff from environment.

Thank you.

0 Kudos
rgainesCW
Contributor
Contributor

Got the same error.  Did you find a solution to this?

Power CLI 7.12

0 Kudos