App-v Error code: 4605F3-18305104-0000180C

-
Issue:-
Attempting to upgrade a package in Microsoft Application Virtualization (App-V) fails with error 04-0000180C:

sftmime add package:"TEST" /manifest "" /overrideUrl ""
The Application Virtualization Client could not complete the operation.
The operation failed because the GUID in the package manifest matches a package name other than the one specified. Verify the package name, and then try again.
Error code: 4605F3-18305104-0000180C

Solution
Generic App-v Error code: 4605F3-18305104-0000180C
Cause
This error indicates that there is a mismatch between the package name of the original package and that of the upgraded package. This results in the App-V client incorrectly determining that there is a duplicate GUID, when the PackageName for the two packages is same and the PackageGUID is different or viceversa. To successfully upgrade a package, both of the following conditions must be true:
1. The package GUID must be the same (the Version tag and VERSIONGUID tag will change).
2. The package name must be exactly the same. This can be verified by opening the original and upgrade package's manifest XML in a text editor to compare the NAME and GUID tags.
The NAME tag is derived from the Package Name field on the General Properties tab of the package. The App-V Sequencer allows this field to be changed after sequencing a package but before saving the files. To avoid this error, do not edit this field.

Comments

  1. Unknown1 July 2015 at 06:09

    Nice post. I have bookmarked you to check your new stuff. Thanks for sharing this post. Its really useful for us.

    Application Packaging
    Sccm Deployment
    Application Compatibility Toolkit

    ReplyDelete

Post a Comment

Popular posts from this blog

App v for Java Runtime Environment

-
Application Type :- App V Issues :- JRE when present on local and virtual load the local version. Hence we need to make the virtual version to work. Resolution and key notes:- Procedure followed for the sequencing of this application 1) take clean sequencing machine (NO JRE(ANY VERSION) INSTALLED) 2) install JRE 1.6 locally on sequencing machine 3) launch "App-V Sequencer" 4) Click "Begin Monitoring" 5) during monitoring open "appwiz.cpl" and uninstall JRE 1.6 6) run the command from cmd "shutdown -r -t 0" to complete uninstallation of JRE 1.6 7) App-V sequencer captures the restart.  Just stop monitoring and start monitoring (to complete restart process) 8)  Now install the JRE 1.4 (during monitoring) 9) After completion of intallation create shorcut pointing to "iexplorer.exe" 10) Stop monitoring and save the captured sequence. Test the sequence package with www.javatester.org/version.html Packge works fine in both...
Read more

app v for mindjet mindmanager

-
Type :- App v  (contains add in and drivers, hence app v can only be done without them) Issues :- 1) installs PDF writer (driver) 2) contains add ins 3) Dictionary function error Solution and key points :- 1)MindManager  when installed with default settings with admin privileges, installs a printer (PDF-Xchange 3.0). On installing the source with custom settings, we are able to disable the feature for the PDF-Xchange. And the source works fine . The function of Export to PDF has been removed by disabling the feature of pdf writer. 2) User\%Sft_Sid%\Software\Mindjet\MindManager\8\Custom Dictionary\ 3) These keys had data for a Custom Dictionary ("custom.dic") in User's App.Data folder. Removed this data and set the number of dictionaries to "0", with "MindManager.dic" as Current. 4) contains add ins for microsoft office (excel , word, powerpoint) , hence we need to create a shortcut of the excel , word, powerpoint to load the add ins...
Read more

Structure of MSI package

-
Logical structure of packages A package describes the installation of one or more full products (Windows Installer does not handle dependencies between products) and is universally identified by a GUID (the PackageCode property). A product is made up of components, grouped into features. Products A single, installed, working program (or set of programs) is a product. A product is identified by a unique GUID (the ProductCode property) provides an authoritative identity throughout the world. The GUID, in combination with the version number (ProductVersion property) allow for release management of the software's files and registry keys. A product is not the same as a package: a package is identified by a unique GUID (stored in the Summary Information Stream) and provides identity and release management for all the contents of the .MSI file. Release management of a Product pertains only to changes in the files and registry keys that make up a software application. Release managem...
Read more