Install of MSI (created using installshield) fails on update

Topics: Updater Application Block
Mar 23, 2007 at 1:21 AM
We have an auto update application and we already have updates posted on server and updates are all msi application which installs a new msi for each update. These msi were build using Setup and deployment project. The current solution updates and adds updates with no issue.

We created a new msi using Installshield and manifest files are read correctly, msi downloaded to client but the msi is not installed. We get

MSI 1729 Error : Product <applicationName> - Configuration failed.

We are using june 2005 enterprise library.

Event Type: Error
Event Source: ApplicationUpdater
Event Category: None
Event ID: 1000
Date: 3/22/2007
Time: 4:34:20 PM
User: N/A
Computer: D040008

Summary for :
--> MachineName: D040008
--> TimeStamp: 3/22/2007 11:34:20 PM
--> FullName: Microsoft.Practices.EnterpriseLibrary.Common, Version=, Culture=neutral, PublicKeyToken=be9225e5145f4774
--> AppDomainName: PostApplicationExitActivationProcess.exe
--> WindowsIdentity: D040008\M1-SKDCAccount

Exception Information Details:
Exception Type: System.Runtime.InteropServices.COMException
ErrorCode: -2147467259
Message: InstallProduct,PackagePath,PropertyValues
Data: System.Collections.ListDictionaryInternal
TargetSite: System.Object ForwardCallToInvokeMember(System.String, System.Reflection.BindingFlags, System.Object, Int32[], System.Runtime.Remoting.Proxies.MessageData ByRef)
HelpLink: Msi.chm#9008
Source: Msi API Error

StackTrace Information Details:
at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at WindowsInstaller.Installer.InstallProduct(String PackagePath, String PropertyValues)
at Microsoft.ApplicationBlocks.Updater.ActivationProcessors.MsiProcessor.Execute()
at Microsoft.ApplicationBlocks.Updater.Activator.ActivationManager.Activate(UpdaterTask task)

For more information, see Help and Support Center at

Is there any update in enterprise library with this isssue or its purely installshield issue?