Hello, after the last (April) Exchange Updates the Powershell Sensor for the Exchange Databases stopped working. Here the log
2021-04-14 09:19:56,617 [DEBUG] - ?<?xml version="1.0" encoding="utf-8"?> <prtg> <error>1</error> <text>The Sensor was able to connect to the Device using Remote-PowerShell but couldn't retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See http://kb.paessler.com/knowledgebase/en/topic/54353 for details. Die Syntax wird von diesem Runspace nicht unterstützt. Dies kann der Fall sein, wenn der Runspace nicht im Sprachmodus vorliegt.</text> </prtg> 2021-04-14 09:20:56,180 [INFO] - #################### BEGIN #################### 2021-04-14 09:20:56,180 [INFO] - Entry Assembly: ExchangeSensorPS, Version=18.4.46.1754, Culture=neutral, PublicKeyToken=null 2021-04-14 09:20:56,195 [INFO] - Now: 14.04.2021 09:20:56 - UTC-Now: 14.04.2021 07:20:56 2021-04-14 09:20:56,195 [DEBUG] - prepare connection 2021-04-14 09:20:56,195 [DEBUG] - user: genesis\prtg 2021-04-14 09:20:56,195 [DEBUG] - server: tango.genesis.local 2021-04-14 09:20:56,242 [DEBUG] - creating runspace 2021-04-14 09:20:56,273 [DEBUG] - opening runspace 2021-04-14 09:20:56,273 [DEBUG] - runspace state changed to: Opening 2021-04-14 09:20:56,539 [DEBUG] - runspace state changed to: Opened 2021-04-14 09:20:56,539 [DEBUG] - opened runspace 2021-04-14 09:20:56,539 [INFO] - connection established 2021-04-14 09:20:56,539 [INFO] - running 'Get-ExchangeServer' 2021-04-14 09:20:56,539 [DEBUG] - Running script: 'Get-ExchangeServer' 2021-04-14 09:20:56,602 [ERROR] - Error in RunRequest Get-ExchangeServer 2021-04-14 09:20:56,617 [ERROR] - Exception occured System.Management.Automation.RemoteException: Die Syntax wird von diesem Runspace nicht unterstützt. Dies kann der Fall sein, wenn der Runspace nicht im Sprachmodus vorliegt. bei System.Management.Automation.Runspaces.AsyncResult.EndInvoke() bei System.Management.Automation.PowerShell.CoreInvokeRemoteHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings) bei System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings) bei System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings) bei System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings) bei System.Management.Automation.RemotePipeline.Invoke(IEnumerable input) bei ExchangeSensorPS.ExchangeSensorProgram.RunRequest(String script) bei ExchangeSensorPS.ExchangeSensorProgram.GetExchangeProductVersion(Collection`1 result) bei ExchangeSensorPS.ExchangeSensorProgram.Main(String[] args) 2021-04-14 09:20:56,633 [DEBUG] - ?<?xml version="1.0" encoding="utf-8"?> <prtg> <error>1</error> <text>The Sensor was able to connect to the Device using Remote-PowerShell but couldn't retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See http://kb.paessler.com/knowledgebase/en/topic/54353 for details. Die Syntax wird von diesem Runspace nicht unterstützt. Dies kann der Fall sein, wenn der Runspace nicht im Sprachmodus vorliegt.</text> </prtg>
Any Idea?
Article Comments
I am having the same issue here and just want to make sure my problem is related to the known issue mentioned above.
It looks like a Cumulative Update 23 (KB5001779) was installed on our Exchange 2013 server last night and since this update has taken place, the mailbox database remote powershell sensor is no longer working.
I'm not sure how to pull a log for this, but this sensor was working prior to this update taking place and I am receiving the same exact error when trying to re-add it:
"The Sensor was able to connect to the Device using Remote-PowerShell but couldn't retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See http://kb.paessler.com/knowledgebase/en/topic/54353 for details."
If this is related, is there an ETA on a hotfix?
Thank you.
Apr, 2021 - Permalink
Hey,
Unfortunately, several customers have reported exactly this behavior after the Exchange update. In software development, it is unfortunately sometimes the case that one manufacturer (in this case Microsoft) changes something and others then have to follow suit.
We have to analyze the problem and I hope that my colleagues from development can offer a hotfix soon. This also means, that unfortunately, I can't offer you a quick solution at the moment and ask for your patience.
Best,
Sven Roggenhofer [Paessler Technical Support]
Apr, 2021 - Permalink