Home
  •  

Server Status - Verify core connectivity configurations - Application

Microsoft.AppVirtualization.Server.45.LightWeightServer.ServerStatus_Verifycoreconnectivityconfigurations_Application (UnitMonitor)

The Server Status provides information to help you monitor that the Application Virtualization Server and verify that it is running properly and providing its expected services.

Knowledge Base article:

Summary

The Server Status provides information to help you monitor that the Application Virtualization Server and verify that it is running properly and providing its expected services.

Cause

This issue may occur when the Application Virtualization Server cannot connect to the domain, to the domain name system (DNS), or to the database before the time-out interval elapses.

Resolutions

This error code is addressed in Knowledge Base Article 931166. 

SYMPTOMS

  1. When you try to start the Application Virtualization Application Streaming Server service, the service does not start.
  2. Additionally, you receive the following error message: "Windows could not start the Application Virtualization Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 41476. "
  3. Additionally, the following event is logged in the System log: Event ID: 7024 Source: Service Control Manager Type: Error Description: The Application Virtualization Server service terminated with service-specific error 41476.
  4. Additionally, the following error code is logged in the Application Virtualization Server log file (Sft-server.log):   41476 "Unable to start core process: Timeout waiting for Core to start."

CAUSE

This issue may occur when the Application Virtualization Server cannot connect to the domain, to the domain name system (DNS), or to the database before the time-out interval elapses.
 
RESOLUTION
 
To resolve this issue
  1. Verify connectivity to the domain, to the DNS, and to the database.
  2. Then, verify the number of core processes that are configured. By default, the Application Virtualization Server is configured to have three core processes. The core process time-out interval is 60 seconds. Therefore, it may take 180 seconds for the service to start. If each core process does not connect to the domain, to the DNS, and to the database within 60 seconds, the service does not start.

To confirm the number of core processes that are configured, follow these steps:

  1. From the registry editor, regedit.exe.
  2. Under the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\DistributionServer locate the NumCores value and check for the value.  5 is the Default.

Element properties:

TargetMicrosoft.AppVirtualization.Server.45.LightWeightServer
Parent MonitorMicrosoft.AppVirtualization.Server.45.ServerStatus.HealthState
CategoryEventCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.SingleEventLogManualReset2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Server Status - Verify core connectivity configurations - Application
{0}
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.AppVirtualization.Server.45.LightWeightServer.ServerStatus_Verifycoreconnectivityconfigurations_Application" Accessibility="Public" Target="Microsoft.AppVirtualization.Server.45.LightWeightServer" TypeID="Windows!Microsoft.Windows.SingleEventLogManualReset2StateMonitorType" ParentMonitorID="Microsoft.AppVirtualization.Server.45.ServerStatus.HealthState">

  <Category>EventCollection</Category>

  <AlertSettings AlertMessage="Microsoft.AppVirtualization.Server.45.LightWeightServer.ServerStatus_Verifycoreconnectivityconfigurations_Application.Alert">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="EventRaised" MonitorTypeStateID="EventRaised" HealthState="Error"/>

    <OperationalState ID="ManualResetEventRaised" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

    <LogName>Application</LogName>

    <Expression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="String">PublisherName</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">Application Virtualization Server</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="UnsignedInteger">41476</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </Expression>

  </Configuration>

</UnitMonitor>