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

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 $nullSet-MonitorDBConnection -DBConnection $nullSet-LogDBConnection -DataStore Logging -DBConnection $nullSet-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 $csSet-LogDBConnection -DataStore Logging -DBConnection $csLoggingSet-MonitorDBConnection -DBConnection $csSet-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.

Related:

  • No Related Posts

XenApp 7.x: Error: the data base is already been configured

Error: the data base is already been configured.

Error Id: XDDS:36FD07F4

Exception:

Citrix.Console.Models.Exceptions.ScriptException The database has already been configured.

at Citrix.Console.PowerShellInteraction.CmdletExecutionMethods.CreateException[T](ICommonLog logger, ExecutionResults`1 results, ICmdletExecutionHost host)

at Citrix.Console.PowerShellInteraction.CmdletExecutionMethods.Execute[T](ISdkCmdlet`1 sdkCmd, ICmdletExecutionHost host, Boolean allowFailover)

at Citrix.Console.PowerShellInteraction.SdkServiceBase.SetDatabaseConnection(ICmdletExecutionHost cmdletExecutionHost, String instanceAddress, DataStore dataStore, String databaseConnection, Boolean force)

at Citrix.Console.PowerShellSdk.UpgradeService.UpgradeTasks.ServiceConfigurationTask.AttachServiceDatastoresToDatabaseServer(ServiceEndpointAnalysis servicesWithUnregisteredServiceInstance, ICmdletExecutionHost host, String databaseConnection)

at Citrix.Console.PowerShellSdk.UpgradeService.UpgradeTasks.ServiceConfigurationTask.<>c__DisplayClass10_0.<RunUpgradeTask>b__5(ICmdletExecutionHost host)

at Citrix.Console.PowerShellInteraction.SimplePowerShellScript.<>c__DisplayClass4_0.<Run>b__0(ICmdletExecutionHost host)

at Citrix.Console.PowerShellInteraction.PowerShellScript`1.Run()

at Citrix.Console.PowerShellSdk.UpgradeService.UpgradeTasks.ServiceConfigurationTask.RunUpgradeTask(IProgressReporter progressReporter, ITaskLogger taskLogger)

at Citrix.Console.PowerShellSdk.UpgradeService.UpgradeTasks.UpgradeTaskBase.RunUpgrade(IProgressReporter progressReporter, ITaskLogger taskLogger)

at Citrix.Console.PowerShellSdk.UpgradeService.UpgradeTasks.UpgradeTaskBase.RunUpgrade(IProgressReporter progressReporter, ITaskLogger taskLogger)

at Citrix.Console.PowerShellSdk.UpgradeService.UpgradeTasks.Upgrade.RunUpgradeTask(IProgressReporter progressReporter, ITaskLogger taskLogger)

at Citrix.Console.PowerShellSdk.UpgradeService.UpgradeTasks.UpgradeTaskBase.RunUpgrade(IProgressReporter progressReporter, ITaskLogger taskLogger)

at Citrix.Console.DeliveryCenter.UI.Mmc.UpgradeResultPaneViewModel.UpgradeTask(IProgressReporter progressReporter, UserCredentials databaseCredentials)

at Citrix.Console.Common.OperationTimer.TimeBlock(Action operation)

at Citrix.Console.CommonControls.ProgressDisplay.GenericProgressOperationWithFeedBack.PerformOperationInternal()

at Citrix.Console.CommonControls.ProgressDisplay.ProgressWindowOperation.PerformOperation()

at Citrix.Console.CommonControls.ProgressDisplay.ProgressWindowViewModel.PerformAction(Action operationComplete)

DesktopStudio_ErrorId : DatabaseConnectionDetailsAlreadyConfigured

Sdk Error Message : Cannot transition directly from using one data store to another; clear the existing data-store connection first.

Sdk Error ID : Citrix.XDPowerShell.Status.DatabaseConnectionDetailsAlreadyConfigured,Citrix.EnvTest.Sdk.DataStore.Commands.SetEnvTestDBConnectionCommand

ErrorCategory : NotSpecified

DesktopStudio_PowerShellHistory : SimplePowerShellScript

Related:

  • No Related Posts

Powershell Snap in giving error when Authenticating: “[New-SfClient], HttpRequestException + FullyQualifiedErrorId : System.Net.Http.HttpRequestException,ShareFile.Api.Powershell.NewSfClient”

When User tries to authenticate the Powershell snap in with the New-SfClient command.

Powershell gives the following error:

PS C:Windowssystem32> New-SfClient New-SfClient : An error occurred while sending the request. At line:1 char:1 + New-SfClient + ~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-SfClient], HttpRequestException + FullyQualifiedErrorId : System.Net.Http.HttpRequestException,ShareFile.Api.Powershell.NewSfClient

Related:

  • No Related Posts

LHC stops synchronizing when RemotePC-WOL for an MachineCatalog that is using an SCCM hosting connection is enabled

When we enable RemotePC-Wake On Lan for a machine catalog that is using an SCCM hosting connection. Local Host Cache stops synchronizing.

When it is in this state, any modification done to the power management via GUI does not take. But it does when done via PowerShell.

Turning off RemotePC-WOL solves these problems

This behavior does not happen when using other types of hosting connections.

The following gets logged in the application event log:

Log Name: Application

Source: Citrix ConfigSync Service

Date: 7/24/2019 3:24:14 PM

Event ID: 505

Task Category: (1)

Level: Error

Keywords: Classic

User: N/A

Computer:

Description:

The Citrix Config Sync Service failed an import.

Error details:

Attempted operation conflicts with current configuration

In the LHC error log we see:

Could not start Service Broker for database id: 6. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.

Related: