This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Custom Action and Sequences
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 21, 2008
04:03 PM
Custom Action and Sequences
Hi Sir
I want to run my .rul file at the end after i have installed all files,copied all files to destination directory..what change should i make in "custom action and sequences" inorder to achieve the above mentioned condition,,,
what i suppose is "install exec sequence ->after install files" should be selected.Am i right or wrong
thanks
jagjit
I want to run my .rul file at the end after i have installed all files,copied all files to destination directory..what change should i make in "custom action and sequences" inorder to achieve the above mentioned condition,,,
what i suppose is "install exec sequence ->after install files" should be selected.Am i right or wrong
thanks
jagjit
(20) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 21, 2008
05:13 PM
Correct, plus you'll want "deferred execution" (probably in system context) for the scheduling.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 21, 2008
05:56 PM
It didnt work at all.Again the .rul files has been called first then the other required files are copied to the specific locations....
1.Is there any other way out so that script.rul file shud always execute at last after the files have been copied.....
2.I would also like to know the diff between "install UI sequence" and
"install exec sequence"...
1.Is there any other way out so that script.rul file shud always execute at last after the files have been copied.....
2.I would also like to know the diff between "install UI sequence" and
"install exec sequence"...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
01:32 AM
Robert is most likely on the right track.
What is the value of the "In-Script Execution" property for your custom action?
What is the value of the "In-Script Execution" property for your custom action?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
11:38 AM
i tried both "deferred execution" and "deferred execution in system context"
right now its deferred execution
right now its deferred execution
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
11:50 AM
Have you tried logging the installation?
If not, try a command similar to
msiexec /i ProductName.msi /l*v c:\msilog.txt
and post that file to this thread.
If not, try a command similar to
msiexec /i ProductName.msi /l*v c:\msilog.txt
and post that file to this thread.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
12:14 PM
Start with reading these two pages:
http://www.installsite.org/pages/en/isnews/200108/index.htm
http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!167.entry
http://www.installsite.org/pages/en/isnews/200108/index.htm
http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!167.entry
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
12:51 PM
can you plz tell me how should i log the installation and
where shud i try this command to generate a log.txt file
where shud i try this command to generate a log.txt file
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
12:57 PM
Run the command
Where YourFile.msi is the fully qualified path to your MSI (if there are embedded spaces in the file path, enclose the entire file spec in quotes).
This will generate a log file called C:\MsiLog.txt
msiexec /i YourFile.msi /l*v C:\MsiLog.txt
Where YourFile.msi is the fully qualified path to your MSI (if there are embedded spaces in the file path, enclose the entire file spec in quotes).
This will generate a log file called C:\MsiLog.txt
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
01:07 PM
this is what i got when i ran the command...
Windows ® Installer. V 3.01.4000.1823
msiexec /Option [Optional Parameter]
Install Options
Installs or configures a product
/a
Administrative install - Installs a product on the network
/j [/t ] [/g ]
Advertises a product - m to all users, u to current user
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*]
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log
Equivalent of /l*
Update Options
/update[;Update2.msp]
Applies update(s)
/uninstall[;Update2.msp] /package
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v]
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
Windows ® Installer. V 3.01.4000.1823
msiexec /Option
Install Options
Installs or configures a product
/a
Administrative install - Installs a product on the network
/j
Advertises a product - m to all users, u to current user
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*]
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log
Equivalent of /l*
Update Options
/update
Applies update(s)
/uninstall
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v]
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
01:14 PM
these are my settings in custom action and sequences
Function Name------------>MyFunction
Return processing------------>Synchronous(check exit code)
In-Script execution------------>Deferred Execution
Install UI Sequence------------>
Install Exec Sequence------------>after move files
Install Exec condition------------>---
Adverstise Exec Seq------------>
Admin UI sequence------------>
Admin Exec Seq------------>
I have set these conditions and plz let me know where i am wrong and what
changes should i make inorder to execute "MyFunction" at the end after all files have been copied
Function Name------------>MyFunction
Return processing------------>Synchronous(check exit code)
In-Script execution------------>Deferred Execution
Install UI Sequence------------>
Install Exec Sequence------------>after move files
Install Exec condition------------>---
Adverstise Exec Seq------------>
Admin UI sequence------------>
Admin Exec Seq------------>
I have set these conditions and plz let me know where i am wrong and what
changes should i make inorder to execute "MyFunction" at the end after all files have been copied
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
01:15 PM
That's the syntax of the msiexec command which appears when the syntax you've specified is incorrect (or you pass the /help parameter).
Can you post the command you used?
Can you post the command you used?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
01:17 PM
jagjit_82 wrote:
these are my settings in custom action and sequences
Function Name------------>MyFunction
Return processing------------>Synchronous(check exit code)
In-Script execution------------>Deferred Execution
Install UI Sequence------------>
Install Exec Sequence------------>after move files
Install Exec condition------------>---
Adverstise Exec Seq------------>
Admin UI sequence------------>
Admin Exec Seq------------>
I have set these conditions and plz let me know where i am wrong and what
changes should i make inorder to execute "MyFunction" at the end after all files have been copied
Move your custom action to after "InstallFiles" (which is typically the action after MoveFiles).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
01:23 PM
msiexec /i ProductName.msi /l*v c:\msilog.txt
i replace the ProductName with FinalRelease ab which is the name of my project and ran it under run command
i replace the ProductName with FinalRelease ab which is the name of my project and ran it under run command
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
01:31 PM
jagjit_82 wrote:
msiexec /i ProductName.msi /l*v c:\msilog.txt
i replace the ProductName with FinalRelease ab which is the name of my project and ran it under run command
If the product name has spaces it, enclose the entire file path in quotes.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
01:45 PM
this is what i have achieved when i put the product name into quotes
Windows ® Installer. V 3.01.4000.1823
msiexec /Option [Optional Parameter]
Install Options
Installs or configures a product
/a
Administrative install - Installs a product on the network
/j [/t ] [/g ]
Advertises a product - m to all users, u to current user
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*]
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log
Equivalent of /l*
Update Options
/update[;Update2.msp]
Applies update(s)
/uninstall[;Update2.msp] /package
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v]
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
Windows ® Installer. V 3.01.4000.1823
msiexec /Option
Install Options
Installs or configures a product
/a
Administrative install - Installs a product on the network
/j
Advertises a product - m to all users, u to current user
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*]
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log
Equivalent of /l*
Update Options
/update
Applies update(s)
/uninstall
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v]
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
02:44 PM
will anybody help me..it urgent
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
02:50 PM
I'm trying to help you, please check my post #12 of this thread. In it I stated:
That's the syntax of the msiexec command which appears when the syntax you've specified is incorrect (or you pass the /help parameter).
Can you post the command you used?
And you didn't report if you tried my suggestion of moving your action to after InstallFiles.
That's the syntax of the msiexec command which appears when the syntax you've specified is incorrect (or you pass the /help parameter).
Can you post the command you used?
And you didn't report if you tried my suggestion of moving your action to after InstallFiles.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
03:09 PM
i have mentioned the output in #16
msiexec /i "Final release".msi /l*v c:\msilog.txt
after running this command i have obtained the output shown in #16
msiexec /i "Final release".msi /l*v c:\msilog.txt
after running this command i have obtained the output shown in #16
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
03:15 PM
It's the filename that needs to be in quotes not the product name. Try
msiexec /i "Final release.msi" /l*v c:\msilog.txt
msiexec /i "Final release.msi" /l*v c:\msilog.txt
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
04:29 PM
before i proceed to next topic i got some prob with this
I have two files NBF.SYS and NETNBF.INF
I need NBF.SYS to copy to system32/drivers
and NETNBF.INF to windows/INF
i created setup file for this exe.
when i run exe for the first time it copies these two files to the required destinations.
but when i delete these two files and run the setup file again it donot copies these two files.can any body tell me how can i resolve this problem.
the ssetup is working fine.it also needs to copy some other files to required destinations and it is copying those files.either for first time or for second.
it has problem only with these two files
thanks
jagjit
I have two files NBF.SYS and NETNBF.INF
I need NBF.SYS to copy to system32/drivers
and NETNBF.INF to windows/INF
i created setup file for this exe.
when i run exe for the first time it copies these two files to the required destinations.
but when i delete these two files and run the setup file again it donot copies these two files.can any body tell me how can i resolve this problem.
the ssetup is working fine.it also needs to copy some other files to required destinations and it is copying those files.either for first time or for second.
it has problem only with these two files
thanks
jagjit