Microsoft KB Archive/930769

= Error message when you try to start an application in Microsoft SoftGrid &quot;Error code: xxxxxx-xxxxxx0A-0000800B&quot; =

Article ID: 930769

Article Last Modified on 5/3/2007

-

APPLIES TO


 * Microsoft SoftGrid for Terminal Services
 * Microsoft SoftGrid for Windows Desktops

-



SYMPTOMS
When you try to start an application in the Microsoft SoftGrid Client, you may receive the following error message:

The SoftGrid Client could not launch ApplicationName.

The package requested could not be found in the system data store or the files associated with this package could not be found on the server. Please report the following error code to your System Administrator.

Error code: xxxxxx-xxxxxx0A-0000800B

The SoftGrid client could not launch ApplicationName.

The URL refers to a file that does not exist. Please report the following error code to your System Administrator.

Error code: xxxxxx-xxxxxx0A-0000800B



CAUSE
This problem occurs because one of the following conditions is true:
 * The HREF path in the .osd file is invalid. Specifically, the HREF attribute of the CODEBASE element contains invalid information
 * The Provider Policy that is specified in the .osd file is invalid. Specifically, the Provider Policy is specified by using ?Customer=. However, the Provider Policy does not exist.
 * The SoftGrid Virtual Application Server service logon account does not have Read File permissions to the .sft files.



The HREF path in the .osd file is invalid
To resolve this problem, use a text editor to modify the .osd file. Determine whether the path, the server name, the port, the folders, and the .sft file are valid.

For example, the .sft file is located on the SoftGrid Virtual Application Server in the following location:

C:\Program Files\Softricity\SoftGrid Server\content\Softricity\sft_ea70.v1.sft

In this example, you must modify the HREF path to resemble the following code example. I HREF=&quot;rtsp://%SFT_SOFTGRIDSERVER%:554/Softricity/sft_ea70.v1.sft&quot;

The Provider Policy that is specified in the .osd file is invalid
To resolve this problem, use a text editor to modify the .osd file. Correct the Provider Policy.

For example, the SoftGrid environment has multiple Provider Policies. They include a default provider and a custom provider that is named Anonymous. You want to configure an .osd file to use the Anonymous Provider Policy. In this example, you must modify the .osd file to resemble the following code example. HREF=&quot;rtsp://%SFT_SOFTGRIDSERVER%:554/Softricity/sft_ea70.v1.sft?Customer=Anonymous&quot;

The SoftGrid Virtual Application Server service logon account does not have Read File permissions to the .sft files
To resolve this problem, grant the account at least Read File permissions to the .sft file. It is preferred to grant the account Read File permissions for the whole CONTENT folder. This step helps prevent this problem on other .sft files. By default, this logon account is the Local System (SYSTEM) account.

To verify the account from the SoftGrid Virtual Application Server, follow these steps:
 * 1) In the Administrative Tools Microsoft Management Console (MMC) snap-in, click Services.
 * 2) Right-click SoftGrid Virtual Application Server, and then click Properties.
 * 3) Click the Log On tab.

Notice the account that is specified under Log on as.

Keywords: kbexpertiseinter kbtshoot KB930769

-

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

© Microsoft Corporation. All rights reserved.