none
App-V 4.6 Application launch error 4605F3-1600200A-000001D1

    Question

  • Hi,

    We are using a stand alone configured client with MSI deployment of sequenced applications, these are cached locally before being installed by the SCCM client.

    The applications work for a while after installation but some later report an Application Virtualization Error with the follow text:

    "The Application Virtualization Client could not lauch <Application name>.

    The Application Virtualization Client is operating in disconnected mode and cannot perform the operation requested. Ensure that you can connect to the Application Virtualization Server, and then retry the operation. If the problem persists, reprt the following error code to your system Administrator.

    Error code: 4605F3-1600200A-000001D1"

    Repairing the application or restarting the services or the PC have no effect, only uninstall and re-installing the application resolves the issue. But the issue may come back.

    Below is a extract from the sftlog:

    09/09/2010 09:58:40:120 SRVC INF] {tid=F34}
    ---- The Application Virtualization Client Service version 4.6.0.1523 has started ----


    [09/09/2010 09:59:05:764 TRAY ERR] {tid=F30:usr=<USERNAME>}
    The Application Virtualization Client could not launch Client 2008 1.0.

    The Application Virtualization Client is operating in disconnected mode and cannot perform the operation requested. Ensure that you can connect to the Application Virtualization Server, and then retry the operation. If the problem persists, report the following error code to your System Administrator.

    Error code: 4605F3-1600200A-000001D1

    [09/09/2010 10:01:57:710 INTF WRN] {tid=F30}
    The data directory for this user is already in use by another user with SID
    <User SID>. All users must have unique data directories. The UserDataDirectory
    setting in the registry may be configured incorrectly.


    [09/09/2010 10:01:58:101 AMGR INF] {tid=19D0}
    Delete application (hApp was 1)


    [09/09/2010 10:01:58:117 AMGR INF] {tid=19D0}
    Delete application (hApp was 2)

    Any idea what may be causeing this intermittant problem?

     

    Keywan

     

    Thursday, November 11, 2010 1:47 PM

Answers

  • Hi mcsiki,

    I had seen this article but this was not the cause of the issue. Our raised case with Microsoft determined the issue was due to our antivirus product blocking access to the usrvol_sftfs_v1.tmp when writing back at the end of session.

    Regards,

     

    Keywan

    • Marked as answer by Keywan Monday, February 07, 2011 11:15 AM
    Monday, February 07, 2011 11:15 AM

All replies

  • Hello,

    How did you install the client? Seems that something is misconfigured inorder to run as a standalone.

    See this whitepaper;

    http://tmurgent.com/WhitePapers%5CMicrosoft_AppV_Stand-Alone.pdf

    /Znack

    Thursday, November 11, 2010 2:17 PM
  • See Below for Client MSI customisations made:

    Agree to License:

    MSI Property:

    AgreeToLicense="Yes"

    Registry:

    N/A

     

    Install Type

    MSI Property:

    _IsSetupTypeMin="Custom"

    Registry:

    N/A

     

    Cache Type (FreeSpace or MaxCache):

    MSI Property:

    _CacheType="FreeSpace"

    Registry:

    N/A

     

    Set Disk Threshold Size (MB):

    MSI Property:

    FS_MINFREEMB="#6000"

    Registry:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\AppFS]

    "MinFreeSpaceMB"=dword:00001770

     

    Set App-V Mount point (Drive Letter):

    MSI Property:

    FS_SWIFSDRIVE="V:"

    Registry:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\AppFS]

    "DriveLetter"="V:"

     

    Standalone mode Configuration:

     

    Application Authorisation:

    Ensures that application can be used without authentication to the App-V Server.

    MSI Property:

    CONF_REQUIREAUTHORIZATIONIFCACHED=”#0”

    Registry:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration]

    "RequireAuthorizationIfCached"=dword:00000000

     

    Online:

    Allows App-V client to be used in offline mode.

    MSI Property:

    NET_ONLINE="#0"

    Registry:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Network]

    "Online"=dword:00000000

     

    Allow Disconnect Operation:

    Allows App-V client to be used in offline mode (default)

    MSI Property:

    NET_ALLOWDISCONNECTEDOPERATION=#1

    Registry:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Network]

    "AllowDisconnectedOperation"=dword:00000001

     

    Offline Time Out:

    Indicates how many minutes an application may be used in a disconnected operation.

     

    Time Out:

    Indicates the time the App-V client can be used offline before it tries to connect to the App-V server.

    MSI Property:

    NET_DOTIMEOUTMINUTES

    The following custom property has been created to configure this as the value of NET_DOTTIMEOUT is reset by the installer to 90 days – Even if it is pre-configured in the MSI to a different value.

    NET_DOTIMEOUTMINUTES2="#16777215"

    Registry:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Network]

    "DOTimeoutMinutes"=dword:00ffffff

     

    Important: Don´t set the value to the value that is indicated in the Microsoft admin guide which is 8xf (FFFFFFFF), but to 6xf (FFFFFF). A value of 8xf will be reset by the App-V client after a reboot or restart of the service to the original setting (HEX: 1fa40) which is 90 days. The value ffffff ensures 31.9 years of offline use for the application

     

    Toggle Offline mode:

    Prevents the user from changing the App-V client back to online mode.

    MSI Property:

    PERM_TOGGLEOFFLINEMODE_WD

    Registry:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Permissions]

    "ToggleOfflineMode"=dword:00000000

    Thursday, November 11, 2010 2:32 PM
  • Hello,

    I would read teh whitepaper and verify the properties you have used... they don't seem to correspond to ones that actually are used (by the installer)...
    Would be good that verify afterwards what the actually registry keys are set to.

    /Znack

    Thursday, November 11, 2010 2:36 PM
  • Hi,

    The three main differences i can see are:

    AUTOLOADONLAUNCH & AUTOLOADONLOGIN & ALLOWINDEPENDENTFILESTREAMING

    I'll doing some testing with these settings

    We are using the free space model for the cache size so the SWICACHESIZE property is not required and SWIGLOBALDATA & SWIUSERDATA are optional.

    That leave SWSKIPDATASETTNGS, is this required if i am using the free space cache model?R

    Keywan

    Thursday, November 11, 2010 3:33 PM
  • Are you attempting to "install" the App-V Application from a Network Share? If so, copy the Application's MSI and the SFT locally to the client machine and try again

    http://www.kirx.org/app-v/read/error-codes/0A-000001D1-en.html

     

     


    Falko
    Tuesday, November 16, 2010 9:35 PM
    Moderator
  • Nope the MSI's are cached locally in the SCCM client cache before installation. I have raised a case with Microsoft support regarding this issue.
    Wednesday, November 17, 2010 9:47 AM
  • Hi Keywan,

    Check this: http://support.microsoft.com/?kbid=979598

    I think this will solve your problem.

    Regards,


    mcsiki
    Monday, February 07, 2011 10:57 AM
  • Hi mcsiki,

    I had seen this article but this was not the cause of the issue. Our raised case with Microsoft determined the issue was due to our antivirus product blocking access to the usrvol_sftfs_v1.tmp when writing back at the end of session.

    Regards,

     

    Keywan

    • Marked as answer by Keywan Monday, February 07, 2011 11:15 AM
    Monday, February 07, 2011 11:15 AM