We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

raddad555
Posts: 23
Joined: Sat Feb 09, 2013 3:40 pm

Best Practices and concepts

I have four scenarios that will decide on what gets installed as well as whether or not an sql query needs to install a database as well as if a custom action need to be launched that is an executable.

1. An iniital install that should install all files and create/attach a database (on a local or remote sql server)--**server**
2. An upgrade of files on the main server -- **server**
3. initial install for a client that also needs to create folders (some of which will be empty) -- **client**
4. An upgrade of client software only installing files. -- **client **

Problems I have experienced:

1. main feature (visible) does initial server install , runs the executable (custom action), but does not run the sql script
2. client called mxrupgrade does not install in the correct location, I use the search to find the proper location (result_property does show that it found the correct location) but the files are being placed in a folder called result_property instead of the value found. If I have the pipe character in front of the target folder then I get an error that its an invalid or some portion of the folder is missing or exceeds the length.

I have been trying to follow through the tutorials nut now banging my head as to what it is I am not understanding, could you please provide me with the best practices for the above scenarios. I also would like to know if there are or going to be any classes held for using Advanced Installer. I was really good at the wise installation since I am a programmer and was able to create and installer almost as if I was programming. Any help and information is appreciated.

Warren
Attachments
MxrAI.aip
Added in case it would help to understand my questions or if you need to test
(303.86 KiB) Downloaded 417 times
raddad555
Posts: 23
Joined: Sat Feb 09, 2013 3:40 pm

Re: Best Practices and concepts

More info as to why files wont install in the correct directory:

AppSearch: Property: RESULT_PROPERTY, Signature: AppSearchSign
MSI (c) (FC:68) [16:11:25:598]: Note: 1: 1324 2: maxrecall\programs 3: 1
MSI (c) (FC:68) [16:11:25:599]: Note: 1: 1324 2: maxrecall\programs 3: 1
MSI (c) (FC:68) [16:11:25:600]: PROPERTY CHANGE: Adding RESULT_PROPERTY property. Its value is 'C:\maxrecall\programs\'. :?
AppSearch: Property: MXR, Signature: AppSearchSign_1
MSI (c) (FC:68) [16:11:25:618]: Note: 1: 1325 2: Maxrecall
MSI (c) (FC:68) [16:11:25:662]: PROPERTY CHANGE: Adding MXR property. Its value is 'C:\Maxrecall\'.
AppSearch: Property: MXRYN, Signature: FileSearchSign
MSI (c) (FC:68) [16:11:25:667]: Note: 1: 1322 2:
MSI (c) (FC:68) [16:11:25:669]: Note: 1: 1322 2:
MSI (c) (FC:68) [16:11:25:674]: PROPERTY CHANGE: Adding MXRYN property. Its value is 'C:\3.3\Binary\zzadmin.exe'.
Action ended 16:11:25: AppSearch. Return value 1.
MSI (c) (FC:68) [16:11:25:676]: Doing action: FindRelatedProducts
Action 16:11:25: FindRelatedProducts. Searching for related applications
Action start 16:11:25: FindRelatedProducts.
Action ended 16:11:25: FindRelatedProducts. Return value 1.
MSI (c) (FC:68) [16:11:25:684]: Doing action: LaunchConditions
Action 16:11:25: LaunchConditions. Evaluating launch conditions
Action start 16:11:25: LaunchConditions.
Action ended 16:11:25: LaunchConditions. Return value 1.
MSI (c) (FC:68) [16:11:25:691]: Doing action: AI_SETMIXINSTLOCATION
Action 16:11:25: AI_SETMIXINSTLOCATION.
Action start 16:11:25: AI_SETMIXINSTLOCATION.
MSI (c) (FC:24) [16:11:25:725]: Invoking remote custom action. DLL: C:\Users\WarrenEB\AppData\Local\Temp\MSIA466.tmp, Entrypoint: MixedAllUsersInstallLocation
MSI (c) (FC!F4) [16:11:25:808]: PROPERTY CHANGE: Adding AI_UserProgramFiles property. Its value is 'C:\Program Files (x86)\'.
Action ended 16:11:25: AI_SETMIXINSTLOCATION. Return value 1.
MSI (c) (FC:68) [16:11:25:875]: Doing action: AI_RESTORE_LOCATION
Action 16:11:25: AI_RESTORE_LOCATION.
Action start 16:11:25: AI_RESTORE_LOCATION.
MSI (c) (FC:34) [16:11:25:906]: Invoking remote custom action. DLL: C:\Users\WarrenEB\AppData\Local\Temp\MSIA522.tmp, Entrypoint: RestoreLocation
Action ended 16:11:25: AI_RESTORE_LOCATION. Return value 1.
MSI (c) (FC:68) [16:11:25:961]: Doing action: SET_APPDIR
Action 16:11:25: SET_APPDIR.
Action start 16:11:25: SET_APPDIR.
MSI (c) (FC:68) [16:11:25:964]: PROPERTY CHANGE: Adding APPDIR property. Its value is 'C:\Program Files (x86)\Maxrecall'.
Action ended 16:11:25: SET_APPDIR. Return value 1.
MSI (c) (FC:68) [16:11:25:966]: Doing action: SET_SHORTCUTDIR
Action 16:11:25: SET_SHORTCUTDIR.
Action start 16:11:25: SET_SHORTCUTDIR.
MSI (c) (FC:68) [16:11:25:968]: PROPERTY CHANGE: Adding SHORTCUTDIR property. Its value is 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Maxrecall'.
Action ended 16:11:25: SET_SHORTCUTDIR. Return value 1.
MSI (c) (FC:68) [16:11:25:973]: Doing action: CostInitialize
Action 16:11:25: CostInitialize. Computing space requirements
Action start 16:11:25: CostInitialize.
MSI (c) (FC:68) [16:11:25:978]: Machine policy value 'MaxPatchCacheSize' is 10
MSI (c) (FC:68) [16:11:25:980]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'C:\'.
MSI (c) (FC:68) [16:11:25:981]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'.
Action ended 16:11:25: CostInitialize. Return value 1.
MSI (c) (FC:68) [16:11:25:983]: Doing action: FileCost
Action 16:11:25: FileCost. Computing space requirements
Action start 16:11:25: FileCost.
MSI (c) (FC:68) [16:11:25:990]: Note: 1: 2205 2: 3: MsiAssembly
MSI (c) (FC:68) [16:11:25:990]: Note: 1: 2205 2: 3: Registry
MSI (c) (FC:68) [16:11:25:991]: Note: 1: 2205 2: 3: Registry
MSI (c) (FC:68) [16:11:25:992]: Note: 1: 2205 2: 3: Class
MSI (c) (FC:68) [16:11:25:992]: Note: 1: 2205 2: 3: Extension
MSI (c) (FC:68) [16:11:25:993]: Note: 1: 2205 2: 3: TypeLib
Action ended 16:11:25: FileCost. Return value 1.
MSI (c) (FC:68) [16:11:25:996]: Note: 1: 2205 2: 3: AI_PreRequisite
MSI (c) (FC:68) [16:11:25:997]: Note: 1: 2228 2: 3: AI_PreRequisite 4: SELECT `Options`,`Feature_`,`MissingCondition`,`DisplayName` FROM `AI_PreRequisite`
MSI (c) (FC:68) [16:11:26:000]: Doing action: CostFinalize
Action 16:11:26: CostFinalize. Computing space requirements
Action start 16:11:26: CostFinalize.
MSI (c) (FC:68) [16:11:26:006]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (c) (FC:68) [16:11:26:007]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (c) (FC:68) [16:11:26:008]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (c) (FC:68) [16:11:26:008]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (c) (FC:68) [16:11:26:009]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (c) (FC:68) [16:11:26:010]: Note: 1: 2262 2: Patch 3: -2147287038
MSI (c) (FC:68) [16:11:26:012]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'C:\'. :?
raddad555
Posts: 23
Joined: Sat Feb 09, 2013 3:40 pm

Re: Best Practices and concepts

MSI (c) (FC:68) [16:11:26:012]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'C:\'.
MSI (c) (FC:68) [16:11:26:013]: PROPERTY CHANGE: Modifying APPDIR property. Its current value is 'C:\Program Files (x86)\Maxrecall'. Its new value: 'C:\Program Files (x86)\Maxrecall\'.
MSI (c) (FC:68) [16:11:26:014]: Note: 1: 1322 2:
Error 1322. A portion of the folder path '' is invalid. It is either empty or exceeds the length allowed by the system.
MSI (c) (FC:68) [16:25:05:111]: Product: Maxrecall -- Error 1322. A portion of the folder path '' is invalid. It is either empty or exceeds the length allowed by the system.
:?:
Action ended 16:25:05: CostFinalize. Return value 3.
MSI (c) (FC:68) [16:25:05:129]: Doing action: FatalError
Action 16:25:05: FatalError.
Action start 16:25:05: FatalError.
MSI (c) (FC:10) [16:25:13:449]: PROPERTY CHANGE: Deleting AI_LOG_CHECKBOX property. Its current value is '1'.
Action ended 16:25:15: FatalError. Return value 2.
MSI (c) (FC:68) [16:25:15:067]: Note: 1: 2205 2: 3: Environment
MSI (c) (FC:68) [16:25:15:068]: Note: 1: 2228 2: 3: Environment 4: SELECT `Environment`,`Component_` FROM `Environment`
MSI (c) (FC:C0) [16:25:15:100]: Destroying RemoteAPI object.
MSI (c) (FC:B0) [16:25:15:187]: Custom Action Manager thread ending.
=== Verbose logging stopped: 9/9/2013 16:25:15 ===

MSI (c) (EC:0C) [16:25:25:785]: PROPERTY CHANGE: Modifying InstallMode property. Its current value is 'Typical'. Its new value: 'Custom'.
Action ended 16:25:35: SetupTypeDlg. Return value 1.
MSI (c) (EC:AC) [16:25:35:925]: Doing action: UpdateFeaturesInstallStates
Action 16:25:35: UpdateFeaturesInstallStates.
Action start 16:25:35: UpdateFeaturesInstallStates.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Best Practices and concepts

Hello Warren,
1. main feature (visible) does initial server install , runs the executable (custom action), but does not run the sql script
This may happen if the condition set in the "Condition" field from "SQL Script" tab is not fulfiled. Also, the sql script will not be executed if the condition of your SQL connection is not true.
2. client called mxrupgrade does not install in the correct location, I use the search to find the proper location (result_property does show that it found the correct location) but the files are being placed in a folder called result_property instead of the value found. If I have the pipe character in front of the target folder then I get an error that its an invalid or some portion of the folder is missing or exceeds the length.
In order to achieve this you should create a property-based folder using your "RESULT_PROPERTY" property. Also, you can take a look on our "Install files in a custom folder" how to which could be useful for you.
I have been trying to follow through the tutorials nut now banging my head as to what it is I am not understanding, could you please provide me with the best practices for the above scenarios. I also would like to know if there are or going to be any classes held for using Advanced Installer. I was really good at the wise installation since I am a programmer and was able to create and installer almost as if I was programming. Any help and information is appreciated.
Since you are new, I highly recommend you read our tutorials for a better understanding of how to use Advanced Installer to efficiently deploy your products. This will also help you better understand support team's suggestions now and in the future. The Simple and Professional tutorials are especially important.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”