List of Softgrid Client Errors

I’m keeping a list of Softgrid errors I’ve encountered in the past for reference:

Softgrid 3.x errors:
Error code: xxxxxx-xxxxxx09-0000E019
According to MS, this is what happens:
This behavior can occur under the following condition.

• An application with same Package Root Directory already exists within the SoftGrid Client cache.

To resolve the issue perform one of the following options:

1. Remove the conflicting application from the SoftGrid Client cache. This is only an option if the application is being permanently disabled.
2. Re-sequence the new application using a different, unique Package Root Directory.
3. Open the new application in the Sequencer, perform a Save As and specify a new Package Root Directory.

I’ve also seen this error with a corrupted OSD/Icon Cache directory. Unload all apps, clear the OSD/Icon Cache dirs and try again..! The Softgrid Apps was fine because the app loaded fine on server 1 through 7 but not number 8 so need to re-sequence.

Error code: xxxxxx-xxxxxx0C-0000003C
When you try to start an application in Microsoft SoftGrid, you receive
the following error message:
The SoftGrid Client could not launch application
This problem occurs because the Settings.cp file is corrupted.

Error code: xxxxxx-xxxxxx44-00001004
The SoftGrid Client could not launch the application you requested.
The SoftGrid Client could no use the specified OSD file because the
application package identifier has changed. Please report the following
error code to your System Administrator.
CAUSE
This problem may occur if the SoftGrid Client cache contains two
applications, and the following conditions are true of the .osd file:*
The NAME attribute of the SOFTPKG element is the same for both
applications.
* The VERSION attribute of the SOFTPKG element is the same for both
applications.
* The NAME attribute of the SUITE element is the same for both
applications.
* The GUID attribute of the CODEBASE element is different for each
application.
(Is not always the case, I’ve seen this happen at random with applications. Unloading and reloading worked for me.)

Error code: xxxxxx-xxxxxx06-00000010
An unexpected error was encountered. Please report the following error code to your System Administrator.
CAUSE
This problem may occur because the Shortcut.dat file is corrupted.
MORE INFORMATION
When you start the application again, the Shortcut.dat file is repaired. The application starts as usual.
This problem is corrected in the latest release of Microsoft SoftGrid.

"Error code: xxxxxx-xxxxxx0B-0000B034"
This issue may occur if an older version of a sequence is streamed to a SoftGrid client that has a newer version of the sequence in the cache. This typically occurs in the following scenarios:

- The new sequence is streamed. However, a decision is made to revert to the old sequence. Therefore, the new sequence is not used. In this scenario, the new sequence must be removed from the SoftGrid client cache before the old sequence is streamed.
- The environment contains multiple load-balanced SoftGrid Virtual Application Servers. One SoftGrid Virtual Application Server contains the old sequence, and another SoftGrid Virtual Application Server contains the new sequence. Examine each SoftGrid Virtual Application Server to confirm that the sequences are all the same version.

When a sequence is created, the Properties tab of the SoftGrid Sequencer will display a file version under Dir Map General. By default the file version is 1. The file version is incremented when a package upgrade is performed. To confirm the file version, open the package.

This also happens when an application is stuck somewhere in the client cache.Clicking refresh on the Softgrid client doesn’t help even when you’ve deleted the application from the cache. A sftmime /remove obj:app /complete /global  and a reboot seems to do the trick

"Error code: xxxxxx-xxxxxx12-00006002"
This problem occurs because one of the following conditions is true:
- The SoftGrid Client service is not started.
- The Shortcut.dat file is corrupted.
In our case the SoftGrid Client Service stopped without apparent reason. Starting the Client service resolved the issue