Installer Error 2920
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up MSI Error 2920: Source directory not specified for file [2] when patching via WiX/MSP up vote 1 down vote favorite Currently we have a scenario where there is a CD release (A), a middle patch (B) and a patch about to go out (C). Installing (A) and patching directly to (C) works fine, but when the user patches up to (B) and then up to (C), they get error 2920 during the "Copying new files" action (first file in the sequence). What's interesting is this issue doesn't occur on Windows 7, but occurs on Win2K3 and XP, which suggests to me that the different versions of Windows Installer are handling this scenario differently. The current patch implementation creates admin installs, Prepares WiX source files for the MSP, creates the PCP file, then creates/signs the MSP file. I've looked all over there hasn't been a determined cause/solution. Thanks for your time. wix windows-installer share|improve this question asked Jan 24 '12 at 15:24 jmcdade 8019 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote I have never created a patch with using Wix, but I did with other authoring tools, and from what I know Windows Installer requires for a set of basic rules that must be followed in order for the path to be correctly created. One of them says this: "Do not change the order of files in a cabinet.". Have you checked that in your packages? More details about the rules required for a patch can be found here: http://msdn.microsoft.com/en-us/library/aa367850.aspx share|improve this answer answered Jan 24 '12 at 15:53 Bogdan Mitrache 6,861825 add a comment| up vote 0 down vote After getting off the phone with Microsoft tech, it turns out that the issue happens regardless if you go from the baseline or middle patch. The issue itself manifested itself in the form of a Windows Installer version incompatibility. Basically back when we released the CD release, we used VS2008. We migrated to VS2010 since then and the latest patch was made with files done in VS2010. VS2010 (from what the tech told me) has a dependency on Windows Installer
ForumsCategoryBoardDocumentsUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Did you mean: Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page All Forum Topics Previous Topic Next Topic Installer Error 2920 Solved! Go to Solution Installer Error 2920 baker_matt Member 07-12-2010 07:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight http://stackoverflow.com/questions/8989347/msi-error-2920-source-directory-not-specified-for-file-2-when-patching-via-wi Print Email to a Friend Report to a Moderator I created an installer through Visual Studios setup and deployment tool. I included CW3dGraph_OCX.msm (8.0.0), However when I run the installer I recieve the following error message. "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2920." The Event Log http://forums.ni.com/t5/LabWindows-CVI/Installer-Error-2920/td-p/1178701 indicates the following: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2920. The arguments are: cw3dgrph.ocx.95A62C25_864C_11D3_AB56_006008CA11D7" I have seen similiar posts where people are having this problem with different libraries however that is version 7.0 and different MSM's. Does anyone know how to resolve this issue? Solved! Go to Solution. 0 Kudos Message 1 of 6 (2,062 Views) Reply 0 Kudos Re: Installer Error 2920 John_M. Member 07-14-2010 05:29 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hey baker_matt, I've got a few questions that will help us all better understand what may be going on... First, what version of Measurement Studio and Visual Studio are you using? Also, what version of Windows are you developing on, and what version are you deploying to? Lastly, what language are you using? Also, in your project, for each of the references, we want to make sure that all of the corresponding merge modules are included. In the Measurement Studio Document
Problems Search error 2920 when using LZMA compression Having trouble running Advanced Installer? Got a bug to report? Post it all here. Post Reply Search Advanced search 2 posts • Page 1 of 1 Dmitry Slabko Posts: 10 Joined: Thu Oct 02, 2008 5:00 am error 2920 when using http://www.advancedinstaller.com/forums/viewtopic.php?t=9823 LZMA compression Quote Postby Dmitry Slabko » Tue Sep 22, 2009 5:14 pm Hello,When I set LZMA compression (any method) the installation fails with error 2920. This happens on any version of Advanced Installer. The http://microsoft.public.platformsdk.msi.narkive.com/OXn4UkXH/error-2920-source-dir-not-specified-while-applying-a-minor-upgrade-patch-onto-a-patched-installation problem began when my installation project became more complex - I am not sure what actually caused this, either adding a COM/TLB component, or a new feature, or something else. The problem is that installer error there are a few features, and any file from these features causes the 2920 error - I was gradually removing files from those features just to test, and they all were failing. Erasing and recreating these features did not help either. The features are set to be installed locally. I will send my project to your support email. Please let me know how the problem can be fixed. CAB installer error 2920 compression works just fine on this project, but LZMA produces almost twice smaller package which is important.Regards,Dmitry Top Cosmin Posts: 5797 Joined: Tue Jul 10, 2007 6:39 pm Contact: Contact Cosmin Website Re: error 2920 when using LZMA compression Quote Postby Cosmin » Wed Sep 23, 2009 11:48 am Hi Dmitry,We tested your project by using dummy source files, but unfortunately we are unable to reproduce this behavior on our test machines. Can you please try the package on other machines? If the behavior is the same please provide an URL from where we can download the package with the problem so we can investigate it.Regards,Cosmin Cosmin Pirvu - Advanced Installer TeamFollow us: Twitter - Facebook - YouTube Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost timeSubject AscendingDescending Post Reply 2 posts • Page 1 of 1 Return to “Common Problems” Jump to Advanced Installer Software Feature Requests Common Problems Building Installers Official Bug List Installer Analytics Who is online Users browsing this forum: Bing [Bot] and 2 guests Board index All times are UTC+01:00 Delete all board cookies The team Contact us Our productsAdvanced InstallerAWR CloudAWR DesktopLead ConverterAdvanced
a severe problem which pops up as error 2920Source directory not specified for file xyz.xyz is the first file in the cab file.We use InstallShield Developer 7.0 as IDE and the error occursin the context of a minor upgrade patch. But only in a certain context.Here are the details:We released SP04 of our current major version as a full installationas well as an upgrade (nimor upgrade patch -> msp file).We are about to release SP05 (only minor upgrade patch but not fullinstallation) and are currently building the firstversions of SP06.When we apply SP06 on an SP05 that we got via patch then we get the error.SP04 --- patch ---> SP05 --- patch ---> SP06 -> XXX error XXXWhen we use the internally available SP05 full installation and apply thepatcheverything is all right.SP05 --- patch ---> SP06 -> no errorWhen we apply the SP06 patch on a SP04 full installation again no problem.SP04 --- patch ---> SP06 -> no errorNow our assumption was that SP05 is the culprit.We are also in contact with InstallShield support but we got no solution sofar.Now I come to the nasty things we do. So maybe one of you specialists seesthe nonos we are doing and by that provoquing the error.1 - When a file is no more needed or when it should be moved to differentfolderwe use transitive components.Example: SP04 File1/Dir1 (Comp1) -> SP05 File1/Dir2 (Comp2)We give the Comp1 a condition that is allways false and we set thecondition to bereevaluated (Bit 64 in the attributes of the comp).Then we create a new component Comp2 for that same file with a differentdestinationdirectory.This is not really a clean approach but it was a solution that workedallways in the past.So I doubt this is the source of the problem.2 - We had some explicit registry entries for a file File23. InInstallShield Developeryou can also let the COM settings be extracted automatically duringcreationof the MSI file.With a new version we had different registry entries.We used our transitive component trick there also but as the twoversionsof the files would go to the same target directory we needed to have twodifferentsource dirs in the component table.We did put an extra source dir not only for the new component but alsofor theold one. InstallShield created a new entry in the Directory table andchangedthe directory table link in the component table to point to the newentry in Dirtable for the old component.My first assumption was that this would be a change that was not allowed(we cha