When you try to start or to load an application in Microsoft SoftGrid Client, the operation is unsuccessful. Additionally, you receive one of the following error messages:
The SoftGrid Client could not launch application_name.
The host name or IP address specified was invalid and the SoftGrid Client was unable to enter into disconnected operation mode. Please check your network connection and try again. If the problem persists, please report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx0B-8006B02B
The SoftGrid Client could not load application_name.
The host name or IP address specified was invalid and the SoftGrid Client was unable to enter into disconnected operation mode. Please check your network connection and try again. If the problem persists, please report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx0B-8006B02B
This issue occurs when the SoftGrid Client is unable to communicate with the SoftGrid Virtual Application Server, and when the application is not 100 percent loaded in cache.
The protocol, the server name, and the port in 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, the DNS name, or 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 are not valid, the application will not start.
If the protocol, the server name, and the port are valid, diagnose and troubleshoot the issue by using the following methods.
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 is displayed in the Status column.
- If the service is not started, right-click SoftGrid Virtual Application Server, and then click Start.
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 operation is successful, you receive the following message:
Pinging SERVERNAME xxx.xxx.xxx.xxx with 32 bytes of data:
Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=128
If the ping operation is unsuccessful, you receive the following message:
Ping request could not find host SERVERNAME. Please check the name and try again.
If the client cannot ping the server, a network-related issue is preventing the client from communicating with the server. You must correct the network-related issue before you can start an application. To do this, 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 Command Prompt window will appear to be blank. Press ENTER two times. You receive the following message:
RTSP/1.0 400 Bad Request
Server: Softricity SoftGrid Server/x.x.x.xxx [Win32; Windows NT x.x]
Date: xxx, xx xxx xxxx xx:xx:xx xxx
If the connection is unsuccessful, you receive the following message:
Could not open connection to the host, on port 554: Connect failed
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. To do this, contact the network administrator.