IM provisioning error: "The syntax is not supported by this runspace" after applying Microsoft Exchange Server patch KB5001779
search cancel

IM provisioning error: "The syntax is not supported by this runspace" after applying Microsoft Exchange Server patch KB5001779

book

Article ID: 213050

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager

Issue/Introduction

Microsoft recently released security update for Microsoft Exchange Server 2019, 2016, and 2013: April 13, 2021 (KB5001779
https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-april-13-2021-kb5001779-8e08f3b3-fc7b-466c-bbb7-5d5aa16ef064
which changed the commands required to interact with Exchange.   

After applying KB5001779 Provisioning against Exchange fails with the error message:

System.Management.Automation.RemoteException: The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.

Create User called failed:

The syntax is not supported by this runspace.  This can occur if the runspace is in no-language mode.

Environment

Release :  14.2, 14.3, 14.4 

Component : CA IDENTITY SUITE (both VIRTUAL APPLIANCE and stand-alone on-premises deployments) 

Cause

Known Issue from Microsoft:

https://techcommunity.microsoft.com/t5/exchange-team-blog/released-april-2021-exchange-server-security-updates/ba-p/2254617

Known Issues

After application of the Exchange Server April security update CMDlets executed against the Exchange Management Console using an invoked runspace might fail with the following error message:
The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.
This behavior is expected; please change any code using .AddScript() to use .AddCommand() for continued compatibility.

 

 

 

Resolution

We have published the hot fixes in support.boradcom.com so that customers can download them from the support site. Below are the links for 14.2, 14.3, and 14.4 respectively

14.2 HotFix: 
We have recently released 14.2 CP6 which includes this fix.  You can get CP6 through the documentation
Latest Cumulative Patch - 14.2 CP6
For clients at CP5 already that do not wish to immediately apply CP6 the hotfix can be applied:
https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU01088&os=WINDOWS-ALL


14.3 HotFix: 

https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU01090&os=WINDOWS-ALL


14.4 HotFix:

https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU01091&os=WINDOWS-ALL

Important: If Exchange is used with an agent, please ensure to replace the existing E2K7PS.dll with the one provided as part of the hotfix. You would need to follow https://knowledge.broadcom.com/external/article/130060/idm-exchange-2016-agent-fails.html to unregister and then re-register the dll.

Additional Information

Broadcom Proactive Notification

https://support.broadcom.com/external/content/product-advisories/Microsoft-Exchange-Server-April-2021-Update-Causes-Broadcom-Exchange-Connector-Failures/18016

FAQ

Q1: Does the Exchange hotfix (DE500337) work with IM environments where the latest Exchange Security patch has not been installed?

A1: Yes.  We have rewritten the code to comply with Microsofts new recommended practices but the IM patch is not dependent upon the MS Security Patch.

Q2: We have installed the 14.3 hotfix HF-DE480544 on our Exchange connectors. It replaces the same DLLs (E2K7PS.dll W2KNamespace.dll). Is this fix included in the new 14.3 Exchange Hotfix (DE500337)?

A2: Yes, the 14.3 DE500337 does include the 14.3 HF-DE480544 fix .