Article ID: 930706
Article Last Modified on 5/14/2007
APPLIES TO
- Microsoft SoftGrid for Terminal Services
- Microsoft SoftGrid for Windows Desktops
SYMPTOMS
When you start an application in Microsoft SoftGrid Client, the operation is unsuccessful. Additionally, you receive the following error message:
Additionally, the following error message is logged in the SoftGrid Client log file (Sftlog.txt):
CAUSE
This issue occurs because the SoftGrid Client cannot communicate with the SoftGrid Virtual Application Server.
MORE INFORMATION
The protocol, the server name, and the port of the SoftGrid Virtual Application Server are specified in the HREF attribute of the CODEBASE element in the .osd file as follows:
HREF="protocol
://server_name
:port
The default protocol is RTSP. The alternative protocol is RTSPS.
The default server name is %SFT_SOFTGRIDSERVER%. This environmental variable must be configured on the SoftGrid clients. This variable can be replaced with the host name, with the DNS name, or with the IP address of the server or of the load balancing device.
The default port is 554. Alternative ports include but are not limited to 332 and 443.
Examples of the HREF attribute are as follows:
HREF="rtsp://%SFT_SOFTGRIDSERVER%:554/DefaultApp.sft"
HREF="rtsps://%SFT_SOFTGRIDSERVER%:332/DefaultApp.sft"
If the protocol, the server name, or the port is invalid, the application will not start.
If the protocol, the server name, and the port are valid, perform the following procedures to diagnose the issue.
Verify that the SoftGrid Virtual Application Server service is started
To do this, follow these steps:
- Click Start, point to All Programs, point to Administrative Tools, and then click Services.
- In the Name column, locate SoftGrid Virtual Application Server.
- Verify that Started appears in the Status column.
- If the service is not started, right-click SoftGrid Virtual Application Server, and then click Start.
- If the service does not start, search the Microsoft Knowledge Base for the message that is reported. To do this, visit the following Microsoft Web site:
Verify that the client can ping the server name
To do this, follow these steps:
- Open a command prompt.
- Type ping
SERVERNAME PORT
, and then press ENTER. For example, type the following command, and then press ENTER:ping %SFT_SOFTGRIDSERVER% 554
- If the ping is successful, you receive the following message:
- If the ping is unsuccessful, you receive the following message:
If the client cannot ping the server, a network-related issue is preventing the client from communicating with the server. The network-related issue must be corrected before an application can be started. Contact the network administrator.
Verify that the client can telnet to the server name and to the port
To do this, follow these steps:
- Open a command prompt.
- Type telnet
SERVERNAME PORT
, and then press ENTER. For example, type the following command, and then press ENTER:telnet %SFT_SOFTGRIDSERVER% 554
- If the connection is successful, the window appears to be blank. Press ENTER two times. You receive the following message:
If the connection is unsuccessful, you receive the following message:
If the client can ping the server but cannot telnet to the server, verify that port traffic between the client and the server is not restricted by a firewall or by software. Contact the network administrator.
Keywords: kbtshoot kbexpertiseinter KB930706