Home > App-V > App-V: The app manager could not create an application from . . . Error 44-00001004

App-V: The app manager could not create an application from . . . Error 44-00001004


What essentially has happened is that an application was launched associated with one package then another new application with a different GUID was attempted on the same machine. It can happen after an OSD file has been cached but the original package (often an Office package) was switched to a different package hence the GUID Attribute for the CODEBASE element changes.

For example, a launch of an OSD (either by direct SFTRAY launch, IFS, or publish via Citrix or TSREMOTEAPPS points to an identically named OSD file as to one that has been cached but from a different package (hence the different package GUID.)

Then you get the following error when trying to launch:

The Application Virtualization Client could not launch the application you requested.

The Application Virtualization Client could not use the specified OSD file because the application package identifier has changed. Report the following error code to your System Administrator.

Error code: xxxxxxx-xxxxxx44-00001004

And the following shows up in the SFTLOG.TXT

The app manager could not create an application from ‘<PATH>\<APPNAME.OSD>’ (rc 0C403644-00001004).

If you recently re-sequenced a package with the same names and applications and tried to load it with a client that had the previous package still cached, this can happen.

  1. Compare the GUID in the CODEBASE element in the PSD file you are trying to launch with what is currently cached.
  2.  Then on the App-V Client’s administrative console, locate the application.
  3. Right-click the application and select “properties.”
  4. Copy the local OSD File.

 Open that file in Notepad and check to see if the GUID is different 

If the Locally cached OSD file is different, verify that GUID is registered as a package in the App-V Client’s registry.

Once that has been verified, unregister that package by running the following from an Administrative command prompt

SFTMIME DELETE PACKAGE:{GUID}

Then refresh against the server and reload the application.

Categories: App-V Tags: , , , , , ,
  1. Sh1va
    February 26, 2012 at 4:49 pm

    Hi,
    I sequenced SAS 9.3. When I launch the application, I don’t get any error msg. But the application doesn’t launch. The log file states “Could not load OSD file….” “The app manager could not create an application from …” As suggested by you I check the cache files under OSD cache, but there’s none for the same application. Although the SAS 9.3 was sequenced previously & launched why can’t I see any cached OSDs there for this application?

    Thanks,
    Sh1va.

  1. August 23, 2013 at 7:18 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: