Server 2003 R2 stuck on installing update

[Bedders]

Morning all,

 

So I need to expand a VHD on our primary SQL server, a virtual machine hosted on Hyper-V. I shut it down last night at 8:30pm and let it install the 18 updates it needs, and went to bed at 11:30pm with it installing update 11 of 18. This morning it is still installing the same update!

 

Our SQL database and shared drive hosted on that server appear to still be live.

 

Is there anything I can do to prevent this server from shutting down at an indeterminate time during the day, that won't cause data loss?

 

Thanks in advance (it's too early in the morning for for this!)

[free780]

Can you view Windowsupdate.log through the c$ share ?

 

I wouldn't force a restart on Server 2003.

Edited June 30, 2017 by free780

[Bedders]

Can you view Windowsupdate.log through the c$ share ?

 

I wouldn't force a restart on Server 2003.

 

Thanks for the help Free. Yes, I can see WindowsUpdate.log and I can view the event logs.

 

It looks like the last update complete successfully, but there's no call to start the next one.

 

The last update was Microsoft Silverlight. In the Event Log it shows the following as being the last msiInstaller log entry:

 

Event Type:    Information
Event Source:    MsiInstaller
Event Category:    None
Event ID:    1035
Date:        29/06/2017
Time:        20:49:35
User:        NT AUTHORITY\SYSTEM
Computer:    
Description:
Windows Installer reconfigured the product. Product Name: Microsoft Silverlight. Product Version: 5.1.40416.0. Product Language: 1033. Reconfiguration success or error status: 0.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 38 39 46 34 31 33 37   {89F4137
0008: 44 2d 36 43 32 36 2d 34   D-6C26-4
0010: 41 38 34 2d 42 44 42 38   A84-BDB8
0018: 2d 32 45 35 41 34 42 42   -2E5A4BB
0020: 37 31 45 30 30 7d         71E00}

 

The WindowsUpdate.Log file shows these entries:

 

2017-06-29    20:49:36:104     896    658    DnldMgr    Preparing update for install, updateId = {6FA27C4F-7654-4133-85AC-A21603E50768}.201.
2017-06-29    20:49:36:136    3932    1710    Handler    :::::::::::::
2017-06-29    20:49:36:136    3932    1710    Handler    :: START ::  Handler: Windows Patch Install
2017-06-29    20:49:36:136    3932    1710    Handler    :::::::::
2017-06-29    20:49:36:136    3932    1710    Handler      : Updates to install = 1
2017-06-29    20:49:36:136    3932    1710    Handler      : Installing update {6FA27C4F-7654-4133-85AC-A21603E50768}.201
2017-06-29    20:49:36:136    3932    1524    Handler    Installing with parameters=-q -z -er, sandbox=C:\WINDOWS\SoftwareDistribution\Download\4c8caebca645ebcd32d4b6aae5bfc88c.
2017-06-29    20:49:45:485    3932    1524    Handler    Install completed with 0x80070bc2.
2017-06-29    20:49:45:485    3932    1710    Handler      : Install completed: result type = 0x1, installer error = False, error = 0x80070bc2, disabled until reboot = No, reboot required = Yes
2017-06-29    20:49:45:485    3932    1710    Handler    :::::::::
2017-06-29    20:49:45:485    3932    1710    Handler    ::  END  ::  Handler: Windows Patch Install
2017-06-29    20:49:45:485    3932    1710    Handler    :::::::::::::
2017-06-29    20:49:45:532     896    1018    AU    >>##  RESUMED  ## AU: Installing update [updateId = {800AB899-CDE0-4E7E-9D49-751E356AB574}, succeeded]
2017-06-29    20:49:45:532     896    658    Report    REPORT EVENT: {9F4367BE-D6C2-4E55-8F30-9784C3FA43AA}    2017-06-29 20:49:45:532+0100    1    199    101    {800AB899-CDE0-4E7E-9D49-751E356AB574}    201    0    AutomaticUpdates
   Success    Content Install    Installation successful and restart required for the following update: Update for Windows Server 2003 (KB3020338)
2017-06-29    20:49:45:532     896    658    DnldMgr    Preparing update for install, updateId = {42E61FA7-4FCC-4A32-948E-8D3120670014}.100.
2017-06-29    20:49:45:783    3932    24c    Handler    :::::::::::::
2017-06-29    20:49:45:783    3932    24c    Handler    :: START ::  Handler: Command Line Install
2017-06-29    20:49:45:783    3932    24c    Handler    :::::::::
2017-06-29    20:49:45:783    3932    24c    Handler      : Updates to install = 1
2017-06-29    20:49:47:674    4192    1094    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: +0100)  ===========
2017-06-29    20:49:47:674    4192    1094    Misc      = Process: c:\3280f3bc55d411164441cc\update\iesetup.exe
2017-06-29    20:49:47:674    4192    1094    Misc      = Module: C:\WINDOWS\system32\wuapi.dll
2017-06-29    20:49:47:674    4192    1094    COMAPI    -------------
2017-06-29    20:49:47:674    4192    1094    COMAPI    -- START --  COMAPI: Search [ClientId = Windows Internet Explorer 8 Setup Utility]
2017-06-29    20:49:47:674    4192    1094    COMAPI    ---------
2017-06-29    20:49:47:690    4192    1094    COMAPI    <<-- SUBMITTED -- COMAPI: Search [ClientId = Windows Internet Explorer 8 Setup Utility]
2017-06-29    23:06:37:945     896    17a0    Agent      * Added update {9D460DA0-8983-4BB4-A839-DF88E5777488}.100 to search result
2017-06-29    23:06:37:945     896    17a0    Agent      * Added update {3ABE760C-4578-4C84-A1CB-BF1DF019EFE4}.100 to search result
2017-06-29    23:06:37:945     896    17a0    Agent      * Added update {596ADB47-108D-482D-85BA-A513621434B7}.100 to search result
2017-06-29    23:06:37:945     896    17a0    Agent      * Added update {7079BEEB-6120-4AFD-AD07-FB4DFA284FBE}.100 to search result
2017-06-29    23:06:37:945     896    17a0    Agent    Update {D9A1873D-B262-4943-9ACD-B4915CA81DEE}.200 is pruned out due to potential supersedence

 

There are more entries more recently, but they seem to be referring to checking for updates rather than installing them. Is there anything generally I should be looking for?

 

Many thanks

[AlanD]

Extended service support for 2003 R2 ended in 2015.

 

It would be difficult to justify (...and please don't "cost" as a justification) for keeping with 2003 R2. With successful ransomware attacks not uncommon in schools, and a requirement to meet Data protection criteria (if hosing SQL on it) you could be accused of a dereliction of duty and negligence (probably a sackable offence) for not taking reasonable precautions - and that would include using "supported" versions of software in my book.

[Bedders]

Extended service support for 2003 R2 ended in 2015.

 

It would be difficult to justify (...and please don't "cost" as a justification) for keeping with 2003 R2. With successful ransomware attacks not uncommon in schools, and a requirement to meet Data protection criteria (if hosing SQL on it) you could be accused of a dereliction of duty and negligence (probably a sackable offence) for not taking reasonable precautions - and that would include using "supported" versions of software in my book.

 

Hi AlanD,

 

Thanks for the warning - believe me I know! Although we are not a school, we do handle a lot of personal data, and running SQL 2000 on a Server 2003 R2 machine is not my idea of secure.

 

On the other hand we are currently investing in a migration process to SQL Server 2016 on a Server 2016 box, however the challenges of migrating all of this system (including heavily in-house customised software) over the the new version have proved problematic without continued support from management and the departments within our business.

[Bedders]

Ok so the server decided that 12:44 was a good time for it to finish and restart. Thankfully a fair number of people were on lunch, but still..... I guess it solved the problem. Once I switched it back on again.