For WMI Mode,
If you are using AppManager version 15470 and above, you can navigate to
Admin > Self Help Tools and choose the monitor type to troubleshoot the problem.
Click here for more details.If you are using AppManager version below 15470, follow the troubleshooting steps mentioned below.
1. Could not Connect to the System. The System may be down or RPC Server is not be available.
2. Authentication failed. Kindly verify the username and password provided for the Host.
After successful connection to wbemtest. Run the below queries :
1. Select Name,State from Win32_Service WHERE Name like 'MSMQ%'
- Services should be displayed as follows if MSMQ is installed properly.
2. select IncomingMessagesPersec,IncomingMulticastSessions,IPSessions,MSMQIncomingMessages,MSMQOutgoingMessages,OutgoingHTTPSessions,OutgoingMessagesPersec,OutgoingMulticastSessions,Sessions,Totalbytesinallqueues,Totalmessagesinallqueues from Win32_PerfFormattedData_MSMQ_MSMQService
- The MSMQ stats should be displayed properly.
3. select Name,BytesinJournalQueue,BytesinQueue,MessagesinJournalQueue,MessagesinQueue from Win32_PerfFormattedData_MSMQ_MSMQQueue
- The data for individual queues should be displayed as below.
For Powershell Mode,
- Make sure all the pre-requisites are completed for Powershell.
- Refer here.
- The Powershell version should be 5 or above. Check the local and remote server.
- Open Powershell console and execute "$session = New-PSSession -ComputerName Server02 -Credential hostname/username".
- Once session is created from AppManager server to the monitored server, execute "Invoke-Command -Session $session -ScriptBlock {Get-MSMQQueue}" command.
- The private queues if any and their data should be diplayed.
- If error message contains cmdlet not found. Make sure MSMQ is installed properly.
- Finally, use "$session |Remove-PSSession" command to remove the session.