Error in Citrix Cloud (DaaS) when creating a MCS Machine Catalogue

[Fernando Farabote]

When trying to create a new Machine Catalogue or manipulating existing one, I'm getting the errors below.

This is happening on 2 different environments I have. It was working fine last week and nothing was changed or updated.

 

Citrix Cloud (DaaS) with Nutanix AHV

I have 4 Nutanix Cluster, 2 in each environment. Error is the same on all of them.

 

I have another Citrix Cloud tenant in the same pair of Nutanix and is working fine as well as onprem DDCs also working fine.

 

Following the errors log.

 

StudioErrorId : ProvisioningSchemeNotFound
Error Source : CitrixMachineCreationService
Sdk Error Message : The specified ProvisioningScheme could not be located.
Sdk Error ID : Citrix.XDPowerShell.MachineCreationStatus.ProvisioningSchemeNotFound,Citrix.MachineCreation.Sdk.Commands.GetProvImageRuntimeEnvironmentCommand
ErrorCategory : ObjectNotFound
DesktopStudio_PowerShellHistory : Create Machine Catalog 'TSTMC'

 

Or

 

 StudioErrorId : ExceptionThrown
    Reason : XaxdProxyDisconnectedException
    Exception : Citrix.HypervisorCommunicationsLibrary.Wcf.Types.Exceptions.XaxdProxyDisconnectedException: Could not connect to the Remote Broker Provider service due to exception: System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error. ---> System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
    Message : Could not connect to the Remote Broker Provider service due to exception: System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

 

Or

 

StudioErrorId : ProvisioningSchemeNotFound
Error Source : CitrixMachineCreationService
Sdk Error Message : The specified ProvisioningScheme could not be located.
Sdk Error ID : Citrix.XDPowerShell.MachineCreationStatus.ProvisioningSchemeNotFound,Citrix.MachineCreation.Sdk.Commands.GetProvImageRuntimeEnvironmentCommand
ErrorCategory : ObjectNotFound
DesktopStudio_PowerShellHistory : Create Machine Catalog 'MCTST'

[Brenton Crosby]

I'm getting a very similar error when updating deployment image for an MCS template server. Wonder if it's a Citrix CLoud thing? Using vmware 8 hypervisor here

 

I'm getting the 2nd error. 

[Paul McCran1709162838]

Hi,

 

I would contact Citrix support.  This might be related to a known issue that they are currently investigating.  You might see errors such as " the given key was not present on the dictionary"

 

The temporary fix for some customers is to have the Citrix Cloud hosting\mcs services restarted on their Citrix cloud tenant. Citrix are working on a new  release to resolve this

 

You'll spend hours\days testing things on your resource locations, so it's worth checking this to save you some time. It only happens  on-premise Resource  locations, apparently not for AWS or Azure or CGP

 

Download the Cloud connector test tool:

 

 https://support.citrix.com/article/CTX260337/cloud-connector-connectivity-check-utility

 

In the DAAS hamburger menu, select "Identity and Acces Management"

Click on "API Access"

Create a new client

Use the Identity and Secret in the Cloud connector test tool when it prompts you

 

Citrix might also ask for the HAR logs while you create the catalog.  For example, in Edge, click the top right corner 3 dots, more tools, developer tools, click on network tab and tick preserve log.  Run the catalog creating. Save the logs

 

 

[Fernando Farabote]

Hi All,

 

Just as a feedback. After contact Citrix as well as Nutanix.

This is a known issue in Nutanix Side bug ENG-519622.

 

You can use this link to see the errors between Cloud Connectors and Nutanix Prism -> https://portal.nutanix.com/page/documents/kbs/details?targetId=kA032000000CiSiCAK

 

The temporary workaround is to restart the Prism service on the Prism leader CVM, which doesn’t cause any outage.