Hello All,

I am having some package/deployment issues with Crystal 10. I have created a package using a transform, entered the serial number and created a registration key. However, when the package is run with the transform (and just a regular install) it reboots the machine. This reboot does not happen all the time, and quite frankly I was wondering why it happens, and if it possible to supress it. After a reboot, the installation bombs out due to network drives not being connected. If the installation is then started again, it works properly with no reboot.

I have tried the package on a freshly ghosted machine and it worked fine with no reboot. I also tried it on a machine that had CR8.5 installed on it, and it worked fine. Any help would be greatly appreciated.

Thanks,
Dan
0 Comments   [ + ] Show Comments

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.

Answers

0
In your transform go to the Property table and add a field.

Reboot = ReallySuppress

Also look for any CR related reboot custom actions and remove them.
Answered 05/17/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
I added that in and I dont think it covered it. The problem is that I dont understand the conditions that cause the reboot. I did some searching and found this line in the "Install Sequence / Execute Sequence" in Wise for Windows while looking at the transform:

Action: ForceReboot
Sequence Number: 4470
Condition: 0 AND (((NeedReboot = "TRUE") OR ReplacedInUseFiles) AND (NOT AFTERREBOOT) AND (NOT Installed))

I checked on the initial condition of NeedReboot and it is set to false. I am fairly new to packages and what not, so where in the script/transform can I find where that changes?

Thanks.

Dan
Answered 06/01/2004 by: mackowia
Yellow Belt

Please log in to comment
0
Hello friends.

I am working in Crystal Reports 10 without MST, i am using properties. I am having deploymet issues with keycode.dll. I am using Unicenter Software Delivery.

P.D. Excuse me for my badly english.
Answered 07/03/2005 by: jperezg
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: mackowia

I added that in and I dont think it covered it. The problem is that I dont understand the conditions that cause the reboot. I did some searching and found this line in the "Install Sequence / Execute Sequence" in Wise for Windows while looking at the transform:

Action: ForceReboot
Sequence Number: 4470
Condition: 0 AND (((NeedReboot = "TRUE") OR ReplacedInUseFiles) AND (NOT AFTERREBOOT) AND (NOT Installed))

I checked on the initial condition of NeedReboot and it is set to false. I am fairly new to packages and what not, so where in the script/transform can I find where that changes?

Thanks.

Dan


Did u try excludingg the ForcReboot action from the Install Execute Seq table??. Also look for any other CAs that may be triggering a reboot (like, ScheduleReboot).
Answered 07/06/2005 by: sridtech
Senior Yellow Belt

Please log in to comment
0
Hi Mackowia,

Can you give the command line when executing the transform?

I can't remember the exact package from the vendor that I used a transform that also had a force reboot like you're saying. I remember adding Reboot=ReallySuppress and RebootYesNo=No in the commandline without success but when I tried adding a verbose log, it worked fine and finished the installation. Just want you to try it if this can also help you.. [;)]
Answered 07/06/2005 by: dj_xest
Fifth Degree Black Belt

Please log in to comment
0
Hej Mackowia,

If you have a Wise, open the msi package in Wise, On the left pane, Check Administration Options tab, there will be an option to reboot or not. By default that value is set to "Reboot if required", You can change that to Never Reboot.

I had though similar problem. I have deployed Adobe Acrobat Reader 7.0 to 30 pc's. 5 of them required reboot after the installation. Weird !

Regards,
Berke.
Answered 07/07/2005 by: Priapus
Orange Belt

Please log in to comment
0
The key here is this.

Condition: 0 AND (((NeedReboot = "TRUE") OR ReplacedInUseFiles) AND (NOT AFTERREBOOT) AND (NOT Installed))

The msi is detecting that it tried to replace in use files and then sets the condition to force a reboot.

You won't get this issue if you workstation deploy it. You might get it if the users install it themselves and have say Word open at the same time.
Answered 07/08/2005 by: MSIMaker
Second Degree Black Belt

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