Christopher Painter wrote: Can you post a log? The SQL custom actions should scheduled after file installation by default. Perhaps you've played with it and have race condition. Are you using the same credentials via InstallShield and Management Studio? I am trying but some encapsula is telling me I am being denied access to post anything aside from text. Here is an excerpt from the log with the error ADO Error: Number: -2147217900 Description: Assembly 'MyAssembly' was not found in the SQL catalog of database 'MyDB'. Source: Microsoft OLE DB Provider for SQL Server SQL State: 42000 Native Error: 6528 1: There was a SQL scripting error at line 17. Aborting the setup. Yes, same credentials. some stupid encapsula website protection error pops up when I attempt to paste in the code blocks with the SQL code being ran. ... View more

hidenori wrote: If you run the same script from Microsoft SQL Server Management Studio, does it work? Yes.......... ... View more

This is the script portion: USE MyDB CREATE ASSEMBLY MyAssemblyFunctions FROM 'c:\Program Files (x86)\CompanyName\ProductName\Database\MyAssembly.dll' WITH PERMISSION_SET = SAFE; ... View more

weakness wrote: Hello. Generally, you cannot hold properties value after installation. You have to add custom action in order to preserve that value. InstallShield Tip: Saving MSI property values to make them available after the initial installation http://www.flexerasoftware.com/webdocuments/PDF/MsiPropUninst.pdf#acresso And, you can use condition property 'IS_MINOR_UPGRADE' in order to confirm if it's minor upgrade or not. http://kb.flexerasoftware.com/selfservice/viewContent.do?externalId=Q112517 I didn't test it, but you might be able to set the Property to ISSearchReplaceInstall custom action and re-run it or not... Interesting... kinda what I thought. Thanks for the reply! ... View more

JohnCresswell wrote: This fix is targeted specifically for the problem with non .ico files. I have not been able to reproduce the problem of using an ico file in house so if you are experiencing this problem could you please provide file that can be used to demonstrate this issue and I will take a look. John, I have attached the ico file that I am attempting to use as the Suite project's ARP icon. It errors with: ISDEV : warning -7212: The icon for the setup.exe could not be updated. Setup.exe will use the default icon. ... View more

Did this help you? ... View more

joshstechnij wrote: Changing the target directory of a Windows Installer package in maintenance mode is not supported: Why can't I change the target directory path during a Maintenance Installation? Unfortunately, there aren't really any ways around this except for installing as a major upgrade (or uninstalling/reinstalling for the same version). Darn... thats what I had figured. Ill have to note that in our deployment documentation so I dont get flack back lol. ... View more

Ill save you the trouble... When you create a text field in a dialog box, it prompts you for the property name to be associated with that text field. Enter a property name (all uppercase, no spaces or characters) to identify the property. Go to the Property manager section Locate your newly created property and you will notice it defaults to containing a digit, edit it and delete that digit so that the property value is empty. Now.... you have created your property which is step 1 Step 2 is you creating the file you wish the property to live in. For sake of simplicity, create a text document that contains a placeholder. The placeholder is simply a string of text that is unique and will later display the value from the property you created in step 1. Something like {PlaceHolder} should suffice. Save your text file, add it as a component that is installed with your feature. Step 3.... the replacing of the placeholder with the value from your property. Under the "System Configuration" section, you will see something called "Text File Changes". Select that. Now in your center window pane you will see the parent "Text File Changes" with no children. Right click and select "Add Replacement Set". I typically name my replacement set after the filename of the text file you will be doing your search/replace in. So take the file name of the file you created in step 2, and add use it here. Left click your newly named replacement set and you will see configuration settings in the right window pane. Choose your target folder (same target as the component of the text file you created in step 2) In the "Include files" section, change the defaulted "*.txt" to the filename of the file you will be doing the search/replace created in step 2. The other configuration settings can be used when you begin getting more complex with your search/replace The setting "Run on Install" should" be "Yes" and the component should be modified to be the component that contains the file you are doing the search/replace on. Now... in the center window pane, right click the replacement set you created, and choose "Add Replacement". I usually name this after what I am replacing. Just makes it easier when you look at it later to figure out what you are doing. Now in the right window pane, you have new configuration settings and they are pretty self explanitory. Choose the "Find What" field and enter in the unique placeholder you created in Step 2 "{PlaceHolder}" (without the quotes) In the "Replace With" field, enter in the public property you created in step 1 [PROPERTY] (remember its a public property so all upper case) The other 3 options I generally keep as No but you can tweak it further. And that is it. Now as long as your txt file is part of a component, and your component is part of a feature being installed.... and you used the correct syntax and spelling... it should do the replace on install. Once you get the hang of that... you can get more complex with uninstalls, rollbacks, multiple replaces, wildcard searches and so forth. You can also have it create the file it does the search/replace on... but this is the easiest in your case to start with. ... View more

Ok, so we re-wrote some code so that we can pass the config file into the DLL and it runs... however we hit another snag on the same process. Essentially as I have mentioned, the DLL reads information from a config file and transmits that information to a database table. Now that we have the DLL reading the config file correctly, it is attempting to transmit that information to the database however it is erroring out with a "user without sifficient privledges" error. The logged in user that is kicking off the install, is an admin and has rights to the database... however the install process is using some other user account and I cannot seem to figure out where it is pulling it from or how to force it to use a specific account. Any other ideas? ... View more

stevenparabit wrote: Hello. I just started this week on installsheild and i'm a little stuck. I have a custom dialog box that asks the person for three values that will be used latter by the application. Can some one point me to how I might save these values for the VB .Net application to read. I have no preference where the values are saved. It could be an XML, Registry or INI. I can read any thing so it does not matter. Thanks. Using a Basic MSI, you can have a text file, config file, xml file or whatever and do a text replace (text file changes) with the properties populated from the values in your fields. First get your values to save to a public property Then use the text file changes selection to create a text file change where it replaces some placeholder in a file with the value's of your public properties created previously. The help has a detailed instruction on doing so... and I would highly recommend the training that Flexera offers for creating Basic MSI's. I took the training and it was great! ... View more

I also am having issues. My ico file works in basic msi packages just fine but will not work on the suite project. I have the full premier edition, not the evaluation. ... View more

No... Ive gotten the service creation etc down pat... this one is a bit different. Essentially through the user interview process, we ask for database servers and database names. THen through text replace, the answers are swapped in a config file. This config file contains an extremely large section of web service pointers. When Installutil is run on the DLL I am trying to install, it takes this web service address and then enters it into the database with location information of the dll and other things so that the company framework knows where the product was installed. It was designed pre-installshield so it may be something that we have to re-design. I just wish there was a way to literally tell the installerclass to run from the [INSTALLDIR] rather than the system32 folder. ... View more