Application Virtualization Server Status

Microsoft.AppVirtualization.Server.45.ServerStatus.HealthState (AggregateMonitor)

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.

Verifier

To verify if the Application Virtualization Server service is running:

  1. Open Services. (Click Start, click Settings, click Control Panel, click Administrative Tools, and then double-click Services).
  2. When Services opens, locate Application Virtualization (Management/Streaming) Server service and double-click it to open its Properties dialog box.
  3. When the Application Virtualization Server Properties dialog box opens, verify that the Service Status reads Started.
  4. Open Task Manager. (Press Ctrl+Alt+Del, and click Task Manager).
  5. Verify that SFTDispatcher.exe and more than one SFTCore.exe processes are running.

To verify that the Application Virtualization clients can communicate with the server, "ping" the server name.  To do this, follow these steps

  1. Open a Command Prompt window.  Type ping SERVERNAME, and then press ENTER.  For example ping SERVERNAME.
  2. If the ping command is successful, you will receive the following message:

    Pinging SERVERNAME xxx.xxx.xxx.xxx with 32 bytes of date: Reply from xxx.xxx.xxx.xxx : bytes=32 time<1ms TTL=128

  3. If the ping command is unsuccessful, you receive the following message:  Ping request could not find host SERVERNAME.  Please check the name and try again.If you received this message, a network related issue may be preventing the client from communicating with the server.  The network related issue must be corrected before an application can be streamed. 

Verify that the client can use the configured ports to connect, use the telnet command to communicate with the server and with the port.

  1. Open a Command Prompt window.
  2. Type telnet SERVERNAME PORT, and then ENTER.  For example, type telnet SERVERNAME 554.  If the connection is successful, the window will be blank.  In this case, press ENTER two times.  You will receive the following message:

    RTSP/1.0 400 Bad Request Server: Application Virtualization Server/ x.x.x.xxx [Win32; Windows NT x.x ] Date: xxx, xx xxx xxxx xx:xx:xx xxx

  3. If the connection is unsuccessful, you will receive the following message:  Could not open connection to the host, on port 554: Connection failed.

If the client can "ping" but not "telnet" to the server, verify that the port traffic between the client and the server is not restricted by a firewall or by other software.  To do this, contact a network adminstrator.

Problems can occur if there is insufficient disk space on the drive that holds the Application Virtualization Server content. You can find the content directory location listed in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\DistributionServer\PackageRoot registry value.

To create extra disk space you can

  1. Empty recycle bin.
  2. Consider deleting files in temp directory, if the temp directory and the content directory are in the same drive. To determine the drive of the temp folder, you can
    • Open Command prompt.

    • Type echo %temp%. This returns the location of temp directory.

    • Run "cd %temp%". Now, delete all the files and folders underneath this directory. Do not delete directory. Only delete files and folders underneath the %temp% directory.

  3. Move some files to a different partition, drive or computer.

Element properties:

TargetMicrosoft.AppVirtualization.Server.45.SoftGridServerRole
Parent MonitorSystem.Health.AvailabilityState
AlgorithmWorstOf
CategoryOperations
EnabledTrue
Alert GenerateFalse
Alert Auto ResolveFalse
RemotableTrue
AccessibilityPublic

Source Code:

<AggregateMonitor ID="Microsoft.AppVirtualization.Server.45.ServerStatus.HealthState" Accessibility="Public" Target="Microsoft.AppVirtualization.Server.45.SoftGridServerRole" ParentMonitorID="Health!System.Health.AvailabilityState">
<Category>Operations</Category>
<Algorithm>WorstOf</Algorithm>
</AggregateMonitor>