Re: Can't see logon window (and a lot more)

Kevin,
No we aren't running apc 6.
I didn't think to try access services or the event viewer remotely. I'll
definitely give that a whirl when I revisit that site (Monday).
Thanks for the ideas.
Jim

"Kevin Longley" <kwlongley@xxxxxxxxxxxxxx> wrote in message
news:OoTAqOTnFHA.1048@xxxxxxxxxxxxxxxxxxxxxxx
> Can you access the event viewer remotely and examine its contents? Can you
> access services remotely and examine there status? Wouldn't happen to be
> running apc version 6 software on it?
> "Jim Pattison" <jpattisonrem@xxxxxxxxxxxxxxx> wrote in message
> news:OyD9hITnFHA.2904@xxxxxxxxxxxxxxxxxxxxxxx
>> Kevin
>> Thanks for the response.
>> We tried botting in safe mode (no network) and inVGA mode. Both came up
>> the same as the normal boot up, mostly black screen. I don't remember
>> the settings on the page file. The only thing I can think of that fills
>> it up is some sort of tempory files associated with active directory.
>> Besides being a domain controller, a dhcp server, and a print server for
>> three or four printers, this server is currently doing much
>> Jim
>>
>> "Kevin Longley" <kwlongley@xxxxxxxxxxxxxx> wrote in message
>> news:%23dEpvCTnFHA.3288@xxxxxxxxxxxxxxxxxxxxxxx
>>> Can you boot up in safe mode and then examine the C drive for amount of
>>> disk space left? What are you running on this server that would use up
>>> disk space as you described it? How do you have the page file set up for
>>> starting and ending size (typically you make both values the same)?
>>> "Jim Pattison" <jpattisonrem@xxxxxxxxxxxxxxx> wrote in message
>>> news:O4RnZ2SnFHA.2916@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Setup: W2K3 standard with SP1 running on a Dell 2400, 1ghz processor,
>>>> 512 mb RAM, RAID 5 with a container of roughly 180 gig, partioned into
>>>> a C (for system only) and a D for storage. C partion is relatively
>>>> small (about 5 gig I think)
>>>>
>>>> Current Problem: all we can see is the upper part of the normal logon
>>>> screen (after CTRL-ALT-DEL). the rest of the screen is black.
>>>>
>>>> Prior to rebooting, we had a normal looking login screen however when
>>>> we logged in we go a message that said (as best as I can remember it)
>>>> that Windows was unable to load our profile (domain administrator) and
>>>> was using the default profile instead because there wasn't enough room
>>>> on the drive. After that message went away we had a black screen with
>>>> icons on it. If you clicked on the start button you would see the
>>>> icons from the start menu but no words. If you clicked on the icon for
>>>> my computer you wouuld see the icons along the left side and across the
>>>> top but nothing else. If you right click on my computer you can't see
>>>> the dialog box. If you launched Internet Explorer you would get the
>>>> white screen that has the verbiage about enhanced security and the
>>>> icons across the top but nothing else. If you clicked on shutdown
>>>> you'd get the iupper part of the normal shutdown dialog and two icons
>>>> that are the new update icon (yellow shield). We figured an update was
>>>> in progress and left it along for 4 hours. Came back and there was no
>>>> change so we forced a reboot (powered it off). Came back in it's
>>>> current configuration.
>>>>
>>>> Other Observations: If you log on remotely (remote desktop) you see the
>>>> exact same thing. If you open a share, the share opens but slowly.
>>>> One of the roles of this server is DHCP and, at least prior to
>>>> rebooting, it was working properly. It is also the primary domain
>>>> controller. Our other domain controller reports that it hasn't been
>>>> able to back up properly because it can't contact this domain
>>>> controller. In the past we have had problems with this server filling
>>>> up the C drive so we moved the paging file to the D drive. A couple of
>>>> weeks ago we discovered that the paging file had moved itself back to
>>>> the C drive and was once again filling the C drive. It was moved back
>>>> to D. An update was installed but we didn't check to see if the paging
>>>> file stayed where we put it. We assume that the paging file has moved
>>>> back and is causing the symptoms we see but can't figure out how to fix
>>>> it. Other assumptions: we assume it isn't the video card as the
>>>> display looks the same on a remote computer, plus we booted it off a CD
>>>> and could see everything.
>>>>
>>>> Sorry to be long winded but figured it would be best to describe this
>>>> in some detail.
>>>>
>>>> Anyone have any ides?
>>>>
>>>> thanks
>>>>
>>>> Jim Pattison
>>>>
>>>
>>>
>>
>>
>
>


.