Cannot Install Windows Server 2003 SP1
- From: "John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 24 May 2005 23:40:03 -0700
I have 11 IBM Servers and have managed to successfully install Windows 2003
SP1 on all but 1 Server. I would greatly appreciate any advise to help
resolve this issue.
I have two domain controllers, the issue is with one of the domain
controllers. It will happily install SP1 but when the system reboots after
the install is complete I get the following message just before the logon
screen.
"Windows could not be started as configured. A previous working
configuration was used instead."
I am able to logon to the server but cannot talk to or ping anything else on
the network also cannot ping or talk to this server from other servers or
workstations via name or IP Address.
I have run IPCONFIG/ALL on the server and all the network settings are ok.
When I uninstall SP1 and reboot all is back to normal with the Server
running happily and communicating across the network. I have checked and
upgraded all device drivers, then tried the install again with the same
result. This server is only file sharing.
I have search the event logs and found the error mentioned above as well as
another error around the same time this one is logged, not sure if the other
error is related. See below.
(Posted from the Event Log)
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 14/05/2005
Time: 1:03:46 PM
User: N/A
Computer: CAVSERVER08
Description:
Application popup: Service Control Manager : Windows could not be started
as configured. A previous working configuration was used instead.
_______________________________________________________
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 5603
Date: 14/05/2005
Time: 1:03:21 PM
User: NT AUTHORITY\SYSTEM
Computer: CAVSERVER08
Description:
A provider, Rsop Planning Mode Provider, has been registered in the WMI
namespace, root\RSOP, but did not specify the HostingModel property. This
provider will be run using the LocalSystem account. This account is
privileged and the provider may cause a security violation if it does not
correctly impersonate user requests. Ensure that provider has been reviewed
for security behavior and update the HostingModel property of the provider
registration to an account with the least privileges possible for the
required functionality.
.
- Prev by Date: Sysvol size
- Next by Date: Re: DHCP server RAS problems
- Previous by thread: Sysvol size
- Next by thread: Are there any article or webcast about how to monitor SQL Server?
- Index(es):
Relevant Pages
|
Loading
