New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Exchange DAG Powershell - 4/12 sensors in error status

Votes:

0

Your Vote:

Up

Down

I upgraded our 3 server DAG from Exchange 2013 CU9 to CU11 this past weekend. After doing so, some of the DAG Powershell sensors return an error. Deleting the sensor, restarting PRTG and redeploying the sensor doesn't clear the error.

Our setup:

Ex01 - database_A, database_B = Active. database_C, database_E = passive

Ex02 - database_C, database_D = Active. database_A, database_F = passive

Ex03 - database_E, database_F = Active. database_B, database_D = passive

The sensors for database_A and database_C return the following error: no result from remote system, check settings

This seems to be linked to these 2 Exchange databases as it's the sensors for the active and passive copies of these DB that fail. This problem doesn't seem to be server-specific as the sensors for the other DB work fine.

How can I troubleshoot what's going on with the sensors on these DB?

Thanks, Greg

dag exchange-2013 powershell

Created on Feb 22, 2016 5:59:59 PM by  gregb (0) 1



9 Replies

Votes:

0

Your Vote:

Up

Down

Hi Greg,

Please open a command prompt in C:\Program Files (x86)\PRTG Network Monitor\Sensor System and execute ExchangeSensorPS.exe with the following parameters: -server="fqdn" -item=dag -object="<name of your mailboxdb>" -user="domain\user" -password="userpassword"

In case you don't want to post the result here, feel free to send us an email (support@paessler.com). While you're at it, please enable Write result to disk in the sensor's Settings tab. With the next scan -either manually performed or following scanning interval- the result will be written to C:\ProgramData\Paessler\PRTG Network Monitor\Logs (System) into a file carrying the sensor's ID in its filename (Sensor-ID is located on the sensor's Overview tab). Please also send us this result and a screenshot showing the sensor's Settings tab.

Thank you in advance & kind regards.

Created on Feb 24, 2016 1:51:04 PM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down


Hi Erhard,

The sensor log shows the same output as the command you gave me. Here's the output from the failed DB sensor (Tier3-A), and from a working sensor (Tier3-M) for a database on the same server.

I've sent an email to support with the requested screenshot (and sensor debug log).

Thanks,
Greg


C:\Program Files (x86)\PRTG Network Monitor\Sensor System>ExchangeSensorPS.exe - server=exchange06.domain.company.com -item=dag -object="Tier3-A" -user=domain\admin -password=PASSWORD \\<prtg> \\ <error> \\ 2 \\ </error> \\ <text>no result from remote system, check settings</text> \\</prtg>

C:\Program Files (x86)\PRTG Network Monitor\Sensor System>ExchangeSensorPS.exe - server=exchange06.domain.company.com -item=dag -object="Tier3-M" -user=domain\admin -password=PASSWORD \\<?xml version='1.0' encoding='UTF-8' ?> \\<prtg> \\ <result> \\ <value>1</value> \\ <unit>Custom</unit> \\ <valueLookup>prtg.standardlookups.exchangedag.status</valueLookup> \\ <channelId>9</channelId> \\ <channel>Status</channel> \\ </result> \\ <result> \\ <value>0</value> \\ <unit>Custom</unit> \\ <valueLookup>prtg.standardlookups.exchangedag.activationstatus</valueLookup> \\ <channelId>1</channelId> \\ <channel>Active Copy</channel> \\ </result> \\ <result> \\ <value>0</value> \\ <unit>Custom</unit> \\ <valueLookup>prtg.standardlookups.exchangedag.yesno.stateyeswarning</valueLookup> \\ <channelId>2</channelId> \\ <channel>Activation Suspended</channel> \\ </result> \\ <result> \\ <value>0</value> \\ <unit>Count</unit> \\ <channelId>7</channelId> \\ <channel>Single Page Restore</channel> \\ </result> \\ <result> \\ <value>0</value> \\ <unit>Count</unit> \\ <channelId>3</channelId> \\ <channel>Copy Queue Length</channel> \\ </result> \\ <result> \\ <value>0</value> \\ <unit>Count</unit> \\ <channelId>6</channelId> \\ <channel>Replay Queue Length</channel> \\ </result> \\ <result> \\ <value>0</value> \\ <unit>Custom</unit> \\ <valueLookup>prtg.standardlookups.exchangedag.yesno.allstatesok</valueLookup> \\ <channelId>5</channelId> \\ <channel>Log Replay Queue Increasing</channel> \\ </result> \\ <result> \\ <value>0</value> \\ <unit>Custom</unit> \\ <valueLookup>prtg.standardlookups.exchangedag.yesno.allstatesok</valueLookup> \\ <channelId>4</channelId> \\ <channel>Log Copy Queue Increasing</channel> \\ </result> \\ <result> \\ <value>0</value> \\ <unit>Custom</unit> \\ <valueLookup>prtg.standardlookups.exchangedag.contentindexstate</valueLookup> \\ <channelId>8</channelId> \\ <channel>Content Index State</channel> \\ </result> \\ <result> \\ <channel>Execution Time</channel> \\ <unit>TimeSeconds</unit> \\ <SpeedTime>Second</SpeedTime> \\ <float>1</float> \\ <ShowChart>0</ShowChart> \\ <ShowTable>0</ShowTable> \\ <ChannelID>99</ChannelID> \\ <Value>2.4</Value> \\ </result> \\ <text> \\ OK \\ </text> \\<prtg>

Created on Feb 25, 2016 1:48:43 PM by  gregb (0) 1

Last change on Feb 29, 2016 8:08:45 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hey Erhard,

I have the same problem after upgrading from Exchange 2013 CU9 to CU11. I'm not getting any results from the Exchange DAG sensors for the DB's in one of two DAGs

My setup is like this:

Ex01 - database_A, database_B, database_C : DAG-1 -active : Getting normal results

Ex02 - database_D, database_E, database_F : DAG-2 -active : "no result from remote system, check settings"

Ex03 - database_A, database_B, database_C : DAG-1 -passive : Getting normal results

Ex04 - database_D, database_E, database_F : DAG-2 -passive : "no result from remote system, check settings"

I'm getting similar XML results to Greg running the ExchangeSensorPS command from the probe server.

-server=Ex01 -item=dag -object="database_A" : <result> <value>1</value> <unit>Custom</unit> etc... -server=Ex01 -item=dag -object="database_B" : <result> <value>1</value> <unit>Custom</unit> etc... -server=Ex01 -item=dag -object="database_C" : <result> <value>1</value> <unit>Custom</unit> etc... -server=Ex01 -item=dag -object="database_D" : <error>2</error><text>no result from remote system, check settings</text> -server=Ex01 -item=dag -object="database_E" : <error>2</error><text>no result from remote system, check settings</text> -server=Ex01 -item=dag -object="database_F" : <error>2</error><text>no result from remote system, check settings</text>

-server=Ex02 -item=dag -object="database_A" : <result> <value>1</value> <unit>Custom</unit> etc... -server=Ex02 -item=dag -object="database_B" : <result> <value>1</value> <unit>Custom</unit> etc... -server=Ex02 -item=dag -object="database_C" : <result> <value>1</value> <unit>Custom</unit> etc... -server=Ex02 -item=dag -object="database_D" : <error>2</error><text>no result from remote system, check settings</text> -server=Ex02 -item=dag -object="database_E" : <error>2</error><text>no result from remote system, check settings</text> -server=Ex02 -item=dag -object="database_F" : <error>2</error><text>no result from remote system, check settings</text>

I've restarted the probes, recreated them on an different probe server, failed the DBs over to the passive nodes and restarted the Exchange servers. Powershell remoting and the Exchange Database sensor are working for all the databases on all the servers.

Thanks, Diarmuid

PRTG Version 16.1.21.1692

Created on Feb 25, 2016 11:33:46 PM by  Diarmuid (0)

Last change on Feb 29, 2016 8:20:28 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks for all your input, Greg and Diarmuid, I'll address this to the developer to see what we can do about this. I get back to you as soon as I know more.

Kind regards.

Created on Feb 26, 2016 8:49:48 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

PRGT support sent me an early-release sensor (ExchangeSensorPS_662326.zip). Replacing the existing ExchangeSensorPS.exe with the new one resolved the issue.

Thanks to PRGT for a quick resolution/turnaround!

Greg

C:\Program Files (x86)\PRTG Network Monitor\Sensor System>ExchangeSensorPS.exe server=exchange06.domain.company.com -item=dag -object="Tier3-M" -user=domain\admin -password=PASSWORD
<?xml version='1.0' encoding='UTF-8' ?>
<prtg>
<result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.status</valueLookup>
    <channelId>9</channelId>
    <channel>Status</channel>
</result>
<result>
    <value>1</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.activationstatus</valueLookup>
    <channelId>1</channelId>
    <channel>Active Copy</channel>
</result>
<result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.yesno.stateyeswarning</valueLookup>
    <channelId>2</channelId>
    <channel>Activation Suspended</channel>
  </result>
  <result>
    <value>0</value>
    <unit>Count</unit>
    <channelId>7</channelId>
    <channel>Single Page Restore</channel>
</result>
<result>
    <value>0</value>
    <unit>Count</unit>
    <channelId>3</channelId>
    <channel>Copy Queue Length</channel>
</result>
<result>
    <value>0</value>
    <unit>Count</unit>
    <channelId>6</channelId>
    <channel>Replay Queue Length</channel>
</result>
<result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.yesno.allstatesok</valueLookup>
    <channelId>5</channelId>
    <channel>Log Replay Queue Increasing</channel>
</result>
<result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.yesno.allstatesok</valueLookup>
    <channelId>4</channelId>
    <channel>Log Copy Queue Increasing</channel>
</result>
<result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.contentindexstate</valueLookup>
    <channelId>8</channelId>
    <channel>Content Index State</channel>
</result>
<result>
    <channel>Execution Time</channel>
    <unit>TimeSeconds</unit>
    <SpeedTime>Second</SpeedTime>
    <float>1</float>
    <ShowChart>0</ShowChart>
    <ShowTable>0</ShowTable>
    <ChannelID>99</ChannelID>
    <Value>3.2</Value>
</result>
<text>
    ActiveDbCopy: EXCHANGE05
</text>
</prtg>
C:\Program Files (x86)\PRTG Network Monitor\Sensor System>ExchangeSensorPS.exe -server=exchange06.domain.company.com -item=dag -object="Tier3-A" -user=domain\admin -password=PASSWORD
<?xml version='1.0' encoding='UTF-8' ?>
<prtg>
  <result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.status</valueLookup>
    <channelId>9</channelId>
    <channel>Status</channel>
  </result>
  <result>
    <value>1</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.activationstatus</valueLookup>
    <channelId>1</channelId>
    <channel>Active Copy</channel>
  </result>
  <result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.yesno.stateyeswarning</valueLookup>
    <channelId>2</channelId>
    <channel>Activation Suspended</channel>
  </result>
  <result>
    <value>0</value>
    <unit>Count</unit>
    <channelId>7</channelId>
    <channel>Single Page Restore</channel>
  </result>
  <result>
    <value>0</value>
    <unit>Count</unit>
    <channelId>3</channelId>
    <channel>Copy Queue Length</channel>
  </result>
  <result>
    <value>0</value>
    <unit>Count</unit>
    <channelId>6</channelId>
    <channel>Replay Queue Length</channel>
  </result>
  <result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.yesno.allstatesok</valueLookup>
    <channelId>5</channelId>
    <channel>Log Replay Queue Increasing</channel>
  </result>
 <result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.yesno.allstatesok</valueLookup>
    <channelId>4</channelId>
    <channel>Log Copy Queue Increasing</channel>
  </result>
  <result>
    <value>0</value>
    <unit>Custom</unit>
    <valueLookup>prtg.standardlookups.exchangedag.contentindexstate</valueLookup>
    <channelId>8</channelId>
    <channel>Content Index State</channel>
  </result>
  <result>
    <channel>Execution Time</channel>
    <unit>TimeSeconds</unit>
    <SpeedTime>Second</SpeedTime>
    <float>1</float>
    <ShowChart>0</ShowChart>
    <ShowTable>0</ShowTable>
    <ChannelID>99</ChannelID>
    <Value>1.9</Value>
  </result>
  <text>
    ActiveDbCopy: EXCHANGE04
  </text>
</prtg>

Created on Feb 26, 2016 5:04:31 PM by  gregb (0) 1

Last change on Feb 29, 2016 7:13:07 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

@Diarmuid: I've just sent you the new exe of the sensor by email.

Kind regards.

Created on Feb 29, 2016 8:24:31 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks guys, its working again. Great response time. Cheers, Diarmuid

Created on Mar 1, 2016 2:55:26 AM by  Diarmuid (0)



Votes:

0

Your Vote:

Up

Down

Microsoft posted an update to their Exchange blog yesterday explaining that CU11 introduced some Remote Powershell changes. After introducing it, they're rolling it back when CU12 releases.

"Prior to CU11, Exchange 2013 routed Remote PowerShell requests by finding a random mailbox that is either higher than the ExchClientVer that is specified in the URL, or if the ExchClientVer is not specified, by using the current CAS version in which the client connected. We refer to this behavior as server version-based routing.

With CU11, we changed Remote PowerShell to route requests to an anchor mailbox. Typically, this anchor mailbox would be the mailbox of the user attempting the connection. In the event the user attempting the connection did not have a mailbox, the request would be routed to the organization arbitration mailbox."

http://blogs.technet.com/b/exchange/archive/2016/03/01/remote-powershell-proxying-behavior-in-exchange-2013-cu12-and-exchange-2016.aspx

Maybe that's why some of the DBs worked while others didn't.

In any case, Paessler's response and solution for me were both terrific.

Greg

Created on Mar 2, 2016 12:15:22 PM by  gregb (0) 1



Votes:

0

Your Vote:

Up

Down

Thanks for the update, Greg!

Created on Mar 3, 2016 1:54:20 PM by  Erhard Mikulik [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.