Member Avatar for Kurtismonger

I have a PDC Server running Windows Server 2003 that was on SP1. The server was low on disk space, but I was able to clear enough were SP2 indicated that it could be installed. Unfortunately half way through, it ran out of space and quit. When I tried to uninstall SP2 via Add/Remove the server crashed and now is not booting.

When I attempt boot it shows the Windows Server logo and progress bar for a few minutes and then BSODs with a Non-DLL error.

As this is my domain controller my whole network is out. Is there anything I can do to get into the system and back out of SP2? I'm in dire need of some help here ASAP.

If it matters it's running on a HP ML330 server

  • 1 Contributor
  • 1 Reply
  • 221 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Kurtismonger

Dani AI

Generated

Useful follow-up notes and checks to complement ’s recovery (storage/driver problems after a partial Service Pack install are a common root cause):

  • Narrow the fault first: boot with “Enable Boot Logging” (F8) and inspect C:\Windows\ntbtlog.txt for drivers that failed to load. That file quickly shows which storage or critical drivers never initialized. Also try Safe Mode / Last Known Good to see whether the kernel can start with a reduced driver set. From WinPE/Recovery Console run a filesystem check (chkdsk) to correct corrupt entries that a failed update may have left behind.

  • If repair or rebuild becomes necessary, protect Active Directory before drastic steps. Make and verify a System State backup if possible. After recovery, validate AD health with:

    dcdiag /v
repadmin /replsummary
netdom query fsmo

    Address any SYSVOL/replication issues before declaring the DC healthy. Use an authoritative System State restore only if you understand the replication consequences — it forces the restored data to replicate to partners and can overwrite newer objects.

  • Prevention and tooling: keep ample free space before major updates, maintain at least one additional DC, and keep recent System State backups. Create recovery media (WinPE/BartPE/ERD) that include your vendor’s storage drivers so you can access arrays without relying on floppy-based F6 methods. Consider slipstreaming service packs into installation media for safer offline repairs in the future.

Caution: if you must rebuild and the old DC won’t come back, make sure FSMO roles are transferred or seized on a surviving DC; poorly handled role changes and rushed authoritative restores are the usual source of long-term AD problems.

Member Avatar for Kurtismonger

In case anyone else has a similar problem, here is the solution:
Because this server had a RAID controller I first had to make a floppy disk with the driver. This was done using the HP SmartController CD. I then booted using the OS disk, pressed F6 to add third party drivers and did a install repair once the install program found the previous install of Windows Server. Initially I had trouble because Windows kept saying it had the proper RAID drivers, but I finally told it to use the one's I supplied and it worked.
After that it was just a matter of letting Windows go through the install/repair process. Amazingly after a few reboots 2003 booted fine and appears to have reverted to SP1 or at least replaced the SP2 files that were causing the problem. Active Directory and all other settings were still intact.

Edited by Kurtismonger because: n/a
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.