Christopher Painter wrote: What project type are you using? What you are describing is a Multiple Instance installation servicing pattern and both InstallScript and MSI projects support it, but in different ways. how this can be acheive in Basic MSI project type? ... View more

Where from we get the Beta version of IS2009? I would like to test our application in newer version of IS before its available. ... View more

....another issue is when I am testing the major upgrade, my installation stops on IsPreventDowngrade CA, even the version I am installing is higher then the one already installed, this is from the log file: MSI (c) (C8 D0) [13:00:55:504]: Doing action: ISSetAllUsers Action 13:00:55: ISSetAllUsers. Action start 13:00:55: ISSetAllUsers. MSI (c) (C8:BC) [13:00:55:854]: Invoking remote custom action. DLL: C:\DOCUME~1\mkhan\LOCALS~1\Temp\MSI27.tmp, Entrypoint: SetAllUsers InstallShield 13:00:56: Begin SetAllUsers() InstallShield 13:00:56: Getting records from Upgrade table InstallShield 13:00:56: UpgradeCode: {9284EE81-AB2C-4E05-9CD3-6A79009D97AB} MinVersion: MaxVersion: 5.00.0079 Language: Attributes: 257 InstallShield 13:00:56: Checking related product {DC0DC59A-AA74-470F-BE4A-552F618CCFE8} InstallShield 13:00:56: My System {DC0DC59A-AA74-470F-BE4A-552F618CCFE8} 1033 5.00.0078 ***Related*** MSI (c) (C8!C0) [13:00:56:966]: PROPERTY CHANGE: Adding IS_MAJOR_UPGRADE property. Its value is 'Yes'. InstallShield 13:00:56: ALLUSERS of related product {DC0DC59A-AA74-470F-BE4A-552F618CCFE8} is = 1 MSI (c) (C8!C0) [13:00:56:976]: PROPERTY CHANGE: Adding ALLUSERS property. Its value is '1'. InstallShield 13:00:56: End SetAllUsers() Action ended 13:00:57: ISSetAllUsers. Return value 1. MSI (c) (C8 D0) [13:00:57:086]: Doing action: FindRelatedProducts Action 13:00:57: FindRelatedProducts. Searching for related applications Action start 13:00:57: FindRelatedProducts. FindRelatedProducts: Found application: {DC0DC59A-AA74-470F-BE4A-552F618CCFE8} MSI (c) (C8 D0) [13:00:57:086]: PROPERTY CHANGE: Adding ISACTIONPROP1 property. Its value is '{DC0DC59A-AA74-470F-BE4A-552F618CCFE8}'. MSI (c) (C8 D0) [13:00:57:086]: PROPERTY CHANGE: Adding MIGRATE property. Its value is '{DC0DC59A-AA74-470F-BE4A-552F618CCFE8}'. Action ended 13:00:57: FindRelatedProducts. Return value 1. MSI (c) (C8 D0) [13:00:57:086]: Doing action: ISPreventDowngrade Action 13:00:57: ISPreventDowngrade. Action start 13:00:57: ISPreventDowngrade. My Error Message MSI (c) (C8 D0) [13:00:59:449]: Product: My System -- My Error Message Action ended 13:00:59: ISPreventDowngrade. Return value 3. ... View more

RobertDickau wrote: Backing up a bit, in your newer project have you changed the ProductCode and ProductVersion properties (for the latter, changed one of the first three fields) and changed the package code? Have you authored a major upgrade item in the Upgrades view? To test the deployment, you can generate an MSI log file when deploying the major upgrade, and then searching the log file for FindRelatedProducts and ISSetAllUsers to determine what MSI is looking for and perhaps failing to find. Yes, on every time I build the package, I update the Product Code, Package Code and Product Version, also I have Major Upgrade setup and following is the value in Upgrade Table: UpgradeCode: {9284EE81-AB2C-4E05-9CD3-6A79009D97AB} VersionMin: VersionMax:***ALL_VERSIONS*** Language: Attributes:257 Remove: ActionProperty:ISACTIONPROP1 ISDisplayName:FullUpgrade and in SecureCustomProperties i have ISACTIONPROP1 Also I have ISPreventDowngrade CA type 19, and Install UI Condition and Install Exec Condition are set to ISACTIONPROP1. My objective to acheive is to authored the installation which prevent downgrade and at the same time prevent the installation or starting the maintenance if the same version of the product is already installed, but if the earlier version of the product is installed then first completely removed the previous version and installed the newer version. thanks, -Moin ... View more

nikhilgupta wrote: Select the product configuration for the release, and set the value of "generate package code" to yes. then goto Upgrades view, for small/minor upgrade settings select "disable". this should meet your requirement. I already have that setting set to yes and disable, but still when I try to install the package which is already installed on a machine I got the maintenance window. ... View more

joshstechnij wrote: Thanks for your feeback! Please let me know if you encounter any issues with the hotfix DLL. I have a quick question in this thread, I am new to MSI installation on Windows 2008 with IIS7, I use my existing MSI package which installed fine on Windows 2003 Server running IIS6, but on Windows 2008 with IIS7 I got the following error on the log file, any idea what could cause such error or do i need to do anything on my MSI package? I am using Basic MSI on IS2008 Premier edition. MSI (s) (2C:68) [15:07:10:825]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI510D.tmp, Entrypoint: CreateIISVRoots 1: This machine does not support legacy objects 1: InitIISObject 1: CoGetClassObject(GETAdminBaseCLSID(TRUE) error: -2147221164 1: Legacy objects not supported Action 15:07:11: Progress Custom Action. Creating application Pools... Action 15:07:11: Progress Custom Action. Creating web service extensions... Action 15:07:11: Progress Custom Action. Creating IIS virtual directories... Action 15:07:11: Progress Custom Action. Creating IIS virtual directory MyVDir 1: SetCommitPath for website '' and app '' 1: InstallShield project contains a website with name 'Default Web Site', site number '0', and port '80'. Checking if it exists... 1: GetAdminSection for section 'system.applicationHost/sites' and path 'MACHINE/WEBROOT/APPHOST' and commitpath 'MACHINE/WEBROOT/APPHOST'. 1: Check if site has port number: 80 1: GetBindingsCollection 1: Searching for binding element 1: GetPortFromBindingInfo: *:80: 1: Found site with the same port number. 1: Website exists. Additonal info: Site number '1', Port '80', sBasePath '/LM/W3SVC/1/Root', DisplayName 'Default Web Site' 1: Creating application 'BestMatchSimulatorGUI' with virtual directory 'MyVDir', website '1', and physical path: 'C:\Program Files\SMS\MyVDir\' 1: No element found with property 'path' value of '/MyVDir'. 1: Exception caught in PutPropertyValue for property 'path' with value 'MyVDir' 1: Attempt to change property value had problems, HRESULT: -2105 1: Error with IISRT: -2105 Action ended 15:07:12: InstallFinalize. Return value 3. ... View more

Alpesh wrote: Hi Moin, I hope this information from a different thread helps you - If InstallShield encounters a problem reading the xml file then it throws error 27520 which reads 'error opening file' although the problem is with reading the xml in the file not in opening it! This is what is currently happening when I add the DOCTYPE declaration to the xml file. Here are the threads which may interest you - http://community.macrovision.com/showthread.php?t=150017 http://community.macrovision.com/showthread.php?t=143739&page=5 Thanks, Alpesh Hi Alpesh, I can understand the error opening file cause by reading the actual XML file, I mostly got the followin error and I now able to capture the error in log file, and I am pasting it here, Please look into this: InstallShield 17:10:33: Node name: 'add' - Attribute name = 'value', Old Value = 'http://localhost/Imaging/services/indexmanager/IndexService.asmx', New value = 'http://localhost/Imaging/services/indexmanager/IndexService.asmx', Actual New Value = 'http://localhost/Imaging/services/indexmanager/IndexService.asmx' InstallShield 17:10:33: Saving XML file 'C:\Program Files\SMS\Web.config' InstallShield 17:10:33: Formatting XML document InstallShield 17:10:33: Using MSXML version 3 InstallShield 17:10:33: Loading stylesheet InstallShield 17:10:33: Successfully loaded stylesheet InstallShield 17:10:33: Using MSXML version 3 InstallShield 17:10:33: Done Formatting XML document Error 27519.Error updating XML file C:\Program Files\SMS\Web.config. -2147024891 MSI (s) (D8!88) [17:19:14:339]: Product: My System -- Error 27519.Error updating XML file C:\Program Files\SMS\Web.config. -2147024891 Error 27519.Error updating XML file C:\Program Files\SMS\Web.config. -2147024891 MSI (s) (D8!88) [17:19:31:127]: Product: My System -- Error 27519.Error updating XML file C:\Program Files\SMS\Web.config. -2147024891 Thanks, -Moin ... View more

DebbieL wrote: As the "Creating an XML File Reference" help topic states: Is it possible for you to add the XML file to your project through the Files and Folders view, and then in the XML File Changes view, could you import only the nodes that you want to edit on the target machine after the file is installed? Debbie Landers Macrovision Corporation Yes, that was my initial design to do that, but after I migrate my project from IS12 to IS2008, i am getting the error as I mentioned in my previous post http://community.macrovision.com/showthread.php?t=174235 somehow before updating the config file IS2008 change its attribute to RHSAO and then give an error that unable to update the config file. -Moin Khan ... View more

anyone who has XML expertise can give me some idea of how to resolve such issue? the configsection should be created first, but in IS2008 creating in middle, causing XML to fail. ... View more

MichaelU wrote: Note also the -z parameter, new to IS2008, which allows you to override properties from the command line. Both ProductVersion and ProductCode are properties, and the package code is generally set to be generated fresh each build (check your releases view > product configuration to be sure). Nice, I can try that, is there any functionality in within IS2008 to generate GUID from a cmdline? ... View more