Skip to main content

Since couple of weeks back, we are getting an error during PSO6 installations.

According to the error the issue is related to VM Scale Sets and Command Script Extension.

  • We are doing PSO Azure installation with interactive login.
  • Have tried with PSO versions 6.8.0.23 and 6.9.0.18. Both give the same error.
  • Have done many number of installation attempts without success.
  • Error is not specific to Azure region or subscription as we have come across the issue in different installations.

 

 

VM has reported a failure when processing extension 'ifsauprodpsoap003vmssCSE'. Error message: "Command execution finished, but failed because it returned a non-zero exit code of: '1'. The command had an error output of: 't Ops File "C:\Program Files\Python37\lib\site-packages\thinc\backends\__init__.py", line 7, in <module> from .ops import Ops File "C:\Program Files\Python37\lib\site-packages\thinc\backends\ops.py", line 13, in <module> from ..util import ...' For more information, check the instance view by executing Get-AzVmssVm or Get-AzVm (https://aka.ms/GetAzVm). These commands can be executed using CloudShell (https://aka.ms/CloudShell)" More information on troubleshooting is available at https://aka.ms/VMExtensionCSEWindowsTroubleshoot
 

 

 

 

Not sure if there are any recent changes in Azure and now the PSO installers are not compatible with those changes.

Would appreciate any advice on getting this installation issue resolved.

 

Hi plavyronp,

We have a fix coming for this issue.  It will be in PSO 6.9.0.22, which should be available next week.

Thanks,

Carl

Thanks for information, Carl

Hi is this available yet?

I have same issue..

Sorry everyone, there were some delays due to IT issues, but the latest update is available now as PSO v6.9.0.22

Hi Carl, 

it was resolved by rerunning this installer. My question is how it happened in the first place and how can we can ensure it will not happen again?

In our case it happened after an upscale on the LB.

Thank you,

Charalampos

Hi Charalampos,

As far as we can tell, there was a change in the Azure components provided by Microsoft, which has caused some issues with specific components of the PSO installation.  Being part of a Microsoft update, there is a chance that this could have affected some existing installations as a part of instance scaling, which I think is likely what you have seen.

Thanks,
   Carl

Hi All,

we have the same issue with version 6.10.0.7

does anyone have any recommendations? 

 

thanks

Gary

Reply


Terms & ConditionsCookie settings