Re: A Very Sick W2K Server
- From: "George Hester" <hesterloli@xxxxxxxxxxx>
- Date: Sun, 7 Aug 2005 20:12:03 -0400
You blue-screened making an ERD? Hmph. Did you ever have an indication prior to this that things weren't right? What did the Event Viewer say about the crash? Were you able to jot down the first line of data in the blue-screen? Immediately after the blue screen and a reboot what happened next assuming that is what you tried to do after the blue-screen?
--
George Hester
_______________________________
"DanaK" <DanaK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:661B0A8E-B522-4EEA-8CCB-0D636DF4BA6F@xxxxxxxxxxxxxxxx
> On Monday my DC crashed at the office (W2K Server, s.p. 4). It blue screened
> while attempting to make an ERD for the another server I manage. This had the
> effect of going through part of my server's OS like a mix-master. I'd LOVE to
> blame Symantec for this but it may very well be that Symantec Corporate
> Antivirus v. 10 may be just as much a victim in this little scenario as W2K
> Server is so right now I'm just going to chalk it up to a hardware failure
> with my floppy drive and leave it at that.
>
> Yesterday I tried to perform a repair installation with a W2K OS disk that
> had service pack 3 on it. The first round took about 30 minutes to inspect my
> drive then another 30 minutes to scan the drive and then it told me to
> reboot. I think it indicated that it had fixed some things also. It didn't
> say reboot to the desktop so I rebooted to the CD and went back to the repair
> function and did another Fast Repair. This time it took over an hour plus to
> get through the inspecting and scanning and then began checking all of my
> system files but never asked me to replace any of them .... UNTIL ... it said
> that a repair was not possible on this drive and told me to hit F3 and get
> out. (This was NOT the CD I used to originally install W2K Server. The
> original CD had no service packs on it. Since the OS had s.p. 4 on it I
> thought an install CD with the closest thing to my original OS would be
> best.) So, with no other place to go I rebooted to see if anything would come
> up at all and it DID, eventually, get back to a login prompt and then, after
> another 15 to 20 minutes, the desktop. It seemed to work a bit better also.
>
> The last thing I did, however, was to attempt to re-apply service pack 4 in
> the belief that it would replace any possibly bad files left over but after
> leaving it alone for well over three hours (It's an dual 800Mhz Dell box so
> you've got to give it time) I came back to find that it never got beyond the
> window that said "Inspecting your system" so I closed the s.p. update.
>
> Looking farther into this problem I find that Windows Installer is not
> starting due to RPC, which it depends on, not being up and I can not Start
> the RPC service (I'm currently looking at article 838428 in Microsoft's KB).
> Has anyone had any experience in restoring the RPC service or do I need to
> follow the thread of dependencies farther back down the line? When I looked
> at the dependencies tab on RPC it didn't list anything except what depended
> on RPC. Without Windows Installer I can't uninstall Symantec CAV which could
> quite possibly release the server from a host of problems.
>
> Unfortunately, this morning the server will not boot to the desktop even
> though I can bring up Task Manager AND my workstation can log in and view the
> files on its two mapped drives on the server. Safe Mode is my next avenue of
> attack on this but if anyone could give me some suggestions on how otherwise
> to proceed I'm all ears.
>
> Thanks in advance.
.
- Follow-Ups:
- Re: A Very Sick W2K Server
- From: DanaK
- Re: A Very Sick W2K Server
- References:
- A Very Sick W2K Server
- From: DanaK
- A Very Sick W2K Server
- Prev by Date: Re: Win2000 Problem with Broadband Internet
- Next by Date: Re: JPEG files
- Previous by thread: A Very Sick W2K Server
- Next by thread: Re: A Very Sick W2K Server
- Index(es):
Relevant Pages
|
