Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Access Rights Manager (ARM) formerly 8MAN > ARM - Knowledgebase Articles > Error checking or settings FullLanguage mode for Exchange scan

Error checking or settings FullLanguage mode for Exchange scan

Updated November 7, 2018

Overview

This article details an issue in which you receive an error message in Exchange when checking or setting the FullLanguage mode for the Exchange scan in web.config:

exchange_error_fullang_scan_1.png

 

The error message is accompanied by a log entry in the pnServer.congif.xml file found under the path C:\Program Files\Protected Networks\8MAN\etc\pnServer.config.xml:

220 | 8MAN | pnJob | 6092.1 | 15 | 8MAN-DEMO \ 8man_admin | pn.framework.Parall ... eRootTreeNodeWorker] | 161026 | 9: 39: 04.839 | Error] ParallelTreeWorker`1.processTreeNode (T treeNode): libPowerShellConnector.powershell.RunspaceNotAvailableException: Scripts not executable. ---> libPowerShellConnector.powershell.RunspaceNotAvailableException: Scripts not executable.

 

You may also see the following error message when opening the IIS/Exchange Backend/PowerShell proxy:

exchange_error_fullang_scan_2.png

Environment

  • Access Rights Manager

Cause

This issue may be caused by a faulty entry in the IIS/PowerShell.

Resolution

  1. Log in to the server running your IIS service.
  2. Open the application settings in IIS that appears in the error message. For example, in the above image: PowerShell Proxy\web.config
  3. Open the folder view.
  4. Using a text editor, open web.config.
  5. Find and delete the duplicate entry.

    exchange_error_fullang_scan_3.png

  6. Restart IIS to load the changes.

 

 

 
Last modified

Tags

Classifications

Internal Use Only