Revision as of 09:32, 21 July 2020

Knowledge Base

Error message when you try to start an application in Microsoft SoftGrid Client or you try to add a new application in the SoftGrid Client MMC snap-in: "Error code: xxxxxx-xxxxxx44-00000007"

Article ID: 930634

Article Last Modified on 3/13/2007

APPLIES TO

Microsoft SoftGrid for Terminal Services
Microsoft SoftGrid for Windows Desktops

SYMPTOMS

When you try to start an application in Microsoft SoftGrid Client or you try to add a new application in the SoftGrid Client Management Microsoft Management Console (MMC) snap-in, you receive the following error message:

The SoftGrid Client could not launch Application.
The application file will not work on the current operating system. Please report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx44-00000007

The SoftGrid Client could not create a new application from 'Path\FileName.osd'.
The application file will not work on the current operating system. Please report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx44-00000007

When this problem occurs, an entry that resembles the following is logged in the SoftGrid Client log file (Sftlog.txt):

The SoftGrid Client could not parse the OSD file 'Path/FileName.osd' Reason: No valid implementation for this machine (rc xxxxxx04-00000007)

CAUSE

This problem occurs because the .osd file is not configured to run on the operating system.

To enable an .osd file to run on a specific operating system, you must specify that operating system within the .osd file. To do this, set the VALUE attribute of the <OS> element. For example, the VALUE attribute must equal "WinXP" if you want to run the .osd file from Microsoft Windows XP Professional. The following table lists the operating systems and corresponding values of the VALUE attribute.

Operating system	VALUE attribute
Microsoft Windows NT	WinNT
Microsoft Windows 2000 Server	Win2K
Windows XP Professional	WinXP
Windows 2000 Server	Win2KSvr
Windows 2000 Terminal Server	Win2KTS
Microsoft Windows Server 2003	Win2003Svr
Windows Server 2003 Terminal Server	Win2003TS
Windows Vista	WinVista

RESOLUTION

To resolve this problem, follow these steps:

Edit the .osd file by using a text editor. For example, edit the file by using Notepad.
Locate the <OS> element or elements within the <IMPLEMENTATION> element.
Verify the VALUE attribute for each <OS> element.
On a new line, type a new operating system value, depending on the operating system that you want to enable. For example, type <OS VALUE="Value"/>.
After you make changes, save the .osd file.

For example, the .osd file may contain the following lines of code.

<SOFTPKG>
  <IMPLEMENTATION>
    <OS VALUE="WinNT"/>
    <OS VALUE="Win2K"/>
    <OS VALUE="WinXP"/>
    <OS VALUE="Win2KSvr"/>
    <OS VALUE="Win2KTS"/>
    <OS VALUE="Win2003Svr"/>
    <OS VALUE="Win2003TS"/>
    <OS VALUE="WinVista"/>
  </IMPLEMENTATION>
</SOFTPKG>

Keywords: kbexpertiseinter kbtshoot KB930634

@@ Line 66: / Line 66: @@
 This problem occurs because the .osd file is not configured to run on the operating system.<br />
 <br />
-To enable an .osd file to run on a specific operating system, you must specify that operating system within the .osd file. To do this, set the '''VALUE''' attribute of the '''&lt;OS&gt;''' element. For example, the '''VALUE''' attribute must equal &quot;WinXP&quot; if you want to run the .osd file from Microsoft Windows XP Professional. The following table lists the operating systems and corresponding values of the '''VALUE''' attribute.
+To enable an .osd file to run on a specific operating system, you must specify that operating system within the .osd file. To do this, set the '''VALUE''' attribute of the '''<OS&gt;''' element. For example, the '''VALUE''' attribute must equal &quot;WinXP&quot; if you want to run the .osd file from Microsoft Windows XP Professional. The following table lists the operating systems and corresponding values of the '''VALUE''' attribute.
 {|
 ! Operating system
@@ Line 104: / Line 104: @@
 To resolve this problem, follow these steps:
 # Edit the .osd file by using a text editor. For example, edit the file by using Notepad.
-# Locate the '''&lt;OS&gt;''' element or elements within the '''&lt;IMPLEMENTATION&gt;''' element.
+# Locate the '''<OS&gt;''' element or elements within the '''<IMPLEMENTATION&gt;''' element.
-# Verify the '''VALUE''' attribute for each '''&lt;OS&gt;''' element.
+# Verify the '''VALUE''' attribute for each '''<OS&gt;''' element.
-# On a new line, type a new operating system value, depending on the operating system that you want to enable. For example, type<span class="kbd userinput"> &lt;OS VALUE=&quot;<code>Value</code>&quot;/&gt;</span>.
+# On a new line, type a new operating system value, depending on the operating system that you want to enable. For example, type<span class="kbd userinput"> <OS VALUE=&quot;<code>Value</code>&quot;/&gt;</span>.
 # After you make changes, save the .osd file.
 For example, the .osd file may contain the following lines of code.
-<pre class="codesample">&lt;SOFTPKG&gt;
+<pre class="codesample"><SOFTPKG&gt;
-   &lt;IMPLEMENTATION&gt;
+   <IMPLEMENTATION&gt;
-     &lt;OS VALUE=&quot;WinNT&quot;/&gt;
+     <OS VALUE=&quot;WinNT&quot;/&gt;
-     &lt;OS VALUE=&quot;Win2K&quot;/&gt;
+     <OS VALUE=&quot;Win2K&quot;/&gt;
-     &lt;OS VALUE=&quot;WinXP&quot;/&gt;
+     <OS VALUE=&quot;WinXP&quot;/&gt;
-     &lt;OS VALUE=&quot;Win2KSvr&quot;/&gt;
+     <OS VALUE=&quot;Win2KSvr&quot;/&gt;
-     &lt;OS VALUE=&quot;Win2KTS&quot;/&gt;
+     <OS VALUE=&quot;Win2KTS&quot;/&gt;
-     &lt;OS VALUE=&quot;Win2003Svr&quot;/&gt;
+     <OS VALUE=&quot;Win2003Svr&quot;/&gt;
-     &lt;OS VALUE=&quot;Win2003TS&quot;/&gt;
+     <OS VALUE=&quot;Win2003TS&quot;/&gt;
-     &lt;OS VALUE=&quot;WinVista&quot;/&gt;
+     <OS VALUE=&quot;WinVista&quot;/&gt;
-   &lt;/IMPLEMENTATION&gt;
+   </IMPLEMENTATION&gt;
-&lt;/SOFTPKG&gt;</pre>
+</SOFTPKG&gt;</pre>
 </div>

Microsoft KB Archive/930634: Difference between revisions

Revision as of 09:32, 21 July 2020

Contents

Error message when you try to start an application in Microsoft SoftGrid Client or you try to add a new application in the SoftGrid Client MMC snap-in: "Error code: xxxxxx-xxxxxx44-00000007"

SYMPTOMS

CAUSE

RESOLUTION