Re: SP1 install and win2k3 server 2003


Dear ALL:

first of all I need to say that everything was working properly on this DC,
until I installed SP1.

it undewent rigorous testing at the time of joining to make sure it was ok,
and again after it became the master of all the fsmo roles.
since that time it has given me no trouble.

The Server was joined to the domain and the FSMO roles were transfered to
it.
its now THE {only} DC, (God forbid I should say "PDC", but it OWNS that
ROLE)
and it has AD integrated DNS. It's Microsoft Windows Server 2003 Enterprize
Edition.

No AV, nor would I run that, or any other resident crap, during an SP
install,
I am behind a firewalled router. Its on a private subnet, and so are the
clients.

I DO NOT get the error stated in this article (file not found), that you
keep pointing me to!!!!!!
http://support.microsoft.com/kb/912023

How do you explain these two errors below?

These both happened right after SP1 install, !BEFORE! ipsec blocked
anything.

1st one looks like a problem with Secutity Accounts Manager starting TCPIP
(cant start TCPIP), so that would be a BIG PROBLEM.

Next it looks like LSA cant start RPC.
ANOTHER BIG PROBLEM. - no endpoints

....and those two errors lead to all the rest of the other problems,
which would probably fix themselves if ONLY these first two were poperly
addressed.

These happened DIRECTLY after I installed SP1 and rebooted.

Your article does NOT address theses problems.

you want a copy of my system log?
maybe it will help you greatly to see the sequence of failure events.



first error:

Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 12291
Date: 2/7/2007
Time: 7:12:55 AM
User: N/A
Computer:
Description:
SAM failed to start the TCP/IP or SPX/IPX listening thread

2nd error:
Event Type: Warning (ok it says warning...but)
Event Source: LsaSrv
Event Category: None
Event ID: 32777
Date: 2/7/2007
Time: 7:12:55 AM
User: N/A
Computer:
Description:
The LSA was unable to register its RPC interface over the TCP/IP
interface.
Please make sure that the protocol is properly installed.


Thank you in advance
James Long


"Dragos CAMARA" <dragos_c@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:38EB9A16-8496-4E22-A1E2-9FAA36EECF39@xxxxxxxxxxxxxxxx
hi,
i said could be the solution because i don't know the configuration of
your
server what other programs/drivers are loaded if AV was or not installed
on
your server.
If it is a clean windows 2003 (with or witout dcpromo)it is the solution.
--
Dragos CAMARA
MCSA Windows 2003 server


"James W. Long" wrote:

Dear ALL:

not the solution?
not to be rude but I think you are wasting my time.

I'm not going to install SP1 again until I know what went wong,
and how to fix it.

I wonder if SOMEBODY could look at these errors and figure out what
happened?

Thank you in advance,

James Long


"Dragos CAMARA" <dragos_c@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B6893F69-20A0-442D-9E17-621576C9FF60@xxxxxxxxxxxxxxxx
hi,
on my first SP1 install i was stuck in same situation, after i
registered
polstore.dll all work again, i dosen't said that is the solution but
could
be
for IpSec in default blocked mode, for others errors will have to see
after
IpSec are not blocking the system connetivity.

--
Dragos CAMARA
MCSA Windows 2003 server


"James W. Long" wrote:

Dear All:

thats not the error I get.

I install sp1 then bang
nothing much works.
look:

Event Type: Information
Event Source: NtServicePack
Event Category: None
Event ID: 4381
Date: 2/7/2007
Time: 6:43:43 AM
User: JEWELCONSULTING\administrator
Computer:
Description:
Windows Server 2003 Service Pack 1 was installed.

then I reboot.
eventlog comes up.


first info:

Event Type: Information
Event Source: DCOM
Event Category: None
Event ID: 10026
Date: 2/7/2007
Time: 7:12:46 AM
User: N/A
Computer:
Description:
The description for Event ID ( 10026 ) in Source ( DCOM ) cannot be
found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may
be
able to use the /AUXSOURCE= flag to retrieve this description; see
Help
and
Support for details. The following information is part of the event:
86400,
SuppressDuplicateDuration, Software\Microsoft\Ole\EventLog.

second info

Event Type: Information
Event Source: IPSec
Event Category: None
Event ID: 4295
Date: 2/7/2007
Time: 7:12:18 AM
User: N/A
Computer:
Description:
The IPSec Driver is starting in Bypass mode. No IPSec security is
being
applied while this computer starts up. IPSec policies, if they have
been
assigned, will be applied to this computer after the IPSec services
start.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 54 00 ......T.
0008: 00 00 00 00 c7 10 00 40 ....Ç..@
0010: 01 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


first error:

Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 12291
Date: 2/7/2007
Time: 7:12:55 AM
User: N/A
Computer:
Description:
SAM failed to start the TCP/IP or SPX/IPX listening thread

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6b 07 00 00 k...

second error:

Event Type: Warning
Event Source: LsaSrv
Event Category: None
Event ID: 32777
Date: 2/7/2007
Time: 7:12:55 AM
User: N/A
Computer:
Description:
The LSA was unable to register its RPC interface over the TCP/IP
interface.
Please make sure that the protocol is properly installed.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6b 07 00 00 k...


third error:


Event Type: Error
Event Source: IPSec
Event Category: None
Event ID: 4292
Date: 2/7/2007
Time: 7:14:41 AM
User: N/A
Computer:
Description:
The IPSec driver has entered Block mode. IPSec will discard all
inbound
and
outbound TCP/IP network traffic that is not permitted by boot-time
IPSec
Policy exemptions. User Action: To restore full unsecured TCP/IP
connectivity, disable the IPSec services, and then restart the
computer.
For detailed troubleshooting information, review the events in the
Security
event log.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 54 00 ......T.
0008: 00 00 00 00 c4 10 00 c0 ....Ä..À
0010: 01 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........



after that, these sevices terminate because the endpoint mapper
database
entry could not be mapped for them:

task scheduler, ipsec, automatic updates, com+(hung on start), system
event
notification (dependency hung on start),
network connections(hung),windows firewall/ICS(hung), and the ntp
timeprovide cant get time because it cant
make a dns lookup of my time server, (becasue DNS is not up, and
neither
is
the DNS MANAGER)


So I reboot again.
then I disable ipsec from starting and reboot again but still I am not
a
dc,
even thoug I am the only dc.
(because rpc STILL does not come up)

I do not know how to ask the question. I dont think your fix is the
solution. what is the problerm here
and how do I fix it?

Thank you in advance
James Long




"Dragos CAMARA" <dragos_c@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:61764CDB-12C7-4218-B54B-293A36E84A99@xxxxxxxxxxxxxxxx
hi,
check this may be help you :
http://support.microsoft.com/kb/912023
--
Dragos CAMARA
MCSA Windows 2003 server


"James W. Long" wrote:

Hi all:

I run Windows Server 2003 SP1 INSTALL then it breaks.

errors:

-ipsec blocks me.
-no ethernet connectoid in control panel->network anymore,
but device manger says ethernet contoller present and is working
correctly.
the connectoid was there before the install and was fine.
-the rpc server is unavailable. cannot fine the domain name,
group policy processing is aborted.
-DNS manager can't connect


then this guy tells me this:

hi,
if you install the sp1 that was for deploy with SUS you have to
regsvr32
polstore.dll to start the ipsec in default mode not in blocked
mode
--

me:
Did I "install the sp1 that was for deploy with SUS..."
I do not know....???
I got it off microsofts website the full sp1 install,
as opposed to getting the download from windows update.

"regsvr32 polstore.dll" when do I do that???


Will it solve the problem ?

Thank you,

James W. Long











.

Relevant Pages

  • RE: Webparts error after sp1 install
    ... SBS 2k3 Premium ... server set up to install the intranet. ... server prompted me that the version needed upgradeing to sp1 level. ...
    (microsoft.public.windows.server.sbs)
  • Re: Error installing VPN on SBS 2003 SP1
    ... When running winver I get a pretty Small Business Server Box with the ... I had assumed that SP1 was installed. ... I am now starting to really wonder if SP1 has been installed on our SBS ... To resolve the issues, install SBS 2003 SP1. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... PCie card - sp1 slipstream is fine and gets all the way through so its a ... the arcane worls of MS Server stuff. ... other persons SP1 or SP2? ... My main reason for slipstreaming the install is because I cannot get ...
    (microsoft.public.windows.server.sbs)
  • Re: SP1 install and win2k3 server 2003
    ... server what other programs/drivers are loaded if AV was or not installed on ... I'm not going to install SP1 again until I know what went wong, ... IpSec are not blocking the system connetivity. ...
    (microsoft.public.windows.server.general)
  • Re: SP1 install and win2k3 server 2003
    ... I'm not going to install SP1 again until I know what went wong, ... IpSec are not blocking the system connetivity. ... Event Source: NtServicePack ...
    (microsoft.public.windows.server.general)