Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Do not ever create custom actions and call regsvr32.exe from MSI/WiX. In WiX 2.0, use the SelfRegCost attribute of the File element to cause MSI to perform the actions of regsvr32.exe on your behalf in a way that works with repairs, upgrades, patches, as well as installs and uninstalls. Of course, if you possibly can, avoid self-registration at all costs. Use the SelfRegCost attribute when you can't avoid it due to problems as you have described in this thread. And don't use/create custom actions when MSI already has built-in actions that will perform the activities you are attempting. -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: Wednesday, March 31, 2010 11:31 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode Thanks Palbinder. Actually we asked the vendor first, but they told us sorry, we don't support Wix... Anyways, here I have another question about the conditions: 1. What is the conditions if I'd like to run the custom action in both 'fresh install' and 'Repair'? Is there something like this? - Not Installed OR Repair=1 2. What is the conditions if I'd like to fun the custom action in 'uninstallation' only? Is this correct? - Remove=ALL 3. Also, What's the condition for 'fresh install' only? For the 2nd one, it doesn't work. Well, the custom action didn't run in 'fresh install' or 'Repair', but it didn't run in 'Uninstallation/Remove', either. What is the correct condition for that case? Thanks. From: Pally Sandher pally.sand...@iesve.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, March 31, 2010 3:38:43 AM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode RegSpy2 may be able to help. See http://www.installsite.org/pages/en/msi/tips.htm about 1/3 down the page. It'll output a .reg file which you run through tallow.exe to output WiX code. However I would ask the vendor of this adxloader.dll for support first. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dave Brotherstone [mailto:dav...@pobox.com] Sent: 31 March 2010 06:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,then we'll get Error 2836 in Repair mode On Wed, Mar 31, 2010 at 1:39 AM, little.forest little.for...@ymail.comwrote: Hi All, I totally understand 'using regsvr32 in Wix' is not recommended. But in this adxloader.dll case, we can't use tallow or heat to generate fragments from the dll. This is not the problem of tallow or heat, but the problem of the dll. However, the dll can be registered manually by using regsvr32.exe. So my question is: is there a way that we can collect the needed registry information manually? If it's possible, then we can get rid of regsvr32. You can probably see the registry entries manually by watching regsvr32 in procmon (from sysinternals). You'll need to convert the output to WiX, but at least you'll see everything that is written. Just set the filter to procname=regsvr32, and only watch the registry. Dave. -- Download IntelR Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download IntelR Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ The new Internet ExplorerR 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- Download Intel#174; Parallel Studio Eval Try the new software
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Thanks Bob, You're right. They don't support MSI. From: Bob Arnson b...@joyofsetup.com To: wix-users@lists.sourceforge.net Sent: Wed, March 31, 2010 5:22:35 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On 3/31/2010 2:31 PM, little.forest wrote: Actually we asked the vendor first, but they told us sorry, we don't support Wix... They don't have to support WiX, just MSI. -- sig://boB http://joyofsetup.com/ -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
RegSpy2 may be able to help. See http://www.installsite.org/pages/en/msi/tips.htm about 1/3 down the page. It'll output a .reg file which you run through tallow.exe to output WiX code. However I would ask the vendor of this adxloader.dll for support first. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dave Brotherstone [mailto:dav...@pobox.com] Sent: 31 March 2010 06:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,then we'll get Error 2836 in Repair mode On Wed, Mar 31, 2010 at 1:39 AM, little.forest little.for...@ymail.comwrote: Hi All, I totally understand 'using regsvr32 in Wix' is not recommended. But in this adxloader.dll case, we can't use tallow or heat to generate fragments from the dll. This is not the problem of tallow or heat, but the problem of the dll. However, the dll can be registered manually by using regsvr32.exe. So my question is: is there a way that we can collect the needed registry information manually? If it's possible, then we can get rid of regsvr32. You can probably see the registry entries manually by watching regsvr32 in procmon (from sysinternals). You'll need to convert the output to WiX, but at least you'll see everything that is written. Just set the filter to procname=regsvr32, and only watch the registry. Dave. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Thanks Dave. I'll try that. From: Dave Brotherstone dav...@pobox.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, March 30, 2010 10:42:16 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On Wed, Mar 31, 2010 at 1:39 AM, little.forest little.for...@ymail.comwrote: Hi All, I totally understand 'using regsvr32 in Wix' is not recommended. But in this adxloader.dll case, we can't use tallow or heat to generate fragments from the dll. This is not the problem of tallow or heat, but the problem of the dll. However, the dll can be registered manually by using regsvr32.exe. So my question is: is there a way that we can collect the needed registry information manually? If it's possible, then we can get rid of regsvr32. You can probably see the registry entries manually by watching regsvr32 in procmon (from sysinternals). You'll need to convert the output to WiX, but at least you'll see everything that is written. Just set the filter to procname=regsvr32, and only watch the registry. Dave. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Thanks Palbinder. Actually we asked the vendor first, but they told us sorry, we don't support Wix... Anyways, here I have another question about the conditions: 1. What is the conditions if I'd like to run the custom action in both 'fresh install' and 'Repair'? Is there something like this? - Not Installed OR Repair=1 2. What is the conditions if I'd like to fun the custom action in 'uninstallation' only? Is this correct? - Remove=ALL 3. Also, What's the condition for 'fresh install' only? For the 2nd one, it doesn't work. Well, the custom action didn't run in 'fresh install' or 'Repair', but it didn't run in 'Uninstallation/Remove', either. What is the correct condition for that case? Thanks. From: Pally Sandher pally.sand...@iesve.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, March 31, 2010 3:38:43 AM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode RegSpy2 may be able to help. See http://www.installsite.org/pages/en/msi/tips.htm about 1/3 down the page. It'll output a .reg file which you run through tallow.exe to output WiX code. However I would ask the vendor of this adxloader.dll for support first. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Dave Brotherstone [mailto:dav...@pobox.com] Sent: 31 March 2010 06:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,then we'll get Error 2836 in Repair mode On Wed, Mar 31, 2010 at 1:39 AM, little.forest little.for...@ymail.comwrote: Hi All, I totally understand 'using regsvr32 in Wix' is not recommended. But in this adxloader.dll case, we can't use tallow or heat to generate fragments from the dll. This is not the problem of tallow or heat, but the problem of the dll. However, the dll can be registered manually by using regsvr32.exe. So my question is: is there a way that we can collect the needed registry information manually? If it's possible, then we can get rid of regsvr32. You can probably see the registry entries manually by watching regsvr32 in procmon (from sysinternals). You'll need to convert the output to WiX, but at least you'll see everything that is written. Just set the filter to procname=regsvr32, and only watch the registry. Dave. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
On 3/31/2010 2:31 PM, little.forest wrote: Actually we asked the vendor first, but they told us sorry, we don't support Wix... They don't have to support WiX, just MSI. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Hi All, Allow me to recap this issue please. Basically, we have an old product(uses Wix 2.0) that is an Outlook plugin application. We use a COM component adxloader.dll from Add-in Express(http://www.add-in-express.com/) in the product. What we need to do is to install the adxloader.dll and register it as a COM. But unfortunately, adxloader isn't friendly for Wix. By using tallow or heat, we can't generate the correct fragments from it. But somebody gives us a solution: http://blogs.microsoft.co.il/blogs/yanush/archive/2008/09/22/howto-use-regsvr32-exe-with-wix.aspx It is kind of working. But there are two problems: 1. After installation, if we re-run the installer and choose Repair. Then Outlook will crash when we start it. This is because these statements: CustomAction Id=RegisterAdx Directory=INSTALLDIR ExeCommand='regsvr32.exe /s [INSTALLDIR]adxloader.dll' Return=check /CustomAction CustomAction Id=UnregisterAdx Directory=INSTALLDIR ExeCommand='regsvr32.exe /s /u [INSTALLDIR]adxloader.dll' /CustomAction InstallExecuteSequence Custom Action=RegisterAdx After=InstallFinalizeNOT Installed/Custom Custom Action=UnregisterAdx Before=InstallInitializeInstalled/Custom /InstallExecuteSequence As what you can see, during Repair, the dll will be unregistered. If the dll isn't registered, then Outlook will crash. So I changed the condition to make sure we only unregister the dll in uninstall or remove: Custom Action=UnregisterAdx Before=InstallInitializeRemove=ALL/Custom This seems working. 2. Out QA also tested this case which is failed: after installation, delete the adxloader.dll, and run the installer again and choose Repair - the result is that the adxloader.dll never comes back and throws a 'Error 2836'. I think this is related to #1. The reason is because in Repair, the installer will try to unregister the file, and couldn't find the file. By fixing #1, this problem seems gone. Right now, it seems working. I totally understand 'using regsvr32 in Wix' is not recommended. But in this adxloader.dll case, we can't use tallow or heat to generate fragments from the dll. This is not the problem of tallow or heat, but the problem of the dll. However, the dll can be registered manually by using regsvr32.exe. So my question is: is there a way that we can collect the needed registry information manually? If it's possible, then we can get rid of regsvr32. Please let me know. I appreciate it. From: little.forest little.for...@ymail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Mon, March 29, 2010 5:35:29 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode Thanks Chad. Actually I tried that, but I got some errors: Microsoft (R) Windows Installer Xml Tool version 2.0.5325.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. Fragment DirectoryRef Id=TARGETDIR Component Id=component0 DiskId=1 Guid=PUT-GUID-HERE File Id=file0 Name=ADXLOA_1.DLL LongName=adxloader.dll Source=C:\mydir\adxloader.dll /Failed to SelfReg: adxloader.dll System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. --- System.TypeInitializationException: Type constructor threw an exception. at DllRegisterServer() --- End of inner exception stack trace --- at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct sig, MethodAttrib utes methodAttributes, RuntimeTypeHandle typeOwner) at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes met hodAttributes, RuntimeTypeHandle typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters , CultureInfo culture, Boolean skipVisibilityChecks) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters , CultureInfo culture) at Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain.DynamicPInvoke(String dll, String entryPoint, Type ret urnType, Type[] parameterTypes, Object[] parameterValues) at Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain..ctor(String[] args) Registry Root=HKCU Key=Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders Name=Personal / Registry Root=HKCU Key=Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders / /Component /DirectoryRef /Fragment /Wix From: Chad Petersen chad.peter...@harlandfs.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Mon, March 29, 2010 2:40:07 PM Subject: Re: [WiX-users] Wix 2.0
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
On Wed, Mar 31, 2010 at 1:39 AM, little.forest little.for...@ymail.comwrote: Hi All, I totally understand 'using regsvr32 in Wix' is not recommended. But in this adxloader.dll case, we can't use tallow or heat to generate fragments from the dll. This is not the problem of tallow or heat, but the problem of the dll. However, the dll can be registered manually by using regsvr32.exe. So my question is: is there a way that we can collect the needed registry information manually? If it's possible, then we can get rid of regsvr32. You can probably see the registry entries manually by watching regsvr32 in procmon (from sysinternals). You'll need to convert the output to WiX, but at least you'll see everything that is written. Just set the filter to procname=regsvr32, and only watch the registry. Dave. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Thanks Bob. That dll is provided by a 3rd party company. We don't know how it's implemented. But I guess something isn't quite right with the DLL. We'll try to talk to the dll provider to understand the detail. The dll can be registered correctly by using regsvr32.exe. So after using regsvr32.exe, is there a way that we could manually collect the registry info for the dll and then use them in the installer? Thanks. From: Bob Arnson b...@joyofsetup.com To: wix-users@lists.sourceforge.net Sent: Sat, March 27, 2010 12:06:31 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On 3/26/2010 2:12 PM, little.forest wrote: 2. Those two DLL files will cause 'Error 2836' directly. But the manifest file will cause the installer showing 'The system can not find the file specified.' first then showing the 'Error 2836'. So this is slightly different from those two DLL files. As I mentioned, that's not a fatal error. There's some other error that might be helpful in diagnosing your root problem. 1. If my guess is correct, please post some links here about how to register a COM component correctly in 2.0. Meanwhile, I'll dig in this topic as well. Use Class, Interface, ProgId, Extension, Verb, TypeLib. -- sig://boB http://joyofsetup.com/ -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Look at the Tallow.exe utility. I think Tallow -s filename might be a first step to try. Chad -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: Monday, March 29, 2010 2:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,then we'll get Error 2836 in Repair mode Thanks Bob. That dll is provided by a 3rd party company. We don't know how it's implemented. But I guess something isn't quite right with the DLL. We'll try to talk to the dll provider to understand the detail. The dll can be registered correctly by using regsvr32.exe. So after using regsvr32.exe, is there a way that we could manually collect the registry info for the dll and then use them in the installer? Thanks. From: Bob Arnson b...@joyofsetup.com To: wix-users@lists.sourceforge.net Sent: Sat, March 27, 2010 12:06:31 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On 3/26/2010 2:12 PM, little.forest wrote: 2. Those two DLL files will cause 'Error 2836' directly. But the manifest file will cause the installer showing 'The system can not find the file specified.' first then showing the 'Error 2836'. So this is slightly different from those two DLL files. As I mentioned, that's not a fatal error. There's some other error that might be helpful in diagnosing your root problem. 1. If my guess is correct, please post some links here about how to register a COM component correctly in 2.0. Meanwhile, I'll dig in this topic as well. Use Class, Interface, ProgId, Extension, Verb, TypeLib. -- sig://boB http://joyofsetup.com/ -- Download Intel(r) Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Thanks Chad. Actually I tried that, but I got some errors: Microsoft (R) Windows Installer Xml Tool version 2.0.5325.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. Fragment DirectoryRef Id=TARGETDIR Component Id=component0 DiskId=1 Guid=PUT-GUID-HERE File Id=file0 Name=ADXLOA_1.DLL LongName=adxloader.dll Source=C:\mydir\adxloader.dll /Failed to SelfReg: adxloader.dll System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. --- System.TypeInitializationException: Type constructor threw an exception. at DllRegisterServer() --- End of inner exception stack trace --- at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct sig, MethodAttrib utes methodAttributes, RuntimeTypeHandle typeOwner) at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes met hodAttributes, RuntimeTypeHandle typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters , CultureInfo culture, Boolean skipVisibilityChecks) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters , CultureInfo culture) at Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain.DynamicPInvoke(String dll, String entryPoint, Type ret urnType, Type[] parameterTypes, Object[] parameterValues) at Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain..ctor(String[] args) Registry Root=HKCU Key=Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders Name=Personal / Registry Root=HKCU Key=Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders / /Component /DirectoryRef /Fragment /Wix From: Chad Petersen chad.peter...@harlandfs.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Mon, March 29, 2010 2:40:07 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode Look at the Tallow.exe utility. I think Tallow -s filename might be a first step to try. Chad -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: Monday, March 29, 2010 2:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,then we'll get Error 2836 in Repair mode Thanks Bob. That dll is provided by a 3rd party company. We don't know how it's implemented. But I guess something isn't quite right with the DLL. We'll try to talk to the dll provider to understand the detail. The dll can be registered correctly by using regsvr32.exe. So after using regsvr32.exe, is there a way that we could manually collect the registry info for the dll and then use them in the installer? Thanks. From: Bob Arnson b...@joyofsetup.com To: wix-users@lists.sourceforge.net Sent: Sat, March 27, 2010 12:06:31 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On 3/26/2010 2:12 PM, little.forest wrote: 2. Those two DLL files will cause 'Error 2836' directly. But the manifest file will cause the installer showing 'The system can not find the file specified.' first then showing the 'Error 2836'. So this is slightly different from those two DLL files. As I mentioned, that's not a fatal error. There's some other error that might be helpful in diagnosing your root problem. 1. If my guess is correct, please post some links here about how to register a COM component correctly in 2.0. Meanwhile, I'll dig in this topic as well. Use Class, Interface, ProgId, Extension, Verb, TypeLib. -- sig://boB http://joyofsetup.com/ -- Download Intel(r) Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
On 3/26/2010 2:12 PM, little.forest wrote: 2. Those two DLL files will cause 'Error 2836' directly. But the manifest file will cause the installer showing 'The system can not find the file specified.' first then showing the 'Error 2836'. So this is slightly different from those two DLL files. As I mentioned, that's not a fatal error. There's some other error that might be helpful in diagnosing your root problem. 1. If my guess is correct, please post some links here about how to register a COM component correctly in 2.0. Meanwhile, I'll dig in this topic as well. Use Class, Interface, ProgId, Extension, Verb, TypeLib. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
First of all, thank you so much for your reply, Bob. There are a couple of other things, not sure if related: 1. Only 3 files cause the problem. According to the developer, one dll file is a COM component, the manifest is associated with the COM dll, another dll is used by the COM dll. I also noticed the COM dll is registered by using regsvr32.exe in a custom action. Not sure if this is the problem. But I've a feeling that COM registration doesn't work that way even I never register a COM in Wix. 2. Those two DLL files will cause 'Error 2836' directly. But the manifest file will cause the installer showing 'The system can not find the file specified.' first then showing the 'Error 2836'. So this is slightly different from those two DLL files. 3. I did look at the dll files' property, they seem normal. By using Orca, I also looked at the File table, these files entries look the same as others. From #1, my guess is the COM registration could cause the problem, but I'm not sure. Please point out if my guess is correct or not: 1. If my guess is correct, please post some links here about how to register a COM component correctly in 2.0. Meanwhile, I'll dig in this topic as well. 2. If my guess isn't correct, please point me out where I should look into, or which file or flag or something I should check. Thanks a lot. From: Bob Arnson b...@joyofsetup.com To: wix-users@lists.sourceforge.net Sent: Thu, March 25, 2010 5:58:55 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On 3/25/2010 7:53 PM, little.forest wrote: DEBUG: Error 2836: The control ChangeButton on the dialog MaintenanceTypeDlg can not take focus The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2836. The arguments are: MaintenanceTypeDlg, ChangeButton, That's not a fatal error; is there some other symptom you're seeing? -- sig://boB http://joyofsetup.com/ -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Tallow.exe in WiX v2.0 should be able to harvest the registry entries required for COM registration (assuming the DLL exports DLLRegisterServer function). Tallow.exe is with the WiX v2.0 equivalent of heat.exe in WiX v3.0. I don't have a WiX v2.0 install lying around but running tallow.exe /? should give you the parameters needed to harvest the COM registration info. Sounds like the problem is the Self Reg of the COM DLL. If one of the 2 DLL's or the manifest file is deleted it may not be able to re-run the Self Reg when you run your repair as it may not have replaced the files at that point. Yet another reason why Self-Reg is a very very very bad idea. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: 26 March 2010 18:12 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,then we'll get Error 2836 in Repair mode First of all, thank you so much for your reply, Bob. There are a couple of other things, not sure if related: 1. Only 3 files cause the problem. According to the developer, one dll file is a COM component, the manifest is associated with the COM dll, another dll is used by the COM dll. I also noticed the COM dll is registered by using regsvr32.exe in a custom action. Not sure if this is the problem. But I've a feeling that COM registration doesn't work that way even I never register a COM in Wix. 2. Those two DLL files will cause 'Error 2836' directly. But the manifest file will cause the installer showing 'The system can not find the file specified.' first then showing the 'Error 2836'. So this is slightly different from those two DLL files. 3. I did look at the dll files' property, they seem normal. By using Orca, I also looked at the File table, these files entries look the same as others. From #1, my guess is the COM registration could cause the problem, but I'm not sure. Please point out if my guess is correct or not: 1. If my guess is correct, please post some links here about how to register a COM component correctly in 2.0. Meanwhile, I'll dig in this topic as well. 2. If my guess isn't correct, please point me out where I should look into, or which file or flag or something I should check. Thanks a lot. From: Bob Arnson b...@joyofsetup.com To: wix-users@lists.sourceforge.net Sent: Thu, March 25, 2010 5:58:55 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On 3/25/2010 7:53 PM, little.forest wrote: DEBUG: Error 2836: The control ChangeButton on the dialog MaintenanceTypeDlg can not take focus The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2836. The arguments are: MaintenanceTypeDlg, ChangeButton, That's not a fatal error; is there some other symptom you're seeing? -- sig://boB http://joyofsetup.com/ -- Download Intel(r) Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
Thanks Palbinder. I'll try tallow. From: Pally Sandher pally.sand...@iesve.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, March 26, 2010 11:26:09 AM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode Tallow.exe in WiX v2.0 should be able to harvest the registry entries required for COM registration (assuming the DLL exports DLLRegisterServer function). Tallow.exe is with the WiX v2.0 equivalent of heat.exe in WiX v3.0. I don't have a WiX v2.0 install lying around but running tallow.exe /? should give you the parameters needed to harvest the COM registration info. Sounds like the problem is the Self Reg of the COM DLL. If one of the 2 DLL's or the manifest file is deleted it may not be able to re-run the Self Reg when you run your repair as it may not have replaced the files at that point. Yet another reason why Self-Reg is a very very very bad idea. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: 26 March 2010 18:12 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,then we'll get Error 2836 in Repair mode First of all, thank you so much for your reply, Bob. There are a couple of other things, not sure if related: 1. Only 3 files cause the problem. According to the developer, one dll file is a COM component, the manifest is associated with the COM dll, another dll is used by the COM dll. I also noticed the COM dll is registered by using regsvr32.exe in a custom action. Not sure if this is the problem. But I've a feeling that COM registration doesn't work that way even I never register a COM in Wix. 2. Those two DLL files will cause 'Error 2836' directly. But the manifest file will cause the installer showing 'The system can not find the file specified.' first then showing the 'Error 2836'. So this is slightly different from those two DLL files. 3. I did look at the dll files' property, they seem normal. By using Orca, I also looked at the File table, these files entries look the same as others. From #1, my guess is the COM registration could cause the problem, but I'm not sure. Please point out if my guess is correct or not: 1. If my guess is correct, please post some links here about how to register a COM component correctly in 2.0. Meanwhile, I'll dig in this topic as well. 2. If my guess isn't correct, please point me out where I should look into, or which file or flag or something I should check. Thanks a lot. From: Bob Arnson b...@joyofsetup.com To: wix-users@lists.sourceforge.net Sent: Thu, March 25, 2010 5:58:55 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On 3/25/2010 7:53 PM, little.forest wrote: DEBUG: Error 2836: The control ChangeButton on the dialog MaintenanceTypeDlg can not take focus The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2836. The arguments are: MaintenanceTypeDlg, ChangeButton, That's not a fatal error; is there some other symptom you're seeing? -- sig://boB http://joyofsetup.com/ -- Download Intel(r) Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
OK, I tried tallow. But it doesn't work. First, I tried tallow.exe -c my.dll, but I got System.BadImageFormatException. Then I tried tallow.exe -s my.dll, but I got System.Reflection.TargetInvocationException. I also tried heat from 3.0 heat.exe file my.dll -out my.wxs, but I only got this: Fragment DirectoryRef Id=mydir FileSource=C:\mydir Component Id=my.dll Guid=PUT-GUID-HERE File Id=my.dll Name=my.dll KeyPath=yes Source=C:\mydir\my.dll / /Component /DirectoryRef /Fragment There is no any COM related info there. Help please. I appreciate it. From: little.forest little.for...@ymail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, March 26, 2010 3:25:42 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode Thanks Palbinder. I'll try tallow. From: Pally Sandher pally.sand...@iesve.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Fri, March 26, 2010 11:26:09 AM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode Tallow.exe in WiX v2.0 should be able to harvest the registry entries required for COM registration (assuming the DLL exports DLLRegisterServer function). Tallow.exe is with the WiX v2.0 equivalent of heat.exe in WiX v3.0. I don't have a WiX v2.0 install lying around but running tallow.exe /? should give you the parameters needed to harvest the COM registration info. Sounds like the problem is the Self Reg of the COM DLL. If one of the 2 DLL's or the manifest file is deleted it may not be able to re-run the Self Reg when you run your repair as it may not have replaced the files at that point. Yet another reason why Self-Reg is a very very very bad idea. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: 26 March 2010 18:12 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,then we'll get Error 2836 in Repair mode First of all, thank you so much for your reply, Bob. There are a couple of other things, not sure if related: 1. Only 3 files cause the problem. According to the developer, one dll file is a COM component, the manifest is associated with the COM dll, another dll is used by the COM dll. I also noticed the COM dll is registered by using regsvr32.exe in a custom action. Not sure if this is the problem. But I've a feeling that COM registration doesn't work that way even I never register a COM in Wix. 2. Those two DLL files will cause 'Error 2836' directly. But the manifest file will cause the installer showing 'The system can not find the file specified.' first then showing the 'Error 2836'. So this is slightly different from those two DLL files. 3. I did look at the dll files' property, they seem normal. By using Orca, I also looked at the File table, these files entries look the same as others. From #1, my guess is the COM registration could cause the problem, but I'm not sure. Please point out if my guess is correct or not: 1. If my guess is correct, please post some links here about how to register a COM component correctly in 2.0. Meanwhile, I'll dig in this topic as well. 2. If my guess isn't correct, please point me out where I should look into, or which file or flag or something I should check. Thanks a lot. From: Bob Arnson b...@joyofsetup.com To: wix-users@lists.sourceforge.net Sent: Thu, March 25, 2010 5:58:55 PM Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode On 3/25/2010 7:53 PM, little.forest wrote: DEBUG: Error 2836: The control ChangeButton on the dialog MaintenanceTypeDlg can not take focus The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2836. The arguments are: MaintenanceTypeDlg, ChangeButton, That's not a fatal error; is there some other symptom you're seeing? -- sig://boB http://joyofsetup.com/ -- Download Intel(r) Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
[WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
We have an old product which uses Wix 2.0(a very stable version). Our test engineer found a problem: if some dll file(s) is manually deleted, then in Repair mode, we'll get Error 2836. Here is the error message from log: MSI (c) (B4:80) [16:22:22:313]: Note: 1: 2205 2: 3: Error MSI (c) (B4:80) [16:22:22:313]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2836 DEBUG: Error 2836: The control ChangeButton on the dialog MaintenanceTypeDlg can not take focus The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2836. The arguments are: MaintenanceTypeDlg, ChangeButton, In real case, I'd say no one would manually delete some files. But it could happen. Also as a test case, I think it's reasonable to test this scenario. And I thought, we're allowed to delete any file, then in Repair mode, we'll get all of our files back, correct? The strange thing is that it only happens for three files, not for all. If we delete some other files, Repair will work correctly. But I looked those files, they are really normal. I also check the msi in Orca. In the File table, they have normal attributes just like others. What make these files special? Is there a way to check what is wrong? Why removing a dll will cause something wrong in ChangeButton? I know 2.0 isn't supported any more. But for us, this old product is still using it. So if you know something, please let us know. Many thanks! __ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0: if some dll file(s) deleted, then we'll get Error 2836 in Repair mode
On 3/25/2010 7:53 PM, little.forest wrote: DEBUG: Error 2836: The control ChangeButton on the dialog MaintenanceTypeDlg can not take focus The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2836. The arguments are: MaintenanceTypeDlg, ChangeButton, That's not a fatal error; is there some other symptom you're seeing? -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
