Microsoft KB Archive/930706

= Error message when you start an application in SoftGrid Client: &quot;The SoftGrid Client could not create a session with the SoftGrid Server. Error code: xxxxxx-xxxxxx0A-000001D1&quot; =

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:

The SoftGrid Client could not launch.

The SoftGrid Client could not create a session with the SoftGrid Server. Please try again in a few minutes.

If the problem persists, please report the following error code to your System Administrator.

Error code: 0A-000001D1

Additionally, the following error message is logged in the SoftGrid Client log file (Sftlog.txt):

The SoftGrid Client could not connect to stream URL '{protocol:// : / / .sft' (FS status: 0A-000001D1).

The Client was unable to connect to a SoftGrid Server (rc 0A-000001D1)



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=&quot; :// :

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=&quot;rtsp://%SFT_SOFTGRIDSERVER%:554/DefaultApp.sft&quot;

HREF=&quot;rtsps://%SFT_SOFTGRIDSERVER%:332/DefaultApp.sft&quot;

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:

http://support.microsoft.com/search/?adv=1



Verify that the client can ping the server name
To do this, follow these steps:  Open a command prompt.</li> Type ping, and then press ENTER. For example, type the following command, and then press ENTER:

ping %SFT_SOFTGRIDSERVER% 554

</li> If the ping is successful, you receive the following message:

Pinging  with 32 bytes of data:

Reply from : bytes=32 time<1ms TTL=128

</li> If the ping is unsuccessful, you receive the following message:

Ping request could not find host. Please check the name and try again.

</li></ol>

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.</li> Type telnet, and then press ENTER. For example, type the following command, and then press ENTER:

telnet %SFT_SOFTGRIDSERVER% 554

</li> If the connection is successful, the window appears to be blank. Press ENTER two times. You receive the following message:

RTSP/1.0 400 Bad Request

Server: Softricity SoftGrid Server/ [Win32; Windows NT ]

Date:

If the connection is unsuccessful, you receive the following message:

Could not open connection to the host, on port 554: Connect failed

</li></ol>

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

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.