Really really really NOT happy with MS Server 2003 update...

Discussion in 'Windows Server' started by Rob R. Ainscough, Apr 15, 2005.

  1. I'm doing my best NOT to explode as I've reached my limits with MS

    The situation -- running Win2K3 Server with SQL Server 2000 -- auto updates
    are enabled. It prompted me to update, so I proceed to update -- tells me
    to restart, so I restart ... yes you guessed it...

    the PC now is stuck in a cycle of reboots, gets to the Windows 2003 Server
    screen with the moving progress bar, then about 5 seconds into that system
    reboots -- keeps this cycle going forever and ever.

    I was I could say there was some other variable at play, but the fact is
    this PC has been rock solid for a long time and this recent update has
    essentially turned it into a large pile of useless metal and plastic.

    To say I'm upset or frustrated at Microsoft's Update would be mild -- I
    guess it is very good that I don't live close to Redmond right now as I'm
    very much in the mood to clear several city blocks into rubble.

    Does Win2K3 have a "safe mode" -- if so, how do I get to that mode?
    Rob R. Ainscough, Apr 15, 2005
    1. Advertisements

  2. Rob R. Ainscough

    Matt Gibson Guest

    NEVER have automatic updates enabled on a server.

    There's a reason you test patches (or wait for them to be tested) before you
    install them.

    You've hung yourself here, not Microsoft.

    Matt Gibson - GSEC
    Matt Gibson, Apr 15, 2005
    1. Advertisements

  3. Rob R. Ainscough

    Ron Woods Guest

    Yes, Server 2003 does have a "safe mode" exactly like XP. When booting, as
    the progress bar begins to creep across the bottom of the screen, hit the F8
    key and then boot into "safe mode". If you are able to get in, you should be
    able to ununstall and updates that have installed including SP1 if that is
    what was installed. Give it a shot, you have nothing to loose at this point

    Ron Woods, Apr 15, 2005
  4. Matt,

    This is not our production SQL server, but none the less -- a certified MS
    patch should not prevent a PC from booting -- not every update is good and
    I'm well aware of that as I've had many years of experience with the
    wonderful world of hack it out and resolve it later, but an update should
    NEVER render a server useless -- that should be caught in their internal

    And it takes A LOT of time and effort to bring a test Server back to life --
    had this been a production server, you'd have seen me on the 6 o'clock news
    being arrested in front of what was once Redmond.

    Rob R. Ainscough, Apr 15, 2005
  5. F8 doesn't appear to work -- onto wasting more time with a repair boot CD

    thanks for the suggestion, Rob.
    Rob R. Ainscough, Apr 15, 2005
  6. Rob R. Ainscough

    Kerry Brown Guest

    Is the server a Dell? They have some problems they are addressing. If it is
    a Dell contact Dell support for an update.

    Kerry Brown, Apr 15, 2005
  7. No Dell, it is a standard PC, nothing special as it is for a test

    Like I said, the only variable involved is installing the MS Update &
    rebooting. The system has been rock solid for many many months until this
    new update. I sure hope someone in Redmond tested this new update to Win2K3
    with MS SQL server 2000 running on it -- it sure seems like they didn't.

    I'm going to replace the power supply as that is the only other time I've
    seen any PC's do this - but I'm grasping at straws as I don't see how an
    update to an OS could somehow cause excessive PS loading.

    Rob R. Ainscough, Apr 16, 2005
  8. I installed sp1 on a server with ms sql 2000 with no issues.
    Kevin Longley, Apr 16, 2005
  9. Rob R. Ainscough

    CyberDroog Guest

    Important tips:

    Never apply patches upon first being notified of them. Let the people who
    will never follow this advice test them first. Make a note of all
    suggested patches and investigate them for at least a few weeks first.

    Make a note of the details of any security updates. You can usually guard
    against the identified threat by others means until you have verified that
    the updates aren't causing problems for others.

    When it comes time to apply the updates, always make an image of the system
    drive before installing them.

    I know how you feel, but it really is impossible for Microsoft to test
    every single possibility. Given that, you have to cover your ass before
    fiddling with the system.

    Of course you are where you are so none of this helps now. What might help
    is ERD Commander (
    CyberDroog, Apr 16, 2005
  10. Adding to Terry's tips:

    1. Always install the Recovery Console or otherwise modify boot.ini on a
    Windows Server 2003 machine so that you will have a start-up menu. If you
    don't do this, getting F8 to work can be very difficult. Without the
    start-up menu, you have to repeatedly stab the F8 key and hope your timing
    is lucky - just holding it down usually will not work.

    2. Every update or service pack creates an $NTUnistallKB<number> or
    $NTServicePackUninstall folder. If you cannot start in Safe Mode, boot from
    the CD and run the Recovery Console. You should be able to uninstall the
    update or service pack by finding the correct $NT* folder in C:\Windows and
    running spuninst.bat.

    For an example, see:;en-us;825062

    Doug Sherman
    Doug Sherman [MVP], Apr 16, 2005
  11. Doug,

    Thanks, I'm not a sys Admin, I'm a developer using a test SQL server -- so I
    don't do the work of a sys admin as I focus on developing applications. MS
    patches should at least pass a minimal level of testing -- it seems these
    days that testing is being farmed out to foreign countries and then pushed
    out the door. The PC I'm working with is using ALL WHQ certified drivers.

    Doug -- did you used to work for BofA -- your name sounds familiar.

    But thanks for your suggestion -- recovery console will be my next step.
    Rob R. Ainscough, Apr 17, 2005
  12. Nope - never worked for B of A - obviously their loss :)

    Once you install the Recovery Console, you will get a startup menu allowing
    you to select either Windows Server 2003 or RC as a startup option. You can
    adjust how long this menu is displayed - default is 30 sec. If no selection
    is made within the alotted time, the system will start the default
    selection - Windows 2003.

    A side benefit of the above, is that you can manually select Windows Server
    2003 by highlighting it and hitting the ENTER key - you can then immediately
    hit F8, and you know that your timing is pretty good if you are trying to
    invoke the Safe Mode, etc. options. Without the side benefit of a startup
    menu, all you can do is hit the start button, repeatedly hit F8; and hope
    you get lucky.

    Obviously there are other benefits to having Recovery Console installed on
    your machine. If necessary, you can still access the Recovery Console by
    booting to the CD and selecting the Repair option.

    Doug Sherman
    Doug Sherman [MVP], Apr 17, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.