Select the product you need help with

Error message when you try to start a SoftGrid program: "The SoftGrid Client could not launch <program>. Error code: <xxxxxx-xxxxxx>18-0000000<n>"

Article ID: 930694 - View products that this article applies to.

SYMPTOMS

When you try to start a Microsoft SoftGrid program, the program does not start. Additionally, you receive the following error message:

The SoftGrid Client could not launch program.
A script failed to return the expected result. Please report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx18-0000000n

Back to the top | Give Feedback

CAUSE

This issue occurs when the script in the .osd file returns an unexpected exit code.

Back to the top | Give Feedback

RESOLUTION

To resolve this issue, first verify that the SUCCESSRESULT and ABORTRESULT attributes of the SCRIPT element in the .osd file are set, and verify that the SUCCESSRESULT attribute is not null. To do this, follow these steps:

Open the .osd file by using a text editor such as Notepad. A sample section of an .osd file is as follows.

<DEPENDENCY>
  <SCRIPT TIMING="PRE" EVENT="LAUNCH" PROTECT="TRUE" WAIT="TRUE"
    TIMEOUT="10" SUCCESSRESULT="n" ABORTRESULT="n">
    <SCRIPTBODY>review script and exit codes here</SCRIPTBODY>
  </SCRIPT>
</DEPENDENCY>

Review the exit codes in the SUCCESSRESULT="" and ABORTRESULT="" attributes.
Review the script and exit codes between the <SCRIPTBODY> and </SCRIPTBODY> elements.
Save and then exit the .osd file.

If the SUCCESSRESULT and ABORTRESULT attributes of the SCRIPT element in the .osd file are set, and if the SUCCESSRESULT attribute is not null, the script must return an exit code that is expected by those attributes. Otherwise, the program will not start, and it will generate an error code.

The error code will be in the xxxxxx-xxxxxx18-0000000n format. In this format, n is a placeholder for the exit code.

For example, if the exit code is 0, the error code is 18-00000000. If the exit code is 1, the error code is 18-00000001, and so on.

After you have verified these attributes, use the procedure that is described in the following article in the Microsoft Knowledge Base to resolve the issue:

930973

(http://support.microsoft.com/kb/930973/ )

How to fail or abort an application launch on script failure

Back to the top | Give Feedback