Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Server & Application Monitor (SAM) > Appinsight for Exchange fails with PowerShell FullLanguageMode is not configured on Remote Host

Appinsight for Exchange fails with PowerShell FullLanguageMode is not configured on Remote Host

Created by Harry Griffiths, last modified by MindTouch on Jun 23, 2016

Views: 890 Votes: 0 Revisions: 14

Updated May 30, 2016

Overview

 

Appinsight for Exchange fails with the following error:

PowerShell FullLanguageMode is not configured on Remote Host At line: 1 char: 30 + Select-Object @(n="test"; e={}} + ~~ Script block literals are not allowed in restricted language mode or a Data section.

 

The configure server is performing the below:

Invoke-Command -Session $sess -ScriptBlock { Select-Object @{n="test"; e={}}}
            if (!$?) {
                        Throw '{{PowerShellFullLanaguageModeNotConfiguredOnHost}}'
            }

 

SAM polling reveals the error returned:

VERBOSE SolarWinds.APM.Probes.CustomPowerShellProbe - <DocumentElement>
  <Connection>
    <Message>{{PowerShellFullLanaguageModeNotConfiguredOnHost}}</Message>
  </Connection>
</DocumentElement>
VERBOSE SolarWinds.APM.Probes.CustomPowerShellProbe - ---
WARN  SolarWinds.APM.Probes.CustomPowerShellProbe - Error found in results: At line:1 char:30
+  Select-Object @{n="test"; e={}}
+                              ~~
Script block literals are not allowed in restricted language mode or a Data section.


Upon checking, the exchange server you are trying to configure for AppInsight for Exchange already has this configured.

IISManager > Sites > default > Powershell > Application Settings, and Add/Change PSLanguageMode to FullLanguage

Environment

All SAM versions

Cause 

FullLanaguageMode is not configured on another exchange server from the one that is being configured which relates back to the usage of arbitration mailboxes.

Resolution

  1. Check to see if you have any arbitration mailboxes on other exchange hosts.
  2. This command displays list of servers which hosts arbitration mailboxes:

    Get-Mailbox -arbitration | select -expand database -Unique | Get-MailboxDatabase | select -expand activationpreference  
    
  3. Make sure that FullLanaguageMode is configured on the other exchange server that hosts such mailboxes.

  4. On the other server, navigate to IISManager-->Sites-->default-->Powershell-->Application Settings, and Add/Change PSLanguageMode to FullLanguage.

    Run from Command prompt IISRESET with administrator privileges.

  5. Configure AppInsight for Exchange against this server as well.

  6. Both exchange servers should be up and running.

 

 

Last modified
02:44, 23 Jun 2016

Tags

Classifications

Public