Some Common SoftGrid Errors
One of the questions I always seem to get from people new to the SoftGrid product is “Hey J.C., I’m new to this whole SoftGrid thing, so what are some of the errors I might run into once I roll this out?” Well, that’s a great question, and an easy one to answer too because I can simply take a peek under the covers of our Knowledge Base and see what errors get searched on the most. Not only can this kind of information help you out of a jam, but if you’re aware of these ahead of time there’s a good chance you can avoid them entirely. So, without any further ado, here are the top five:
SoftGrid Client "Error code: xxxxxx-xxxxxx0A- 20000194"
When streaming an application, it may fail with the following error code:
The SoftGrid Client could not launch {application_name}.
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-20000194
The SoftGrid Client log file, sftlog.txt, may also report the following:
The SoftGrid client could not connect to stream URL '{protocol}://{server_name}:{port}/{path}/{filename}.sft' (FS status: xxxxxx0A-20000194).
The client was unable to connect to a SoftGrid server (rc xxxxxx0A-20000194)
The SoftGrid Virtual Application Server log file, sft-server.log, may report the following:
44808 "Unable to locate {provider_policy}."
44811 "Unable to open {path}\{filename}.sft."
Luckily we have a great Knowledge Base article that will tell you exactly how to resolve this.
SoftGrid Client "Error code: xxxxxx-xxxxxx2A-00002AFC"
When streaming an application, it may fail with the following error code:
The SoftGrid Client could not launch {application_name} .
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-20000194
The SoftGrid Client log file, sftlog.txt, may report the following:
The SoftGrid client could not connect to stream URL '{protocol}://{server_name}:{port}/{path}/{filename}.sft' (FS status: xxxxxx0A-20000194).
The client was unable to connect to a SoftGrid server (rc xxxxxx0A-20000194)
The SoftGrid Virtual Application Server log file, sft-server.log, may report the following:
44808 "Unable to locate {provider_policy}."
44811 "Unable to open {path}\{filename}.sft."
Here’s a Knowledge Base article that will help resolve that one.
SoftGrid Management Console "Error code: 0000C800"
When connecting to the SoftGrid Management Web Service from the SoftGrid Management Console, it may fail with the following error code:
Unexpected error occurred.
Please report the following error code to your system administrator.
Error code: 0000C800
And here’s your answer, yet again found in a KB article .
SoftGrid Client “Error Code:xxxxxx-xxxxxx2C-800736B1
When trying to launch a sequenced application you may receive the following error on the client:
The SoftGrid Client could not launch <xxxxx>.
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
Error code: xxxxxx-xxxxxx2C-800736B1
You may also see some of the following events logged in the system log:
Source: SideBySide
Event ID: 59
Description: Generate Activation Context failed for <path to exe>. Reference error message: The operation completed successfully.
Source: SideBySide
Event ID: 59
Description: Resolve Partial Assembly failed for Microsoft.VC80.MFC. Reference error message: The referenced assembly is not installed on your system.
Source: SideBySide
Event ID: 59
Description: Dependent Assembly Microsoft.VC80.MFC could not be found and Last Error was The referenced assembly is not installed on your system.
Resolution:
This is usually caused because the Visual C++ 2005 runtime or some other similar component is required by the application yet is not installed locally on the client. The logs in the system event log should give you a clue as to what is missing. If you’re trying to sequence an application like this with the current shipping version of SoftGrid, once you’re able to identify the component that is giving you problems simply install it locally on the SoftGrid client computer and the sequenced application should now work. For your reference, the Microsoft Visual C++ 2005 Redistributable Package can be found here.
SoftGrid Client "Error code: xxxxxx-xxxxxx0A-0000E019
When streaming an application, it may fail with the following error code:
The SoftGrid Client could not launch {application_name}.
An unexpected error occurred. Please report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx 0A-0000E019
The SoftGrid Client log file, sftlog.txt, may also report the following:
The SoftGrid client could not connect to stream URL ' {protocol} :// {server} : {port} / {path} / {filename} .sft' (FS status: xxxxxx 0A-0000E019).
The client was unable to connect to a SoftGrid server (rc xxxxxx 0A-0000E019)
Here’s a Knowledge Base article that will help resolve this one.
So these are the top five error codes some of our users run into. The chances of you seeing any of these are slim but just in case you do, now you'll have a head start in resolving them. That’s all for today but if you have any feedback or suggestions for future topics please let us know.