Network is blown away after install, of W2003 sp1

Network worked fine, new 2003 server was installed and part of a domain.
Just installed sp1 and gor an error at leats one service failed to start.
Looked in event viewer and saw error SAM failed to start the TCP-IP or
IP-SPX listening service.
Evidently, nothing to do with nework works after that. I got no icon in my
network for add new connection, no current connection. NOTHING <GGGGG> Yet I
wa sable to loin to my domai account on thix computer after a reboot. How
the devil do I get my network back. and how the h... can MS put out a SP
that does such idiocy?
Thanks for any help,


Bob

is the nic functioning properly? any specific event id?
the login must have worked from cached credentials

"Bob" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Network worked fine, new 2003 server was installed and part of a domain.
> Just installed sp1 and gor an error at leats one service failed to start.
> Looked in event viewer and saw error SAM failed to start the TCP-IP or
> IP-SPX listening service.
> Evidently, nothing to do with nework works after that. I got no icon in
> my network for add new connection, no current connection. NOTHING <GGGGG>
> Yet I wa sable to loin to my domai account on thix computer after a
> reboot. How the devil do I get my network back. and how the h... can MS
> put out a SP that does such idiocy?
> Thanks for any help,
>
>
> Bob
>

The nic is physically OK. I removed the service pack 1 by using add remove
from the control panel add remove programs
Then rebooted the machine.
As soon as I rebooted the machine, I got full network connectivity back.
That proves that the NIc works fine and that the network cabling and hubs
are OK.

In the event viewer when I had sp1 installed I got an error message saying
SAM failed to start the TCP/IP or IP/SPX listening service.

I could not ping that machine from another I could not ping another from
that but I could ping the local loopback address 127.0.0.1

The EventId I get when this occurs is 12291.

Maybe it worked from cached credentials but I'm not sure about that. I did
an uninstall of SP1 rebooted the machine, my network was OK. I re-downloaded
a new version of SP1 to another folder than the original download, did an
install from that folder and got the same problems, no network same first
error event as above.

Hope I can get this resolved. Thanks for the help and any further help would
be appreciated.

Bob



"seth" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> is the nic functioning properly? any specific event id?
> the login must have worked from cached credentials
>
> "Bob" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Network worked fine, new 2003 server was installed and part of a domain.
>> Just installed sp1 and gor an error at leats one service failed to start.
>> Looked in event viewer and saw error SAM failed to start the TCP-IP or
>> IP-SPX listening service.
>> Evidently, nothing to do with nework works after that. I got no icon in
>> my network for add new connection, no current connection. NOTHING <GGGGG>
>> Yet I wa sable to loin to my domai account on thix computer after a
>> reboot. How the devil do I get my network back. and how the h... can MS
>> put out a SP that does such idiocy?
>> Thanks for any help,
>>
>>
>> Bob
>>
>
>

you didn't say anything about any problems with dfs, so this article may not
entirely apply, but it's the only thing i could find with id 12291

http://support.microsoft.com/?kbid=307734


"Bob" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The nic is physically OK. I removed the service pack 1 by using add remove
> from the control panel add remove programs
> Then rebooted the machine.
> As soon as I rebooted the machine, I got full network connectivity back.
> That proves that the NIc works fine and that the network cabling and hubs
> are OK.
>
> In the event viewer when I had sp1 installed I got an error message saying
> SAM failed to start the TCP/IP or IP/SPX listening service.
>
> I could not ping that machine from another I could not ping another from
> that but I could ping the local loopback address 127.0.0.1
>
> The EventId I get when this occurs is 12291.
>
> Maybe it worked from cached credentials but I'm not sure about that. I did
> an uninstall of SP1 rebooted the machine, my network was OK. I
> re-downloaded a new version of SP1 to another folder than the original
> download, did an install from that folder and got the same problems, no
> network same first error event as above.
>
> Hope I can get this resolved. Thanks for the help and any further help
> would be appreciated.
>
> Bob
>
>
>
> "seth" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> is the nic functioning properly? any specific event id?
>> the login must have worked from cached credentials
>>
>> "Bob" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Network worked fine, new 2003 server was installed and part of a domain.
>>> Just installed sp1 and gor an error at leats one service failed to
>>> start. Looked in event viewer and saw error SAM failed to start the
>>> TCP-IP or IP-SPX listening service.
>>> Evidently, nothing to do with nework works after that. I got no icon in
>>> my network for add new connection, no current connection. NOTHING
>>> <GGGGG> Yet I wa sable to loin to my domai account on thix computer
>>> after a reboot. How the devil do I get my network back. and how the h...
>>> can MS put out a SP that does such idiocy?
>>> Thanks for any help,
>>>
>>>
>>> Bob
>>>
>>
>>
>
>

Thanks Seth I think I got the symptoms wrong.
The network connect now seems to be ok But I have a COM+ service hanging on
startup which means I can't get any updates from MS and I don't see anything
in the network menu. These are the error messages in sequence.

1- SAM Failed to start TCP/IP or SPX/IPX listening thread EventId: 12291, I
looked at the microsoft links, I'm not using Novell so that doesn't apply.
2-The Symantec Settings Manager service terminated with service-specific
error 4294967295 (0xFFFFFFFF).
Event Id: 7024 I'll remove NAV That should clear this one up.
3-The Task Scheduler service terminated with the following error:
The endpoint mapper database entry could not be created
EventId 7023
4-The Automatic Updates service terminated with the following error:
The class is configured to run as a security id different from the caller.
(WAS OK Before installing SP1)
EventId 7023
5-The COM+ Event System service hung on starting.
EventId 7022 - This is where problem lies I think, how do I fix this one?
6-The System Event Notification service depends on the COM+ Event System
service which failed to start because of the following error:
After starting, the service hung in a start-pending state.
EventId 7001 - result of 5 above I guess

The application logs for the startup sequence are as follows:
1-Failed to create the COM Module! User NT Authority System EventId :13
Source ccSetMgr

The COM+ Event System detected a bad return code during its internal
processing. HRESULT was 80004015 from line 142 of
d:\srvrtm\com\complus\src\events\tier2\service.cpp . Please contact
Microsoft Product Support Services to report this error.
Source EventSystem Category 51 Event Id 4609

I think this is where all the problems start!

2-Volume Shadow Copy Service error: The EventSystem service is disabled or
is attempting to start during Safe Mode. The Volume Shadow Copy service
cannot start while in safe mode. If not in safe mode, make sure that
EventSystem service is enabled. CLSID:{4e14fba2-2e22-11d1-9964-00c04fbbb345}
Name:CEventSystem [0x80040206]
Source VSS EventId 17

3-Volume Shadow Copy Service error: Unexpected error calling routine
CoCreateInstance. hr = 0x80040206.

Source VSS EventId: 8193

4-Windows couldn't log the RSoP (Resultant Set of Policies) session status.
An attempt to connect to WMI failed. No more RSoP logging will be done for
this application of policy.

Source UserEnv Event Id:1090

5-Windows couldn't log the RSoP (Resultant Set of Policies) session status.
An attempt to connect to WMI failed. No more RSoP logging will be done for
this application of policy.
Source UserEnv Event Id:1090

Thanks for your help I hope I can find a way to fix this.

Bob


"seth" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> you didn't say anything about any problems with dfs, so this article may
> not entirely apply, but it's the only thing i could find with id 12291
>
> http://support.microsoft.com/?kbid=307734
>
>
> "Bob" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> The nic is physically OK. I removed the service pack 1 by using add
>> remove from the control panel add remove programs
>> Then rebooted the machine.
>> As soon as I rebooted the machine, I got full network connectivity back.
>> That proves that the NIc works fine and that the network cabling and hubs
>> are OK.
>>
>> In the event viewer when I had sp1 installed I got an error message
>> saying SAM failed to start the TCP/IP or IP/SPX listening service.
>>
>> I could not ping that machine from another I could not ping another from
>> that but I could ping the local loopback address 127.0.0.1
>>
>> The EventId I get when this occurs is 12291.
>>
>> Maybe it worked from cached credentials but I'm not sure about that. I
>> did an uninstall of SP1 rebooted the machine, my network was OK. I
>> re-downloaded a new version of SP1 to another folder than the original
>> download, did an install from that folder and got the same problems, no
>> network same first error event as above.
>>
>> Hope I can get this resolved. Thanks for the help and any further help
>> would be appreciated.
>>
>> Bob
>>
>>
>>
>> "seth" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> is the nic functioning properly? any specific event id?
>>> the login must have worked from cached credentials
>>>
>>> "Bob" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>>> Network worked fine, new 2003 server was installed and part of a
>>>> domain. Just installed sp1 and gor an error at leats one service failed
>>>> to start. Looked in event viewer and saw error SAM failed to start the
>>>> TCP-IP or IP-SPX listening service.
>>>> Evidently, nothing to do with nework works after that. I got no icon in
>>>> my network for add new connection, no current connection. NOTHING
>>>> <GGGGG> Yet I wa sable to loin to my domai account on thix computer
>>>> after a reboot. How the devil do I get my network back. and how the
>>>> h... can MS put out a SP that does such idiocy?
>>>> Thanks for any help,
>>>>
>>>>
>>>> Bob
>>>>
>>>
>>>
>>
>>
>
>

Hi Bob, I had this problem too and I don't have an immediate answer to
your question, but I can possibly shed some light on what ultimately
worked for me to fix this:

1) I went on the hunch that my group policies applied to this busted
server were the cause of the problem
2) I reset the security settings to their defaults on the busted server
(it took a LONG time to log in) -
http://support.microsoft.com/Default.aspx?kbid=313222
3) I un-linked all group policy settings to the busted server's OU.
(You can just move the server to a test OU without policies, if you
want)
4) I restarted the server - sure enough, it came up fine
5) Problem now is that none of my group policies were being applied,
save the global policy.

I recreated the group policies step-by-step, making sure that each time
I didn't bust the server again. YES, it took awhile. YES, I made some
mistakes along the way.

Since your group policy settings can, and probably are, very different
from mine, I can't give you a silver bullet gp setting to modify.

Hope this helps.

very helpfull...thank you!

my problem was the "default domain controllers policy"
so i reset that policy to it's defaults
1. login to domain controller
2. run
dcgpofix /targetC

source: http://www.windowsitpro.com/Article/...878/41878.html


"(E-Mail Removed)" wrote:

> Hi Bob, I had this problem too and I don't have an immediate answer to
> your question, but I can possibly shed some light on what ultimately
> worked for me to fix this:
>
> 1) I went on the hunch that my group policies applied to this busted
> server were the cause of the problem
> 2) I reset the security settings to their defaults on the busted server
> (it took a LONG time to log in) -
> http://support.microsoft.com/Default.aspx?kbid=313222
> 3) I un-linked all group policy settings to the busted server's OU.
> (You can just move the server to a test OU without policies, if you
> want)
> 4) I restarted the server - sure enough, it came up fine
> 5) Problem now is that none of my group policies were being applied,
> save the global policy.
>
> I recreated the group policies step-by-step, making sure that each time
> I didn't bust the server again. YES, it took awhile. YES, I made some
> mistakes along the way.
>
> Since your group policy settings can, and probably are, very different
> from mine, I can't give you a silver bullet gp setting to modify.
>
> Hope this helps.
>
>