The Citrix Licensing service unexpectedly stops on License Server 11.6.1 Build 10007 running on Windows Server 2003, when logging off the server console. This issue occurs when logging off the physical console or logging off RDP session 0 that was established using the /console or /admin switch. Restart the license server. The concurrentstate.xml and the activationstate.xml files are recreated after restarting the license server allowing the Citrix Licensing Service to successfully start and the Citrix License Server to function normally.

• This will force the License Server service to restart anytime it crashes. Combined with BarTender’s “Grace Period”, this should ensure that production is not disrupted by the DST event. To set the service to restart: list=1.Open the Windows Services panel.Double click on the Seagull License Server service.Go to the Recovery tab.
• Use the License Server Administration tool to correct the network license files. Perform the following steps: Navigate to Start All Programs Esko Network License Manager Network License Manager. Click the Tools tab License Server Administration. Click the Handle license files tab. Click the Remove the Barco based license file radio.

Client License Service (ClipSVC) - Windows 10 Service

Provides infrastructure support for the Microsoft Store. This service is started on demand and if disabled applications bought using Windows Store will not behave correctly.

This service exists in Windows 10 only.

Startup Type

Default Properties

Default Behavior

The Client License Service (ClipSVC) is running as LocalSystem in a shared process of svchost.exe. Other services might run in the same process. If Client License Service (ClipSVC) fails to start, the error is logged. Windows 10 startup proceeds, but a message box is displayed informing you that the ClipSVC service has failed to start.

Dependencies

Client License Service (ClipSVC) is unable to start, if the Remote Procedure Call (RPC) service is stopped or disabled.

Restore Default Startup Type for Client License Service (ClipSVC)

Automated Restore

1. Select your Windows 10 edition and release, and then click on the Download button below.

2. Save the RestoreClientLicenseServiceClipSVCWindows10.bat file to any folder on your hard drive.

3. Right-click the downloaded batch file and select Run as administrator.

4. Restart the computer to save changes.

Note. Make sure that the ClipSVC.dll file exists in the %WinDir%System32 folder. If this file is missing you can try to restore it from your Windows 10 installation media.

The Archestra License Server Service Terminated Unexpectedly Unavailable

This article helps you resolve the problems where the SQL Server service and the SQL Server Agent Service may not start on a stand-alone server.

Original product version: SQL Server
Original KB number: 307288

Symptoms

• Issue 1: On a stand-alone server, the MSSQLSERVER service may fail to start, and you receive the following error message:

  An error 1068 - (The dependency service or group failed to start.) occurred while performing this service operation on the MSSQLServer Service.

• Issue 2: Similarly, the SQLServerAgent service may also fail to start, and you receive the following error message:

  An error 1068 - (The dependency service or group failed to start.) occurred while performing this service operation on the SQLServerAgent Service.

  Issue 1 and Issue 2 occur when both of the following conditions are true:

  • The server computer is in a workgroup and not part of a domain.
  • Both the MSSQLSERVER and SQLServerAgent services are set to use a domain account for the startup.

• Issue 3: On a domain member server, the MSSQLSERVER service may not start during the server start, and you receive the following error message:

  The MSSQLSERVER service was unable to log on as domainmssqlsvc with the currently configured password due to the following error: Source: NetLogon Description: There are currently no logon servers available to service the logon request. The MSSQLSERVER service terminated unexpectedly.

This problem occurs when all the following conditions are true:

• The server is part of a domain.
• Both the MSSQLSERVER and SQLServerAgent services are set to use a domain account for the startup.
• The startup mode for the MSSQLSERVER and SQLServerAgent are set to Automatic.

Cause

The Issue 1 and Issue 2 occurs because the server is a stand-alone computer, the NetLogon service does not start on the server, hence no domain-wide logon authentications are possible.

The Issue 3 occurs because SQL Server services try to start before NetLogon service starts.

Resolution

The Archestra License Server Service Terminated Unexpectedly Email

To fix the Issue 1 and Issue 2, follow these steps:

• Change the startup account of both the MSSQLSERVER and SQLServerAgent to use the local system account.

• Restart the server.

The Archestra License Server Service Terminated Unexpectedly Job

To fix the Issue 3, use the following workarounds:

• Configure the SQL Server startup to delayed start for particular Windows servers, other Windows services such as NetLogon complete first and SQL Server starts without problems.

• Configure the SQL Server startup to retry, the startup can be completed on the second startup attempt.

• Change the Duplicate Address Detection (-DadTransmits) value to 1 for all network interfaces on the server. See command Set-NetIPInterface for more information.

• Change the Recovery options for SQL Server and SQL Server Agent services. Specify Restart the service as action for the failure options. You can perform this option from the Services applet of Administrative Tools using the familiar Service Control Manager interfaces.

If the delayed start option can't fix this Issue 3, you can add the following dependencies to the SQL Server service:

• Ip helper service
• Server Service
• Network list service

You can add the dependencies by using the following command:

More information

The Archestra License Server Service Terminated Unexpectedly Account

On a stand-alone computer, the NetLogon Service should be set for manual startup.