Start to look at Troubleshooting - Simple

Article
03/21/2007

If you have a problem with streaming a package it may be worth you checking some of the following;

Make sure that your package is pointing to the right location for content if it’s in a sub directory. This has caught me out in the past when I first started.....

Also, Check that your OSD file is pointing to the right location also (for example, my ethereal package is in a subfolder called ethereal.v1 ;

When I have had problems is where the OSD file is not pointing not pointing to the sft location due to where I set up VAS server to point to my content share.

Not working example

Working Example

If you’re still having issues start to understand the logs on the client (sftlog.txt) and the server (sft-server.log) file on your SoftGrid Server.

Also look out for the %SFT_SOFTGRIDSERVER% variable that is used.

The OSD file tells the client where to connect for the virtual application stream. It accomplished this through an RTSP or RTSPS URL inside of the CODEBASE tag as seen below:

Sample OSD File

The client uses the host name (“stream” in this example) in the RTSP or RTSPS to direct the connection request to a MSCVAS server. This name may be an IP Address or host name and can be directed to a third-party load balancer for connection distribution as well.

Optionally, this name can be replaced with a variable known as %SFT_SOFTGRIDSERVER%. If this variable is used in place of a host name, the client will use the entry for the environment variable of the same name on the local system. This environment variable may be set any number of ways including through login script.

Hope that this helps and it is just some quick fire steeps for newbies into SoftGrid!

Start to look at Troubleshooting - Simple

Additional resources