Re: SBS LOGIN FREEZE, HELP!

You don't need to log in to the server to use Computer Management - just
open it on your desktop PC, and connect to the server from the r-click menu
on the top item in the console.

But don't rule out SuperGumby's excellent advice to call Microsoft support.

"Subhas" <Subhas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2F7002F0-D24E-465D-A5C1-67EAD1245DA5@xxxxxxxxxxxxxxxx
Thanks for your quick responses.

I wish I could get to that point, however I am unable to log into the
machien from either remotely OR locally, it just passes the login dialog
and
it freezes there. It just shows my wallpaper and that is it, I cannot do
anything else. If I hit CTRL+ALT+DEL I can only click the shutdown button,
all other buttons don't do anything.



"Dave Nickason [SBS MVP]" wrote:

This is what I would do. Locally if possible, but definitely from within
the building (you may end up losing remote access in this process, so you
won't want to be working from home). If you can log into the server
locally
and access Computer Management, do it there. If not, you can do it from
your desktop by r-clicking the top level in Computer Management and
connecting to the SBS. In Services, change the startup type for all 3rd
party (non-Microsoft) services to Disabled. You might want to pop out
the
ethernet cable for your Internet connection since your AV will be down,
and
you'll need a domain admin account to change startup properties. Note
the
services you change so you can undo it after.

Now restart the server and see what happens. If you're doing this
remotely,
on your desktop click Start -> Run -> shutdown -i. That'll give you a
GUI
interface you can use to reboot the SBS remotely.

When the server comes back up, see if you have normal access. If not,
again
open Computer Management either remotely or locally and look at the event
logs. Any services that failed to start should have logged information
for
troubleshooting purposes. If you can log in normally, change the startup
settings and restart the 3rd party services one at a time. If you have a
service that's causing a problem, this should let you determine which one
it
is, and you can troubleshoot from there.

At the point you can get into the server normally, you'll want to run MU
to
make sure the server has all patches installed. I'd note the ones you're
installing before starting the download/installation, and watch the whole
process to make sure all the installs succeed. Then reboot whether the
patch installer asks you to or not.


"Subhas" <Subhas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:80BCE576-4391-42A4-819A-E92C86522B67@xxxxxxxxxxxxxxxx
Hi, this is my 3rd time posting this question because the first 2
became
old
and not too much activity. I know the situation is odd and difficult to
troubleshoot, but all suggestions would be appreciated. As I have been
locked
out of my SBS box for over 2 weeks now, and we have a new employee & PC
coming in soon, and I would be unable to setup that user's account
without
access to the SBS. Ok to the heart of the problem, I have provided more
information regarding recent attempts.

We run windows server 2003 SBS which acts as our all in one server. We
recently installed several security patches via windows update. Shortly
after
completing the updates an explorer.exe error occured. It did not allow
the
launch
of any program after that. I was connected to the machine via remote
desktop
connection. So i figured I would just log off and log back in, this is
all
done with administrator account by the way. After I logged off and
tried
to
log back in it went through the usual (loading settings...applying
settings/policies, etc) once that dialog went away it refused to load
my
desktop and anything else, and it just frooze there. I closed the
session
and
tried and again but it stayed at the same spot. So I came in the office
to
see it first hand, only to get the same response. I then rebooted the
machine
and it gave an error after displaying the login box "At lease one
service
or driver failed during system startup. Use event viewer to examine the
event
log for details" Im not sure if this always showed up or not, because I
havn't rebooted the machine since September. After I click OK and I
login,
it shows two errors.
Title: Explorer.exe -Application error
the application failed to initalize proerply (0xc01500002). Click ok to
terminate application."

&

"title: RUNDLL
A dynamic link library (DLL) initalization routine failed."

If I click OK on both, it just shows me by wallpaper and nothing else,
I
can
ctrl+alt+del to ONLY shutdown, nothing else works (task manager, log
off,
nothing), it just doesn't do anything. I tried going into safemode,
however
it behaves the same with the same errors. I've restarted the machine
several
times now trying to get it to work. I cannot load task manager after
logon
to
run explorer.exe or any other application.

Sometimes when i goto shutdown, the drop down menu states 'install
updates
and shutdown'. So I choose that option. It then says installing update
1
of 9
for a while and then jumps to "shutting down" without saying
'installing
update 2 of 9' or any other increment.

So I am unable to log into my machine, which means I can't view log
files,
etc.
I recently started getting emails from the machine, at least once a day
now:
--------------------------------------------------------------------------------
RemoteAccess service is Stopped.

This service enables virtual private network (VPN) and network address
translation (NAT) routing services for the Small Business Server
computer
and
other computers connected to the network. If this service is stopped,
these
services will be unavailable.

For more information about this event, see the event logs on the server
computer. You can restart this service by using the View Services task
in
the
Server Management Monitoring and Reporting taskpad.

You can disable this alert by using the Change Alert Notifications
task.
--------------------------------------------------------------------------------

Pleaseeee help as I need access into the sever to add a new employee.
Sorry
for
the long read.






.