Microsoft recently released security update for Skype for Business https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-skype-for-business-server-and-lync-server-may-11-2021-kb5003729-3a6def2e-4b74-480e-bf24-fbec151f10a0), started to get this error:
After applying KB5003729 Provisioning against Skype for Business 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.
This is similar message
Release : 14.2, 14.3, 14.4
Component : CA IDENTITY SUITE (both VIRTUAL APPLIANCE and stand-alone on-premises deployments)
Known Issue from Microsoft:
It's a similar problem we experienced with exchange server when Microsoft released security patches for exchange (please see the Article https://knowledge.broadcom.com/external/article?articleId=213050 about Exchange) but this here is about Skype for Business Server and Lync Server (different issue here).
Known Issues
After application of the Skype for Business May Security update CMDlets executed against the Skype for Business Server 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.
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:
https://support.broadcom.com/download-center/solution-detail.html?aparNo=99111164&os=WINDOWS-ALL
14.3 HotFix:
https://support.broadcom.com/download-center/solution-detail.html?aparNo=99111165&os=WINDOWS-ALL
14.4 HotFix:
https://support.broadcom.com/download-center/solution-detail.html?aparNo=99111166&os=WINDOWS-ALL
This Security Patch from Microsoft on Skype Server that had broken the same API for skype and fixed this above HF.
This HF also includes the Exchange issue is fixed by the mentioned in article
https://knowledge.broadcom.com/external/article?articleId=213050