Sign in
Microsoft.com
 
Application Virtualization TechCenter
 
 
 
Application Virtualization TechCenter > Microsoft Application Virtualization (App-V) Forums > App-V Clients > GUID in manifest does not match the existing package GUID
Ask a questionAsk a question
Search Forums:
 

Proposed AnswerGUID in manifest does not match the existing package GUID

  • Sunday, October 11, 2009 6:16 PMMetan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Has Code
    Sign In to Vote
    0
    Sign In to Vote
    Hi,
    With app-v 4.5 and SCCM SP1 R2, I tried to distribute virtual winrar package on a client.
    I created a virtual package with sequencer, copied it on SCCM server, created a virtual package and an advertisement. (download content from DP option selected).
    The advertisement arrives on client, download sources, and fails :

    ADD PACKAGE command line = ["C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM" ADD PACKAGE:"WinRar 3.61" /MANIFEST "C:\\WINDOWS\\system32\\CCM\\Cache\\SMZ00011.1.S-1-5-21-3709416827-403088569-1483651483-1000\\Winrar_manifest.xml" /OverrideUrl "FILE://C:\\WINDOWS\\system32\\CCM\\Cache\\SMZ00011.1.S-1-5-21-3709416827-403088569-1483651483-1000\\SMZ00011.sft"] VAppRegistration 11/10/2009 19:23:32 1864 (0x0748)
Executing command line: "C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM" ADD PACKAGE:"WinRar 3.61" /MANIFEST "C:\\WINDOWS\\system32\\CCM\\Cache\\SMZ00011.1.S-1-5-21-3709416827-403088569-1483651483-1000\\Winrar_manifest.xml" /OverrideUrl "FILE://C:\\WINDOWS\\system32\\CCM\\Cache\\SMZ00011.1.S-1-5-21-3709416827-403088569-1483651483-1000\\SMZ00011.sft" VAppRegistration 11/10/2009 19:23:32 1864 (0x0748)
The command completed with exit code 6153. VAppRegistration 11/10/2009 19:23:35 1864 (0x0748)
CVAppRegistration::RunAddPkgCommand failed. (0x80009101) VAppRegistration 11/10/2009 19:23:35 1864 (0x0748)
Succeeded loading resource DLL 'C:\WINDOWS\system32\CCM\core\swd_res.dll' VAppRegistration 11/10/2009 19:23:35 1864 (0x0748)
Raising event:
[SMS_CodePage(850), SMS_LocaleID(1036)]
instance of CLIMSG_VIRTUALAPP_ERROR_PACKAGEADD_FAILURE
{
 AdvertisementId = "SMZ2000A";
 ClientID = "GUID:6E398C07-43F8-4E29-B881-D48BDB3D531D";
 DateTime = "20091011172335.136000+000";
 ErrorCode = "0x00001809";
 ErrorMessage = "The command failed with error 0x00001809.";
 MachineName = "CI428929";
 PackageID = "SMZ00011";
 ProcessID = 2640;
 SiteCode = "SMZ";
 ThreadID = 1864;
 VirtualAppPackageGUID = "{3EEB2D53-5DA3-45B1-B15E-65BF3E468426}";
 VirtualAppPackageName = "WinRar 3.61";
};
 VAppRegistration 11/10/2009 19:23:35 1864 (0x0748)
Raised ADD PACKAGE Registration Failure event for Ad: SMZ2000A, PackageID: SMZ00011, Name: WinRar 3.61, PackageGUID: {3EEB2D53-5DA3-45B1-B15E-65BF3E468426} VAppRegistration 11/10/2009 19:23:35 1864 (0x0748)
CVAppRegistration::ExecuteAdd failed for the virtual application package. (0x80009101) VAppRegistration 11/10/2009 19:23:35 1864 (0x0748)
CVAppPackageInfo::WriteToRegistry() succeeded. VAppRegistration 11/10/2009 19:23:35 1864 (0x0748)

    If I try to launch the command manually :

    D:\Documents and Settings\admin> "C:\Program Files\Microsoft Application Virtual
ization Client\SFTMIME.COM" ADD PACKAGE:"WinRar 3.61" /MANIFEST "C:\\WINDOWS\\sy
stem32\\CCM\\Cache\\SMZ00011.1.S-1-5-21-3709416827-403088569-1483651483-1000\\Wi
nrar_manifest.xml" /OverrideUrl "FILE://C:\\WINDOWS\\system32\\CCM\\Cache\\SMZ00
011.1.S-1-5-21-3709416827-403088569-1483651483-1000\\SMZ00011.sft"
The Application Virtualization Client could not complete
the operation.
The operation failed to complete because the GUID in the
specified manifest file does not match the existing
package GUID.
Error code: 450519-18304D04-00001809
    I look in manifest file and package version GUID in sequencer, it is the same...

    Do you see where it comes from ? SCCM seems to distribute package correctly, but fails arrived on appv client. If someone have an idea, thanks in advance.
     

All Replies

  • Sunday, October 11, 2009 6:50 PMznack Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello, Sounds really odd I would say you perhaps got a mismatch between .sprj / .sft and the .xml, so try to resave and create a new package... /Znack
     
  • Sunday, October 11, 2009 6:51 PMMetan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi znack,

    Yes I already retried to create the virtual package, created a new package in SCCM, updated etc...no changes :(
     
  • Sunday, October 11, 2009 7:02 PMznack Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello,

    do you have any successfull packages?

    Perhaps there is a conflict with a previous package? Try using a new package name / 8.3-name / whatever...

    /Znack
    • Proposed As Answer byznack Tuesday, October 27, 2009 6:04 AM
    •  
     
  • Thursday, November 05, 2009 2:10 PMMullahvik Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi Metan, if still struggle with this, I have a tip for you. I ran into the same situation but for me it was an old package with the same name but different GUID that caused the trouble. I found that the SFTMIME command showed me information that was not available through the Application Virtuaization Client console.
    I ran SFTMIME QUERY OBJ:PACKAGE and looked for the package name in the output. I found it together with an old GUID. To get rid of this old information I was forced to install this old version again with the old GUID and remove it completely with SFTMIME DELETE APP:"App name" afterwards.

    Hope this helps

    Knut