Citrix Virtual Apps and Desktops: Issues with Monitor Service after upgrade to 2402 CU2
book
Article ID: CTX693068
calendar_today
Updated On:
Description
Environment has been upgraded to 2402 CU2 version.
When admin invokes a cmdlet: Get-MonitorConfiguration, the error is displayed: A database operation failed and could not be recovered : Reason ?
Not all Delivery Controllers are affected and cmdlet returns actual configuration on some of the Delivery Controllers (This is import as this indicates that the issue is most likely with one of the controllers and not with the database or settings stored in the database).
CDF Control trace captured on the DDC shows the error:
Monitor System Setting 'GroomMachinePowerActionLogRetentionDays' exists in the database was loaded but not found in class MonitorSystemConfiguration.
Environment
The above mentioned sample code is provided to you as is with no representations, warranties or conditions of any kind. You may use, modify and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the sample code may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the sample code fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the sample code. In no event should the code be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SAMPLE CODE, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Although the copyright in the code belongs to Citrix, any distribution of the sample code should include only your own standard copyright attribution, and not that of Citrix. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the sample code.
Resolution
Verify if there is a version mismatch between different Delivery Controllers and database.
On one of the delivery controllers, open PowerShell as administrator and check cmdlets:
- Get-MonitorService | select DNSName, ServiceVersion
- Get-MonitorInstalledDBVersion
Example - If 2402 CU2 version was installed with the latest Monitor Service:
Get-MonitorService | select DNSName, ServiceVersion
DNSName ServiceVersion
------- --------------
DDC1.TEST.COM 7.43.100.71
DDC2.TEST.COM 7.43.100.71
Get-MonitorInstalledDBVersion
Major Minor Build Revision
----- ----- ----- --------
7 43 100 0
Example - If 2402 CU2 version was installed without the latest Monitor Service:
Get-MonitorService | select DNSName, ServiceVersion
DNSName ServiceVersion
------- --------------
DDC1.TEST.COM 7.41.2100.17
Get-MonitorInstalledDBVersion
Major Minor Build Revision
----- ----- ----- --------
7 41 2100 0
If you see a mismatch:
- Monitor Service is on the lower version than database, for example Service version 7.41 and Database schema 7.43; Monitor Service on the Delivery Controller should be upgraded using installation media.
- If the version of Monitor Service is higher than the database schema; Database should be upgraded using Site Manager (there should be a prompt to upgrade database).
Problem Cause
Database Schema and monitor service versions mismatch.
Admin selected an option "Install the Director Current Release and update Monitoring Service" during CU2 installation on some of the Delivery Controllers only.
Was this article helpful?
thumb_up
Yes
thumb_down
No