cancel
Showing results for 
Search instead for 
Did you mean: 

Server restart mid Install for Backup Exec 12.5

TrevorCooper
Level 1
I am mid way through a rollout program for Backup Exec 12.5.  After 10 servers I had experienced no problems, then suddenly the last 2 servers have both restarted themselves midway through the install.  I was watching the 2nd one closely and it was whilst it was finalizing but before it got to installing the remote agents I had selected.

The install suddenly closed along with all other windows, I was logged off and then briefly saw "Windows is shutting down" before my remote control session disconnected.

Looking through event viewer I found the below messages indicating the restart was caused by a patch for MS SQL Server 2005.  Looking through the event viewer for one of the other servers this patch was installed but did not cause the server to restart.  Can you please explain why this has happened.

Event Type: Information
Event Source: USER32
Event Category: None
Event ID: 1074
Date: 2009/09/08
Time: 03:52:48 PM
User: NT AUTHORITY\SYSTEM
Computer: JHBSRV01
Description:
The process msiexec.exe has initiated the restart of computer JHBSRV01 on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
Reason Code: 0x80030002
Shutdown Type: restart
Comment: The Windows Installer initiated a system restart to complete or continue the configuration of 'Microsoft SQL Server 2005 Backward compatibility'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 02 00 03 80 ...€

 
Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 1005
Date: 2009/09/08
Time: 03:52:48 PM
User: TTGROUP\admintc
Computer: JHBSRV01
Description:
The Windows Installer initiated a system restart to complete or continue the configuration of 'Microsoft SQL Server 2005 Backward compatibility'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 31 32 35 30 38 46 42 {12508FB
0008: 32 2d 38 39 45 43 2d 34 2-89EC-4
0010: 42 45 36 2d 42 35 46 37 BE6-B5F7
0018: 2d 36 34 34 45 38 46 39 -644E8F9
0020: 35 41 46 37 42 7d 5AF7B}
1 REPLY 1

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

This has been seen at least once against a version of MOM holding a file open that cause s the Backward Compatibility installer to request the reboot.

If you look in
C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\SQLServer2005_BC.log

you might find an entry similar to

MSI (s) (2C:84) [11:42:43:111]: 1 application(s) had been reported to have files in use.
Info 1603.The file C:\Program Files\Microsoft SQL Server\80\Tools\binn\SQLDMO.DLL is being held in use by the following process: Name: MOMHost, Id: 3096, Window Title: '(not determined yet)'. Close that application and retry.
MSI (84:9C) [11:42:43:111]: File In Use: -MOMHost- Window could not be found. Process ID: 3096

Which should help you identify the systems in your environment that might cause the reboot so that you can disable the services prior to attempting the install/upgrade or at least warn you in advance so you can perform the upgrade in a reboot window.