Virtual Desktops 7.15 CU3 - On Studio - Machine catalogs, keeps spinning for long time and never displays the list of the machines.

Virtual Desktops 7.15 CU3 - On Studio - Machine catalogs, keeps spinning for long time and never displays the list of the machines.

book

Article ID: CTX249836

calendar_today

Updated On:

Description

Virtual Desktops 7.15 CU3 - On Studio - Machine catalogs, keeps spinning for long time and never displays the list of the machines.

As per the CDF logs uploaded, there found exceptions related to communication for Get-ProvTask execution.
261057,0,2019/03/18 13:19:16:45184,6716,2288,1,Xendesktop Management Console,,0,,1,Information,"CmdletExecutionLog(774): Script GetSdkProvisioningTasksScript(773): The command; Get-ProvTask  -AdminAddress ""DDCServername:80"" -MaxRecordCount 2147483647, Took 719.33 seconds to execute",""
261058,0,2019/03/18 13:19:16:45230,6716,2288,1,Xendesktop Management Console,,0,,1,Information,"::-2fd6ed23-e814-4508-ba7b-9be7bb5c8a16:Executing Cmdlet: Get-ProvTask",""
261059,0,2019/03/18 13:19:16:45786,6716,2288,1,Xendesktop Management Console,,0,,1,Information,"Attempting to resolve the error CommunicationError to a resource string.",""

 

Running just the command Get-ProvTask on DDC - runs and gives 250 max records, however there are more records.

When ran the same command as listed in CDF- Get-ProvTask  -AdminAddress ""DDCServername:80"" -MaxRecordCount 2147483647, gave error as below in the powershell as well:
"The maximum message size quota for incoming messages (41943040) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.QuotaExceededException: The maximum message size quota for incoming messages (41943040) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element."

Resolution

Check any active / pending tasks by running powershell command "Get-Provtask -Active $True" on DDC server:
Review the output:
If there are any pending tasks found, review the tasks and if they are pending for very long time - check and delete the long pending tasks.
If there are any Active task - let them finish the task.

If there are no out resulted for the above command - then run the below command to delete the already completed old MCS tasks.
Get-ProvTask –active $false | Remove-ProvTask

Once the tasks are deleted, open Studio and check the machine catalogs tab (you should be seeing the faster response).

Problem Cause

Get-provtask output has many entries due to frequent updates on machine catalogs / creation of catalogs.