Unable to logon to a Windows Server 2003 system.

[Edson da Silva]

Hello guys

I have a problem with a server in one of our remote sites. We normally
connect to this server using VNC. for the last two weeks we are unable to log
on into it, basically what's happening is that when you type your credentials
(Username/Password) the system attempts to log you on but instead of loading
the desktop, it takes you back to "press contrl Alt and Delete" window. All
network shares can be accessed without any problems, is just the fact that we
are unable to log on to the server that is presenting an issue. I have also
tried Remote Desktop and reboot the machine but didn't work either. I there
any way to solve this problem remotely (may be through the comand line)
without having to phisically repari the system installation.

Another question... is there any way to see/and or stop running services on
a remote system.

Thanks and regards

EDSON

 

[Pegasus \(MVP\)]

"Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in message
news:FEE6F376-7236-4889-9F8A-397ED5CC8457@microsoft.com...
> Hello guys
>
> I have a problem with a server in one of our remote sites. We normally
> connect to this server using VNC. for the last two weeks we are unable to
> log
> on into it, basically what's happening is that when you type your
> credentials
> (Username/Password) the system attempts to log you on but instead of
> loading
> the desktop, it takes you back to "press contrl Alt and Delete" window.
> All
> network shares can be accessed without any problems, is just the fact that
> we
> are unable to log on to the server that is presenting an issue. I have
> also
> tried Remote Desktop and reboot the machine but didn't work either. I
> there
> any way to solve this problem remotely (may be through the comand line)
> without having to phisically repari the system installation.
>
> Another question... is there any way to see/and or stop running services
> on
> a remote system.
>
> Thanks and regards
>
> EDSON

This usually happens when the file userinit.exe is not in its
expected place or if the file is corrupted. Its location is
shown here:
HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit

You should be able to examine the file by looking at C$
on the remote machine, and to check the registry entry
by opening the registry remotely. By running a Command
Prompt under psexec.exe (www.sysinternals.com), you
can check that the system drive letter is correct - it is in
most cases C:.

You can start/stop services with sc.exe, or with net start/stop
while running a Command Prompt remotely with psexec.exe.

 

[Edson da Silva]

Hello there....

I have located the Userinit.exe file, how do I know if it's corrupeted and
if so how do can we replace/ and or fix it?

Thanks Edson

"Pegasus (MVP)" wrote:

>
> "Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in message
> news:FEE6F376-7236-4889-9F8A-397ED5CC8457@microsoft.com...
> > Hello guys
> >
> > I have a problem with a server in one of our remote sites. We normally
> > connect to this server using VNC. for the last two weeks we are unable to
> > log
> > on into it, basically what's happening is that when you type your
> > credentials
> > (Username/Password) the system attempts to log you on but instead of
> > loading
> > the desktop, it takes you back to "press contrl Alt and Delete" window.
> > All
> > network shares can be accessed without any problems, is just the fact that
> > we
> > are unable to log on to the server that is presenting an issue. I have
> > also
> > tried Remote Desktop and reboot the machine but didn't work either. I
> > there
> > any way to solve this problem remotely (may be through the comand line)
> > without having to phisically repari the system installation.
> >
> > Another question... is there any way to see/and or stop running services
> > on
> > a remote system.
> >
> > Thanks and regards
> >
> > EDSON
>
> This usually happens when the file userinit.exe is not in its
> expected place or if the file is corrupted. Its location is
> shown here:
> HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit
>
> You should be able to examine the file by looking at C$
> on the remote machine, and to check the registry entry
> by opening the registry remotely. By running a Command
> Prompt under psexec.exe (www.sysinternals.com), you
> can check that the system drive letter is correct - it is in
> most cases C:.
>
> You can start/stop services with sc.exe, or with net start/stop
> while running a Command Prompt remotely with psexec.exe.
>
>
>

 

[Pegasus \(MVP\)]

Simple: Compare it with userinit.exe from a different
machine or with the version from your installation CD.

Don't forget to check the other items I mention in my
first reply. They must ALL be correct!


"Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in message
news:15E6149A-AF0B-4B5B-BCC8-0A875B710D02@microsoft.com...
> Hello there....
>
> I have located the Userinit.exe file, how do I know if it's corrupeted and
> if so how do can we replace/ and or fix it?
>
> Thanks Edson
>
> "Pegasus (MVP)" wrote:
>
>>
>> "Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in
>> message
>> news:FEE6F376-7236-4889-9F8A-397ED5CC8457@microsoft.com...
>> > Hello guys
>> >
>> > I have a problem with a server in one of our remote sites. We normally
>> > connect to this server using VNC. for the last two weeks we are unable
>> > to
>> > log
>> > on into it, basically what's happening is that when you type your
>> > credentials
>> > (Username/Password) the system attempts to log you on but instead of
>> > loading
>> > the desktop, it takes you back to "press contrl Alt and Delete" window.
>> > All
>> > network shares can be accessed without any problems, is just the fact
>> > that
>> > we
>> > are unable to log on to the server that is presenting an issue. I have
>> > also
>> > tried Remote Desktop and reboot the machine but didn't work either. I
>> > there
>> > any way to solve this problem remotely (may be through the comand line)
>> > without having to phisically repari the system installation.
>> >
>> > Another question... is there any way to see/and or stop running
>> > services
>> > on
>> > a remote system.
>> >
>> > Thanks and regards
>> >
>> > EDSON
>>
>> This usually happens when the file userinit.exe is not in its
>> expected place or if the file is corrupted. Its location is
>> shown here:
>> HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit
>>
>> You should be able to examine the file by looking at C$
>> on the remote machine, and to check the registry entry
>> by opening the registry remotely. By running a Command
>> Prompt under psexec.exe (www.sysinternals.com), you
>> can check that the system drive letter is correct - it is in
>> most cases C:.
>>
>> You can start/stop services with sc.exe, or with net start/stop
>> while running a Command Prompt remotely with psexec.exe.
>>
>>
>>

 

[Edson da Silva]

Hello again..Thanks for your time here...
Now can I simply copy the good files from the CD or from one of the good
systems in order to replace the corrupted ones and see if this issue gets
addressed.

Regards

EDSON


"Pegasus (MVP)" wrote:

> Simple: Compare it with userinit.exe from a different
> machine or with the version from your installation CD.
>
> Don't forget to check the other items I mention in my
> first reply. They must ALL be correct!
>
>
> "Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in message
> news:15E6149A-AF0B-4B5B-BCC8-0A875B710D02@microsoft.com...
> > Hello there....
> >
> > I have located the Userinit.exe file, how do I know if it's corrupeted and
> > if so how do can we replace/ and or fix it?
> >
> > Thanks Edson
> >
> > "Pegasus (MVP)" wrote:
> >
> >>
> >> "Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in
> >> message
> >> news:FEE6F376-7236-4889-9F8A-397ED5CC8457@microsoft.com...
> >> > Hello guys
> >> >
> >> > I have a problem with a server in one of our remote sites. We normally
> >> > connect to this server using VNC. for the last two weeks we are unable
> >> > to
> >> > log
> >> > on into it, basically what's happening is that when you type your
> >> > credentials
> >> > (Username/Password) the system attempts to log you on but instead of
> >> > loading
> >> > the desktop, it takes you back to "press contrl Alt and Delete" window.
> >> > All
> >> > network shares can be accessed without any problems, is just the fact
> >> > that
> >> > we
> >> > are unable to log on to the server that is presenting an issue. I have
> >> > also
> >> > tried Remote Desktop and reboot the machine but didn't work either. I
> >> > there
> >> > any way to solve this problem remotely (may be through the comand line)
> >> > without having to phisically repari the system installation.
> >> >
> >> > Another question... is there any way to see/and or stop running
> >> > services
> >> > on
> >> > a remote system.
> >> >
> >> > Thanks and regards
> >> >
> >> > EDSON
> >>
> >> This usually happens when the file userinit.exe is not in its
> >> expected place or if the file is corrupted. Its location is
> >> shown here:
> >> HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit
> >>
> >> You should be able to examine the file by looking at C$
> >> on the remote machine, and to check the registry entry
> >> by opening the registry remotely. By running a Command
> >> Prompt under psexec.exe (www.sysinternals.com), you
> >> can check that the system drive letter is correct - it is in
> >> most cases C:.
> >>
> >> You can start/stop services with sc.exe, or with net start/stop
> >> while running a Command Prompt remotely with psexec.exe.
> >>
> >>
> >>
>
>
>

 

[Edson da Silva]

Would I be OK if I simply copy one of the non-corrupted to replace the
corrupted ones..?

Regards

EDSON

"Edson da Silva" wrote:

>
> Hello again..Thanks for your time here...
> Now can I simply copy the good files from the CD or from one of the good
> systems in order to replace the corrupted ones and see if this issue gets
> addressed.
>
> Regards
>
> EDSON
>
>
> "Pegasus (MVP)" wrote:
>
> > Simple: Compare it with userinit.exe from a different
> > machine or with the version from your installation CD.
> >
> > Don't forget to check the other items I mention in my
> > first reply. They must ALL be correct!
> >
> >
> > "Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in message
> > news:15E6149A-AF0B-4B5B-BCC8-0A875B710D02@microsoft.com...
> > > Hello there....
> > >
> > > I have located the Userinit.exe file, how do I know if it's corrupeted and
> > > if so how do can we replace/ and or fix it?
> > >
> > > Thanks Edson
> > >
> > > "Pegasus (MVP)" wrote:
> > >
> > >>
> > >> "Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in
> > >> message
> > >> news:FEE6F376-7236-4889-9F8A-397ED5CC8457@microsoft.com...
> > >> > Hello guys
> > >> >
> > >> > I have a problem with a server in one of our remote sites. We normally
> > >> > connect to this server using VNC. for the last two weeks we are unable
> > >> > to
> > >> > log
> > >> > on into it, basically what's happening is that when you type your
> > >> > credentials
> > >> > (Username/Password) the system attempts to log you on but instead of
> > >> > loading
> > >> > the desktop, it takes you back to "press contrl Alt and Delete" window.
> > >> > All
> > >> > network shares can be accessed without any problems, is just the fact
> > >> > that
> > >> > we
> > >> > are unable to log on to the server that is presenting an issue. I have
> > >> > also
> > >> > tried Remote Desktop and reboot the machine but didn't work either. I
> > >> > there
> > >> > any way to solve this problem remotely (may be through the comand line)
> > >> > without having to phisically repari the system installation.
> > >> >
> > >> > Another question... is there any way to see/and or stop running
> > >> > services
> > >> > on
> > >> > a remote system.
> > >> >
> > >> > Thanks and regards
> > >> >
> > >> > EDSON
> > >>
> > >> This usually happens when the file userinit.exe is not in its
> > >> expected place or if the file is corrupted. Its location is
> > >> shown here:
> > >> HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit
> > >>
> > >> You should be able to examine the file by looking at C$
> > >> on the remote machine, and to check the registry entry
> > >> by opening the registry remotely. By running a Command
> > >> Prompt under psexec.exe (www.sysinternals.com), you
> > >> can check that the system drive letter is correct - it is in
> > >> most cases C:.
> > >>
> > >> You can start/stop services with sc.exe, or with net start/stop
> > >> while running a Command Prompt remotely with psexec.exe.
> > >>
> > >>
> > >>
> >
> >
> >

 

[Pegasus \(MVP\)]

I will spell it out for you in detail:
1. The file userinit.exe must exist.
2. It must be in the location indicated by this registry key.
HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit
3. It must be intact.
4. If you think that it may be corrupted then you can
replace it with its original from your CD. Make sure to
keep the original!
5. The system drive letter must be C: (unless you have a
totally non-standard installation).
6. You can check the system drive letter with a Command
Prompt that you run on the problem server, using
psexec.exe.
If the above instructions make no sense then I recommend
that you ask an experienced server administrator to assist you.


"Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in message
news:63A46CBD-5685-4ECA-89ED-DC744577B80A@microsoft.com...
>
> Hello again..Thanks for your time here...
> Now can I simply copy the good files from the CD or from one of the good
> systems in order to replace the corrupted ones and see if this issue gets
> addressed.
>
> Regards
>
> EDSON
>
>
> "Pegasus (MVP)" wrote:
>
>> Simple: Compare it with userinit.exe from a different
>> machine or with the version from your installation CD.
>>
>> Don't forget to check the other items I mention in my
>> first reply. They must ALL be correct!
>>
>>
>> "Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in
>> message
>> news:15E6149A-AF0B-4B5B-BCC8-0A875B710D02@microsoft.com...
>> > Hello there....
>> >
>> > I have located the Userinit.exe file, how do I know if it's corrupeted
>> > and
>> > if so how do can we replace/ and or fix it?
>> >
>> > Thanks Edson
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >>
>> >> "Edson da Silva" <EdsondaSilva@discussions.microsoft.com> wrote in
>> >> message
>> >> news:FEE6F376-7236-4889-9F8A-397ED5CC8457@microsoft.com...
>> >> > Hello guys
>> >> >
>> >> > I have a problem with a server in one of our remote sites. We
>> >> > normally
>> >> > connect to this server using VNC. for the last two weeks we are
>> >> > unable
>> >> > to
>> >> > log
>> >> > on into it, basically what's happening is that when you type your
>> >> > credentials
>> >> > (Username/Password) the system attempts to log you on but instead of
>> >> > loading
>> >> > the desktop, it takes you back to "press contrl Alt and Delete"
>> >> > window.
>> >> > All
>> >> > network shares can be accessed without any problems, is just the
>> >> > fact
>> >> > that
>> >> > we
>> >> > are unable to log on to the server that is presenting an issue. I
>> >> > have
>> >> > also
>> >> > tried Remote Desktop and reboot the machine but didn't work either.
>> >> > I
>> >> > there
>> >> > any way to solve this problem remotely (may be through the comand
>> >> > line)
>> >> > without having to phisically repari the system installation.
>> >> >
>> >> > Another question... is there any way to see/and or stop running
>> >> > services
>> >> > on
>> >> > a remote system.
>> >> >
>> >> > Thanks and regards
>> >> >
>> >> > EDSON
>> >>
>> >> This usually happens when the file userinit.exe is not in its
>> >> expected place or if the file is corrupted. Its location is
>> >> shown here:
>> >> HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit
>> >>
>> >> You should be able to examine the file by looking at C$
>> >> on the remote machine, and to check the registry entry
>> >> by opening the registry remotely. By running a Command
>> >> Prompt under psexec.exe (www.sysinternals.com), you
>> >> can check that the system drive letter is correct - it is in
>> >> most cases C:.
>> >>
>> >> You can start/stop services with sc.exe, or with net start/stop
>> >> while running a Command Prompt remotely with psexec.exe.
>> >>
>> >>
>> >>
>>
>>
>>

 

[Olaf Engelke [MVP Windows Server]]

Hello,
Edson da Silva wrote:
> I have a problem with a server in one of our remote sites. We normally
> connect to this server using VNC. for the last two weeks we are
> unable to log on into it, basically what's happening is that when you
> type your credentials (Username/Password) the system attempts to log
> you on but instead of loading the desktop, it takes you back to
> "press contrl Alt and Delete" window. All network shares can be
> accessed without any problems, is just the fact that we are unable to
> log on to the server that is presenting an issue. I have also tried
> Remote Desktop and reboot the machine but didn't work either. I there
> any way to solve this problem remotely (may be through the comand
> line) without having to phisically repari the system installation.
>
did you reboot the machine or only try it?
Often it helps in such cases, to call a user on site, have him shut down the
server (with power button, if necessary also the hard way) and power on
after a few seconds.
Best greetings from Germany
Olaf