locked
Error 39-0000010B The directory name is invalid. However file can be opened via sfttray command line. RRS feed

  • Question

  • Hi Folks,

    I bump across this every so often and can't work out what the issue is. Sequencer 4.6 (not sp1) I sequence an application to c: and it launches correctly on the sequencer. I install it via the sequenced msi on a verification machine set up with AllowIndependentFileStreaming.

    On starting the application I get Error 39-0000010B The directory name is invalid. However if I launch the same sequence from the command line (sfttray /exe cmd.exe /launch "Recipient Manager VOE01017.100" ) I can navigate to the same folder and run the appropriate exe, which runs.

    excerpt from sftlog.txt on Information setting.

    [09/27/2011 17:43:46:645 SWAP ERR] {hap=B3:app=Recipient Manager VOE01017.100:tid=1294:usr=ADMIN} The client could not launch

    C:\BO61\broadcast agent publisher\Shared\Recipient Manager\Recipient Manager.exe (rc 1F701639-0000010B, last error 0).

    [09/27/2011 17:43:46:739 TRAY ERR] {tid=10A4:usr=ADMIN} The Application Virtualization Client could not launch Recipient Manager VOE01017.100.

    The directory name is invalid.

    Error code: 4605F3-1F701639-0000010B

    Partial directory on the verification machine within the bubble sfttray /exe cmd.exe /launch "Recipient Manager VOE01017.100"

    Directory of C:\BO61\broadcast agent publisher\Shared\Recipient Manager 15/10/2003 18:00 1,490,944 Recipient Manager.exe

    Directory of V:\VOE01017.100\VFS\BO61\broadcast agent publisher\Shared\Recipient Manager 15/10/2003 18:01 42,786 Recipient_Manager.EXE

     

    This is the OSD File, The error occurs even if there are no dependencies in the OSD. The other dependencies function correctly.

    <?xml version="1.0" standalone="no"?>
    <SOFTPKG GUID="A5CE6618-2C6E-46E4-9655-A1D41599031B" NAME="Recipient Manager" VERSION="VOE01017.100">
      <IMPLEMENTATION>
        <CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/VOE01017_BAP_Recipient_Manager_6.1b_1.0.0/VOE01017_BAP_Recipient_Manager_6.1b_1.0.0_3.sft" GUID="A8736BCE-0F26-4680-B528-C5228EEA677C" PARAMETERS="" FILENAME="C:\BO61\broadcast agent publisher\Shared\Recipient Manager\Recipient Manager.exe" SYSGUARDFILE="VOE01017.100\osguard.cp" SIZE="34159123" />
        <VIRTUALENV TERMINATECHILDREN="TRUE">
          <DEPENDENCIES>
            <CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/VOE00978_BusinessObjects_6.1_1.0.0/VOE00978_BusinessObjects_6.1_1.0.0_5.sft" GUID="8789CC94-7366-48C8-A713-D593D76E04F3" PARAMETERS="" FILENAME="C:\BO61\bin\busobj.exe" SYSGUARDFILE="00978100\osguard.cp" SIZE="398462559" MANDATORY="TRUE" />
            <CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/VOE02796_bomain_fdw_mkey_file_1.0.0/VOE02796_bomain_fdw_mkey_file_1.0.0.sft" GUID="D43038EB-BFCB-4440-AAE1-1A64DDD887C0" PARAMETERS="" FILENAME="%SFT_SYSTEM32_X64%\Notepad.Exe" SYSGUARDFILE="VOE02796.100\osguard.cp" SIZE="490980" MANDATORY="TRUE" />
            <CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/VOE00931_BO_FDW_Key_1.0.0/VOE00931_BO_FDW_Key_1.0.0_2.sft" GUID="CE9A5376-CED7-4BD8-BB83-D5CB359387F7" PARAMETERS="" FILENAME="%SFT_SYSTEM32_X64%\Notepad.Exe" SYSGUARDFILE="VOE00931.100\osguard.cp" SIZE="60796" MANDATORY="TRUE" />
          </DEPENDENCIES>
          <ENVLIST>
            <ENVIRONMENT VARIABLE="PATH">C:\BO61\broadcast agent publisher\Shared\bin\;bin\jre\bin\server;%PATH%;%CSIDL_PROGRAM_FILES%\Microsoft Application Virtualization Sequencer x64\;</ENVIRONMENT>
          </ENVLIST>
        </VIRTUALENV>
        <WORKINGDIR />
        <VM VALUE="Win32">
          <SUBSYSTEM VALUE="windows" />
        </VM>
      </IMPLEMENTATION>
      <DEPENDENCY>
        <CLIENTVERSION VERSION="4.6.0.0" />
      </DEPENDENCY>
      <PACKAGE NAME="VOE01017_BAP_Recipient_Manager_6.1b_1.0.0" />
      <ABSTRACT>ECS - Chris Binner 27/09/2011 - Business Objects BAP Recipient Manager 6.1b</ABSTRACT>
      <MGMT_SHORTCUTLIST>
        <SHORTCUT LOCATION="%CSIDL_PROGRAMS%\Business Objects\Broadcast Agent Publisher 6.1" FILENAME="Recipient Manager.lnk" OVERRIDDEN="FALSE" DISPLAY="Recipient Manager" ICON="%SFT_MIME_SOURCE%/VOE01017_BAP_Recipient_Manager_6.1b_1.0.0 Icons/VOE01017.100_Recipient_Manager.ico" />
      </MGMT_SHORTCUTLIST>
      <MGMT_FILEASSOCIATIONS>
        <PROGIDLIST />
        <FILEEXTENSIONLIST />
      </MGMT_FILEASSOCIATIONS>
    </SOFTPKG>
    


    Are there further troubleshooting steps that I can do?

     

    Tuesday, September 27, 2011 5:14 PM

Answers

  • Hello,

    Seeing that the process working directory is set to none (meaning process will likely have directory set to App-V Client's directory or System32), have you tried setting WORKINGDIR element explicitly to the directory executable being launched sits in?

    <WORKINGDIR>C:\BO61\broadcast agent publisher\Shared\Recipient Manager</WORKINGDIR>

     


    br,
    Kalle Saunamäki
    • Marked as answer by ChrisBinner Tuesday, September 27, 2011 10:03 PM
    Tuesday, September 27, 2011 7:27 PM
    Moderator

All replies

  • Hello,

    Seeing that the process working directory is set to none (meaning process will likely have directory set to App-V Client's directory or System32), have you tried setting WORKINGDIR element explicitly to the directory executable being launched sits in?

    <WORKINGDIR>C:\BO61\broadcast agent publisher\Shared\Recipient Manager</WORKINGDIR>

     


    br,
    Kalle Saunamäki
    • Marked as answer by ChrisBinner Tuesday, September 27, 2011 10:03 PM
    Tuesday, September 27, 2011 7:27 PM
    Moderator
  • ps, is the target process 32-bit application?

    You seem to have sequenced on a 64-bit Sequencer based on captured path in virtualized environment variable so if the application is 32-bit have you tried to sequence it on 32-bit Sequencer and see if it works any better?

     


    br,
    Kalle Saunamäki

    Tuesday, September 27, 2011 7:31 PM
    Moderator
  • Hi Kalle,

    Adding the path to the working directory as you suggested made the difference.

    <WORKINGDIR>C:\BO61\broadcast agent publisher\Shared\Recipient Manager</WORKINGDIR>
    

    The path is non standard because a prerequisite outside the bubble; oracle 8i doesn't like special characters such as brackets

    ( or ) in Program Files (x86)

    in its search path.

    That is the first time I've had do that in 9 months of sequencing. For me it is usually there and correct or empty and the sequences usually work.

    I have also now made sure that I had added the paths from the mandatory linked packages to the osd.

    <ENVIRONMENT VARIABLE="PATH">C:\BO61\broadcast agent publisher\Shared\bin\;bin\jre\bin\server;C:\BO61\bin\orb\asp\5.1\bin;C:\BO61\bin\orb\bin;C:\BO61\bin;%PATH%;%CSIDL_PROGRAM_FILES%\Microsoft Application Virtualization Sequencer x64\;</ENVIRONMENT>
    
    I don't know why the path used in the WORKINGDIR is not in the Enivronment path, but that is what happens when your are sequencing someone elses repackaged MSI blind. Could that also been a solution?

    The 64 bit sequencer is by customer preference, but it would have been a possibility. Just did not want to mix versions as this suite is a mix of 5 or 6 applications, database drivers, middle-ware and licence keys. This bit was almost the end of the suite.

    Thanks for your help, and thanks for all the bits of sequencing knowledge that you have posted on the internet that I have been reading since January :-)

    Thanks

    Chris



    • Edited by ChrisBinner Tuesday, September 27, 2011 10:05 PM edit for clarification
    Tuesday, September 27, 2011 9:59 PM
  • oops, the path has a chunk missing in the update, but it is now correct (and didn't affect the application launching) 

    <ENVIRONMENT VARIABLE="PATH">C:\BO61\broadcast agent publisher\Shared\bin\;C:\BO61\bin\jre\bin\server;C:\BO61\bin\orb\asp\5.1\bin;C:\BO61\bin\orb\bin;C:\BO61\bin;%PATH%;%CSIDL_PROGRAM_FILES%\Microsoft Application Virtualization Sequencer x64\;</ENVIRONMENT>
    
    

    Wednesday, September 28, 2011 9:06 AM
  • Chris,

    Good thing that the suggestion solved your issue.

    It's indeed very rare to see that WORKINGDIR is left empty, but it does happen sometimes. I guess it's something to do with the situation wherein Sequencer cannot figure out what the working directory should be; this information is usually found in the application shortcut file (.LNK) but it's probably not mandatory so if the original installer does not set it, Sequencer will just skip that too.

    AFAIK, in normal circumstances the Explorer would set started application's working directory to same path as executable is found from if not told otherwise, but in App-V scenario it's App-V Client's components doing the actual process creation so the behaviour differs.

    btw, you can safely remove ";%CSIDL_PROGRAM_FILES%\Microsoft Application Virtualization Sequencer x64\" from your virtualized path. That's another oddity in Sequencer sometimes that it adds its own path to it, but of course there's no path like that on the client!

     


    br,
    Kalle Saunamäki
    http://blog.gridmetric.com/
    Wednesday, September 28, 2011 9:12 AM
    Moderator
  • Hi Kalle,

    Unfortunately, when I stream the file it fails with the same error. I have checked that the working directory is there.

    The msi install with the the standalone test still works.

    <?xml version="1.0" standalone="no"?>
    <SOFTPKG GUID="A5CE6618-2C6E-46E4-9655-A1D41599031B" NAME="Recipient Manager" VERSION="VOE01017.100">
      <IMPLEMENTATION>
        <CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/VOE01017_BAP_Recipient_Manager_6.1b_1.0.0/VOE01017_BAP_Recipient_Manager_6.1b_1.0.0_8.sft" GUID="A8736BCE-0F26-4680-B528-C5228EEA677C" PARAMETERS="" FILENAME="C:\BO61\broadcast agent publisher\Shared\Recipient Manager\Recipient Manager.exe" SYSGUARDFILE="VOE01017.100\osguard.cp" SIZE="8076819" />
        <VIRTUALENV TERMINATECHILDREN="TRUE">
          <DEPENDENCIES>
            <CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/VOE00978_BusinessObjects_6.1_1.0.0/VOE00978_BusinessObjects_6.1_1.0.0_5.sft" GUID="8789CC94-7366-48C8-A713-D593D76E04F3" PARAMETERS="" FILENAME="C:\BO61\bin\busobj.exe" SYSGUARDFILE="00978100\osguard.cp" SIZE="398462559" MANDATORY="TRUE" />
            <CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/VOE02796_bomain_fdw_mkey_file_1.0.0/VOE02796_bomain_fdw_mkey_file_1.0.0_2.sft" GUID="D43038EB-BFCB-4440-AAE1-1A64DDD887C0" PARAMETERS="" FILENAME="%SFT_SYSTEM32_X64%\Notepad.Exe" SYSGUARDFILE="VOE02796.100\osguard.cp" SIZE="59588" MANDATORY="TRUE" />
            <CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/VOE00931_BO_FDW_Key_1.0.0/VOE00931_BO_FDW_Key_1.0.0_2.sft" GUID="CE9A5376-CED7-4BD8-BB83-D5CB359387F7" PARAMETERS="" FILENAME="%SFT_SYSTEM32_X64%\Notepad.Exe" SYSGUARDFILE="VOE00931.100\osguard.cp" SIZE="60796" MANDATORY="TRUE" />
          </DEPENDENCIES>
          <ENVLIST>
            <ENVIRONMENT VARIABLE="PATH">C:\BO61\broadcast agent publisher\Shared\bin\;C:\BO61\bin\jre\bin\server;C:\BO61\bin\orb\asp\5.1\bin;C:\BO61\bin\orb\bin;C:\BO61\bin;%PATH%;%CSIDL_PROGRAM_FILES%\Microsoft Application Virtualization Sequencer x64;</ENVIRONMENT>
          </ENVLIST>
        </VIRTUALENV>
        <WORKINGDIR>C:\BO61\broadcast agent publisher\Shared\Recipient Manager</WORKINGDIR>
        <VM VALUE="Win32">
          <SUBSYSTEM VALUE="windows" />
        </VM>
      </IMPLEMENTATION>
      <DEPENDENCY>
        <CLIENTVERSION VERSION="4.6.0.0" />
      </DEPENDENCY>
      <PACKAGE NAME="VOE01017_BAP_Recipient_Manager_6.1b_1.0.0" />
      <ABSTRACT>ECS - Chris Binner 29/09/2011 - Business Objects BAP Recipient Manager 6.1b</ABSTRACT>
      <MGMT_SHORTCUTLIST>
        <SHORTCUT LOCATION="%CSIDL_PROGRAMS%\Business Objects\Broadcast Agent Publisher 6.1" FILENAME="Recipient Manager.lnk" OVERRIDDEN="FALSE" DISPLAY="Recipient Manager" ICON="%SFT_MIME_SOURCE%/VOE01017_BAP_Recipient_Manager_6.1b_1.0.0 Icons/VOE01017.100_Recipient_Manager.ico" />
      </MGMT_SHORTCUTLIST>
      <MGMT_FILEASSOCIATIONS>
        <PROGIDLIST />
        <FILEEXTENSIONLIST />
      </MGMT_FILEASSOCIATIONS>
    </SOFTPKG>
    

     

    I had tidied up the path, but at some point checking it in the sequencer the sequwencer x64 section just re-appeared :-(

     

    Even on verbose mode the logs do not add anything to the error:

    The client could not launch

    C:\BO61\broadcast agent publisher\Shared\Recipient Manager\Recipient Manager.exe (rc 1F701639-0000010B, last error 0).

    [09/27/2011 17:43:46:739 TRAY ERR] {tid=10A4:usr=ADMIN} The Application Virtualization Client could not launch Recipient Manager VOE01017.100.

    The directory name is invalid.

    Error code: 4605F3-1F701639-0000010B

    (times different, but the log it two RDP sessions away and it is late :-)

    Any suggestions?

    Cheers

    Chris

    Thursday, September 29, 2011 10:24 PM
  • With streaming vs. using standalone MSI there shouldn't be any functional differences in pacakge's operation like this.

    What immediately comes to my mind is if you have run publishing refresh i.e. that the OSD files has been properly re-downloaded the client? What if you look at the cached OSD, does it contain the modifications you made to it before replacing package files on your Content directory?

     

     


    br,
    Kalle Saunamäki
    http://blog.gridmetric.com/
    Friday, September 30, 2011 6:57 AM
    Moderator