none
No valid implementation for this machine (rc 07708A04-00000007) - <SUBSYSTEM VALUE="console"/> - Windows 7

    Question

  • Hi all,

    I have sequenced a failry simple console app called EnzPack adn I get the following errors in my client log file....

    [03/19/2010 10:25:23:204 OSDF INF] {tid=C34:usr=appvuser}
    The Application Virtualization Client could not parse the OSD file 'C:\ProgramData\Microsoft\Application Virtualization Client\Temp\75d0acd8-f07a-4a0a-be31-93abfd37fe16.osd'. Reason: No valid implementation for this machine (rc 07708A04-00000007)
    
    
    [03/19/2010 10:25:23:224 AMGR INF] {tid=C34:usr=appvuser}
    The app manager could not create an application from '\\AppVServer\content\EnzPack 1.3\Enzpack.osd' (rc 07708A44-00000007).

     

     

    The OSD file looks like this...

    <?xml version="1.0" standalone="no"?>
    <SOFTPKG GUID="0001ABE3-2BC2-40D7-96EC-3DDA870D94F9" NAME="Enzpack" VERSION="1.0">
    	<IMPLEMENTATION>
    		<CODEBASE HREF="RTSP://AppVServer.our.domain:554/EnzPack 1.3/EnzPack 1.3_3.sft" GUID="A356D513-AEBA-4EC9-B01B-D92DD796138A" PARAMETERS="" FILENAME="EnzPack1-3.1\Enzsvr\ENZPWIN.EXE" SYSGUARDFILE="EnzPack1-3.1\osguard.cp" SIZE="1703282"/>
    		<WORKINGDIR/>
    		<VIRTUALENV TERMINATECHILDREN="FALSE">
    			<ENVLIST/>
    		</VIRTUALENV>
    		<VM VALUE="Win16">
    			<SUBSYSTEM VALUE="console"/>
    		</VM>
    		<OS VALUE="Win7"/>
    		<OS VALUE="Win764"/>
    		<OS VALUE="WinVista"/>
    		<OS VALUE="WinXP"/>
    	</IMPLEMENTATION>
    	<DEPENDENCY>
    		<CLIENTVERSION VERSION="4.6.0.0"/>
    	</DEPENDENCY>
    	<PACKAGE NAME="EnzPack 1.3"/>
    	<ABSTRACT/>
    	<MGMT_SHORTCUTLIST>
    		<SHORTCUT LOCATION="%CSIDL_PROGRAMS%" FILENAME="Enzpack.lnk" OVERRIDDEN="FALSE" DISPLAY="Enzpack" ICON="%SFT_MIME_SOURCE%/EnzPack 1.3 Icons/Enzpack.ico"/>
    	</MGMT_SHORTCUTLIST>
    	<MGMT_FILEASSOCIATIONS>
    		<PROGIDLIST/>
    		<FILEEXTENSIONLIST/>
    	</MGMT_FILEASSOCIATIONS>
    </SOFTPKG>

     

    What I know is correct for sure....

     

    -The path to the SFT in the OSD is correct

    -The path to the OSD in the Application details in the server console is correct

    -The client can see the content share and read the files

    -The client is running other virtulised apps from the sever without issue

    -The client OS is Win 7 x64

    -I have not yet tested this on another OS

     

    What I'm wondering might be the problem is Win 16 + Console is not compatible on Windows 7 x64.

    Any ideas?

     

    Cheers,

    Matt

    Friday, March 19, 2010 11:05 AM

Answers

All replies

  • Hello,

    Try removing the OS values at all and see if that helps.

    See OSD-illustrated for tips;

    http://www.tmurgent.com/OSD_Illustrated.aspx

     

    /znack

    Friday, March 19, 2010 11:10 AM
  • Thanks znack,

     

    Now i get...

     

    [03/19/2010 11:22:56:542 SWAP WRN] {tid=C30:usr=appvuser}
    Could not load OSD file \\ITSCDSEAVSTest\content\EnzPack 1.3\Enzpack.osd


    [03/19/2010 11:22:56:573 AMGR INF] {tid=C30:usr=appvuser}
    The app manager could not create an application from '\\ITSCDSEAVSTest\content\EnzPack 1.3\Enzpack.osd' (rc 0C405A44-00001007)

     

     

    I thought 44-00001007 tended to related to incorrect parameters in the OSD relating to the SFT path. I'm sure the SFT path is correct.

     

    Cheers,

    Matt

    Friday, March 19, 2010 11:34 AM
  • Hello,

    See this article;

    http://blogs.technet.com/appv/archive/2008/10/29/error-xxxxxx44-00001007-in-the-sftlog-txt-file.aspx

    I assume that you left some type of orphaned OS tag...

    /Znack

    Friday, March 19, 2010 11:36 AM
  • Thanks again znack,

    Just to be clear, here is the new OSD...

     

     

    <?xml version="1.0" standalone="no"?>
    <SOFTPKG GUID="0001ABE3-2BC2-40D7-96EC-3DDA870D94F9" NAME="Enzpack" VERSION="1.0">
    	<IMPLEMENTATION>
    		<CODEBASE HREF="RTSP://AppVServer.our.domain:554/EnzPack 1.3/EnzPack 1.3_3.sft" GUID="A356D513-AEBA-4EC9-B01B-D92DD796138A" PARAMETERS="" FILENAME="EnzPack1-3.1\Enzsvr\ENZPWIN.EXE" SYSGUARDFILE="EnzPack1-3.1\osguard.cp" SIZE="1703282"/>
    		<WORKINGDIR/>
    		<VIRTUALENV TERMINATECHILDREN="FALSE">
    			<ENVLIST/>
    		</VIRTUALENV>
    		<VM VALUE="Win16">
    			<SUBSYSTEM VALUE="console"/>
    		</VM>
    	</IMPLEMENTATION>
    	<DEPENDENCY>
    		<CLIENTVERSION VERSION="4.6.0.0"/>
    	</DEPENDENCY>
    	<PACKAGE NAME="EnzPack 1.3"/>
    	<ABSTRACT/>
    	<MGMT_SHORTCUTLIST>
    		<SHORTCUT LOCATION="%CSIDL_PROGRAMS%" FILENAME="Enzpack.lnk" OVERRIDDEN="FALSE" DISPLAY="Enzpack" ICON="%SFT_MIME_SOURCE%/EnzPack 1.3 Icons/Enzpack.ico"/>
    	</MGMT_SHORTCUTLIST>
    	<MGMT_FILEASSOCIATIONS>
    		<PROGIDLIST/>
    		<FILEEXTENSIONLIST/>
    	</MGMT_FILEASSOCIATIONS>
    </SOFTPKG>

     

     

    I don't think there are any orphand OS tags, but I have been afflicted with temporary blindness in the past :)

     

    Cheers,

    Matt

    Friday, March 19, 2010 11:49 AM
  • Hello,

     

    Well - only one option left - switch the VM VALUE to Win32....

    /Znack

    Friday, March 19, 2010 12:01 PM
  • Hi znack,

     

    That's done the trick, app will now appear on the desktop.

    I am now getting another error (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. Report the following error code to your System Administrator ... 0A-20000194), but I'll check futher and open a new thread if I need it looked into.

     

    Cheers,

    Matt

    Friday, March 19, 2010 12:20 PM
  • Hi all,

     

    Just some further info to add.....

     

    There is a reason why changing win16 to win32 worked in this case. 64 bit OS's don't support 16 bit applications or 32 bit apps that run 16-bit processes or 16-bit components (64-bit versions of Windows do not support 16-bit components, 16-bit processes, or 16-bit applications ). Therefore the client was correct saying that there was no valid implementation for this machine when the subsystem was set to win16 as it knows 16 bits apps won't run on 64 bit OS's. Feeling a little dumb that I didn't realise this before, but now I shouldn't forget at least :)

     

    Cheers,

    Matt

    Monday, March 22, 2010 11:58 AM