Error on Studio: "A working instance for the Configuration Logging Service could not be found"

Error on Studio: "A working instance for the Configuration Logging Service could not be found"

book

Article ID: CTX224257

calendar_today

Updated On:

Description

After Starting the automatic Site upgrade, the following error is shown:             
               Delivery Controller address has changed...
               Re-enter the Controller address or try a new one.
               A working instance for the Configuration Logging Service could not be found.


User-added image

  • Checking with Get-command Get*service status and running executing all the servicestatus commands, the LogServiceStatus and MonitorServiceStatus return "DBUnconfigured".
User-added image
  • Checking the DataStore Connection for all the services in the registry under HKLM/SOFTWARE/Citrix/XDServices in the Controllers, the correct string is shown.

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

1. Restart the Citrix services with the following PowerShell commands and then close and reopen Studio:
  • Get-Service Citrix* | Stop-Service -Force
  • Get-Service Citrix* | Start-Service

Note: Studio is not going to show the same error message anymore, and it should prompt for a Mandatory upgrade again. Do not proceed with the upgrade yet, and make sure you have a good backup of the database before continuing with the following steps.

2. Re-register the Log and Monitor services connection strings with the following PowerShell commands:
 
Set-MonitorDBConnection -DataStore Monitor -DBConnection $null
Set-MonitorDBConnection -DBConnection $null
Set-LogDBConnection -DataStore Logging -DBConnection $null
Set-LogDBConnection -DBConnection $null


$cs="Server=$ServerName;Initial Catalog=$SiteDBName;Integrated Security=True"
$csLogging= "Server=$ServerName;Initial Catalog=$LogDBName;Integrated Security=True"
$csMonitoring = "Server=$ServerName;Initial Catalog=$MonitorDBName;Integrated Security=True"


Set-LogDBConnection -DBConnection $cs
Set-LogDBConnection -DataStore Logging -DBConnection $csLogging
Set-MonitorDBConnection -DBConnection $cs
Set-MonitorDBConnection -DataStore Monitor -DBConnection $csMonitoring


3. Proceed with the Mandatory upgrade on Studio by clicking the "Start the automatic Site upgrade" button. If prompted, enter the credentials used by the controllers to connect to the database.

4. Wait for the upgrade to finish, and then Studio should start to work properly.
 

Problem Cause

DBUnconfigured for the Get-LogServiceStatus and Get-MonitorServiceStatus services because the Log Service Instance and Monitor Service Instance were not registered properly .