After execution of Check requirements and Configuration for Citrix MPXAXD Agent task, the following error is returned:
'connection-discovery'                          Not Operational
       Workflow error                                OData server returned: 500 Internal Server Error”

After execution of Check requirements and Configuration for Citrix MPXAXD Agent task, customer should verify which version of Citrix OData URL is used “v1” or “v2”:
 
Citrix XenApp/XenDesktop OData Interface            [   OK   ]
------------------------------------------------------------
URL:  http://st1w1011/Citrix/Monitor/OData/v1/data/
Configured interface accessible                     Yes
 
In case if Citrix XenApp/XenDesktop OData Interface URL is configured with v1, there should be verified if v2 exist and change Citrix MPXAXD Citrix OData Interface URL.
To list all available Citrix OData interfaces, execute following steps:

• Go directly on XD Delivery controller where issue was detected
• Start PowerShell as Administrator and execute following commands

o    add-pssnapin Citrix.Configuration.Admin.*
o    get-configregisteredserviceinstance -servicetype Monitor -interfacetype odata


If Odata URL with version v2 is listed, please perform following steps:

• Open/Verify one of the Citrix Odata URL’s in web browser (e.g. ​http://<hostname>/Citrix/Monitor/OData/v2/data/)

Login with MPXAXD Agent account 

 

• If you get the following result, then Citrix OData URL is working fine. In next step you need to configure Citrix OData Interface for Citrix XenApp/XenDesktop MP agent.
• Open Registry editor and navigate to following registry key: “HKEY_LOCAL_MACHINE\SOFTWARE\Comtrade\XenDesktop MP Agent”
• Add working Citrix OData URL (http://<hostname>/Citrix/Monitor/OData/v2/Data/) into the ‘ODataClientUrl’ registry key and save it.

 

• Restart ‘Citrix MPXAXD Agent’ service
• Re-run “Check Requirements and Configuration for Citrix MPXAXD Agent” task and verify the output
• The connection section output should be positive for Citrix OData URL.

 
 
NOTE: This Citrix OData URL configuration is relevant for Citrix XenApp and XenDesktop version 7.5 and above where is used new version of Citrix OData interface (v2). The Older versions of Citrix XenApp and XenDesktop are using Citrix OData Interface version (v1).
 

---

Problem Cause

The reason for such behavior lies in different versions of Citrix Odata URL's (v1 and v2).
Issue exists only on Controllers that are Site Data Collectors and if v1 is set in registry, but v2 is available (for XAXD version 7.6 and newer).

Site Data Collector collects information about user connections (including failed connections) on a site-level. And while querying this data we get errors while using v1 on XAXD 7.6 or newer, due to changes between v1 and v2.

Querying v1 on XAXD 7.5 or older, the same query works fine.
So:

•           v1 should be used for MP Agents on XAXD <= 7.5,
•           v2 should be used for MP Agents on XAXD >= 7.6

In case when Citrix MPXAXD Odata is configured with Citrix Odata v1 and failed connection occurs on XAXD 7.6 or newer, exception will be thrown.
 

Error: "OData Server Returned: 500 Internal Server Error” - Making Connection Discovery is not Operational - SCOM Management Pack (ComTrade)

-