I'm attempting to sequence Sybase 12.0 Client, Sybase 12.0 Server, and a specific application as part of an application suite. Per the suite installation instructions, there are 5 reboots. At the end of the client & server installations, numerous dlls are getting replaced (i.e. mfc42.dll). In the instructions, I'm supposed to select 'Yes' to overwrite each of the identified dlls. Because the dlls are locked or being used, the Sybase software requires that the system reboot to replace these dlls & to complete the Sybase Studio Installer script - E:\Sybase12.0_Client\restart.bat E: \Sybase12.0_Client noname q:\sybase\reboot.sav - where E: is the CD-ROM drive. The script entry was found under the HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce key.

If I…
• click ‘Yes’ to reboot,
• ‘Stop Monitoring’ to process the reboot,
• ‘Begin Monitoring’ again
• & run the script,
I receive a ‘System Reboot’ error message that states ‘Reboot failed to properly rename locked dll’s. Execution Aborted.’ just like I would if I didn’t reboot the system during a standard install & ran the script.

Is there a best practice for processing these dlls (unlocking & replacing like a reboot would do) so I can continue on with the Sybase Studio Installer script that needs to be run after rebooting?

I'm using my standard physical sequencing laptop:
• 2 partitions (C=25GB / Q=30 GB)
• WinXP SP2
• Office 2003
• SG Sequencer
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


I just repackage the whole install into some sort of installer then run the new installer through the sequencer. It usually does the trick for me when the reboot processing isn't making the application installer happy.
Answered 05/16/2007 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Thanks - I had a feeling that might be the quickest way to resolve this.
Answered 05/16/2007 by: BadShadd
Orange Senior Belt

Please log in to comment
I should mention that I have sequenced Sybase client 10 and 12 using repackaged MSIs and not the vendor install. The only thing is that I had the luxury of the client already making a MSI out of the installs.
Answered 05/17/2007 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity