Incomplete bootup

  • Thread starter Thread starter Allan
  • Start date Start date
A

Allan

Hello all. I just installed SP4 on my Windows 2000 Server
on Saturday. Upon reboot it would not let me log in for
about an 1/2 hour. I finally got in and many of my
services including Active Directory Connector, a few of my
backup exec (Veritas) services, Distributed File System,
and a few more were not started. I went ahead and started
them manually and they all came up and all was well.
Tonight (Monday) I rebooted to see if I would get the same
result. The same thing is happening. Does anyone think
this would be due to SP4 or possibly something else. I
did archive the filesso I should be able to uninstall
SP4. Just curiouse if anyone would have an idea about
this before I Uninstall SP4. Thanks for your time.


Allan
 
That is strange, but first thing I would check is Event Log to see what
error events are happening during system startup.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), MVP
(e-mail address removed)
http://ladava.com
 
Try uninstalling SP4 from your system and then try to reinstall SP4. I got
similar problem on one server with SP3 that hang during startup, but after
SP3 uninstall it worked.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), MVP
(e-mail address removed)
http://ladava.com

Allan said:
Its me again. Below I have included some of my event logs.

Event ID: 26
Application popup: spoolsv.exe - Entry Point Not Found :
The procedure entry point GetJobA could not be located in
the dynamic link library SPOOLSS.dll.

Event ID: 8250
The Win32 API call 'DsGetDCNameW' returned error code
[0x862] The specified component could not be found in the
configuration information. The service could not be
initialized. Make sure that the operating system was
installed properly.

Event ID: 7001
The Net Logon service depends on the Server service which
failed to start because of the following error:
After starting, the service hung in a start-pending state.

Thanks again for your time.

Allan
-----Original Message-----
That is strange, but first thing I would check is Event Log to see what
error events are happening during system startup.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), MVP
(e-mail address removed)
http://ladava.com




.
 
Back
Top