Check is the 'Always Overwrite' tag is set for these files. If it is it assigns a version of 255.255.65534 to the file(s). This would cause the Validaiton to see it as a versioned file. Hence the need for the language designation. ... View more

You can skip the actions that register the program, features and components. Not recommended because it leaves you with the possibility of having an MSI do a couple of odd things. Perpetual repair if it breaks in the right place, break and have to be manually cleaned up, and of course there is little or no auditing capabilities if you do this. It sounds like you are saying you want to run an MSI as a non-msi. Hmmmmm. There are better ways to do what you are looking to do. iExpress, VBScript, JSctript, SMS Installer, Bat2Exe, cmd or bat files, Heck even xCopy and Robocopy are better etc... What is the reason for the MSI if you aren't using any of it's functionality other then to copy files? The way I see it there are too many cons not enough pros. This quesiton sounds strnagely familiar to me though... :confused: ... View more

OK. I see one thing that may be the issue. Look at this then let me know. The Custom Action is scheduled as an immediate action for In Script Execution but is also scheduled under the Execute sequence. Try moving it to the Install UI Sequence anytime after Cost Initialize. Do this for both Custom Actions and let me know what happens. Thanks, Bill V. ... View more

Very good! ... View more

“I see the PORT in the PropertyManager and not in the DirectEditor!” Do you mean that you see the PORT property with declared value in the Property Manager but not in the Property table in the direct editor? In InstallShield the Property Manager is a direct representation of the Property Table which can be seen in the Direct Editor. So if this is what you are saying this is peculiar. However putting a property in the XML view anywhere that has not already been declared in the Property Manager only makes the MSI look for the value of that property at run time but does not set its value. I hope I am reading this right from your second post. “The really weird thing is in the PropertyManager, the Name is listed as PORT and the Value is listed as {ID_STRING19}1234. This is the 1234 value that is populated in the XML file!” This is normal. First, the ID_STRING19 is only telling you that the string ‘1234’ is localizable. You can ignore that but if possible I would make it NOT Localizable by recreating it and doing so a a regular property. Second, since the Property Manager has declared this value for the port, ‘1234’ that is what appears to be used during runtime. So there isn’t a change. If it does change maybe there is a scheduling issue with the Custom Action. If possible can you send a couple screen shots of the CA, the XML config, and the Property table from the Direct Editor? Or better yet attach the ISM zipped if there is no sensitive info in it. Thanks, Bill V. ... View more

Hello again, The Chained MSI can run with its own settings. You can pass it certain command lines. There is one issue I am not very fond of for Chained MSI(s) though... That is if the original MSI is installed with a couple MSI(s) chained, and the original MSI is later uninstalled, the chained MSI(s) get uninstalled automatically as well. But to counter this in a way you can uninstall any one of the chained MSI(s) on their own without affecting the other MSI(s). Your standard options for a chained MSI in IS2009 are as follows: Installation (run-time path): Where is the MSI located Product code: Pretty self explanatory UI level: Choices are pretty standard Full UI (/qf) Basic UI (/qb) Reduced UI (/qr) No UI (/qn) Install condition: Any standard conditional statement Install properties: So you can declare values for any Installer Property Removal condition: Any standard conditional statement. The default of course is REMOVE="ALL" Removal properties: So you can declare values for any Installer Property for use during uninstall Release flags: To declare which builds you want the chained MSI to be part of. And you can do anything you like within the chained MSI itself. I hope this helps. Let me know if you have any other questions too. Thanks, Bill V. I attached a screen shot of the Chained MSI configuration screen for reference to these options. ... View more

Have you looked though your file table for a corrupted entry? Maybe a MSM that is corrupt or incomplete? Just a thougt. I must admit it is a strange error. Thank you, Bill V. ... View more

Are you using the Chained MSI method? Let me know, Bill V. ... View more

Specifying the Setup Launcher Type (Unicode or ANSI) for a Release InstallShield 2009 Project This information applies to the following project types: Basic MSI Web InstallShield creates ANSI setup launchers for InstallScript MSI and InstallScript projects; it does not support the creation of Unicode setup launchers for these project types. If your release includes a setup launcher, InstallShield lets you specify the type of setup launcher that you want to build: Unicode—A Unicode setup launcher can correctly display double-byte characters in the setup launcher dialogs, such as the PreparingToInstall dialog, regardless of whether the target system is running the appropriate code page for the double-byte-character language. Windows 9x does not support Unicode setup launchers. ANSI—An ANSI setup launcher displays double-byte characters in the setup launcher dialogs if the target system is running the appropriate code page. However, it displays garbled characters instead of double-byte characters in those dialogs if the target system is not running the appropriate code page. Task To specify the setup launcher type for a release: In the View List under Media, click Releases. In the Releases explorer, click the release that you would like to configure. Click the Setup.exe tab. For the Setup Launcher Type setting, select the appropriate option. Tip To learn about scenarios that require a Setup.exe setup launcher, see Creating a Setup Launcher. See Also Setup.exe Tab for a Release --------------------------------------------------------------------------InstallShield Help Library 5 June 2008 Does this help? ... View more

Can you run the MSI through the InstallShield debugger and see what the property values are at the various stages? This will tell you at least if it is populating the [PORT] property correctly, passing it off correctly, etc... Let me know what you find. Thank you, Bill V. ... View more