System hangs after dial up - EventId 10010, DCOM timeout

[Guest]

After dialing up the system (XP Pro SP2) hangs (connection may be established
by opening IE or done manually over network connections)
If an IE window is already open, I'm able to surf (connection is ok) but
clicks to start menu or desktop or CTRL-ALT-DEL don't work.
After 5 to 10 minutes all clicks are processed and everything works as normal.
In the event log there is always an error entry (ID10010): "The server {ID}
did not register with DCOM within the required timeout".
ID can be either
F3A614DC-ABE0-11D2-A441-00C04F795683 (C:\Programme\Messenger\msmsgs.exe)
or
72C2714F-4478-11D3-B537-00902771A435
(C:\Programme\Symantec\LiveUpdate\LuComServer_2_6.EXE)

Tried to change the modem, disabled DCOM with grc.com's DCOMBobulator
(checked the registry). Nothing changed.

Anybody can help?? Thanks!

 

[Wesley Vogel]

Click the [+] Related Knowledge Base articles
at the bottom to see a list of Knowledge Base articles.

ID: 10010
Source: DCOM
http://www.microsoft.com/technet/su...indows+Operating+System&LCID=1033&ProdVer=5.2

msmsgs.exe is the main process relating to the MSN Messenger Internet chat
tool installed by default on most Windows computers.

Depending on the version, msmsgs.exe can also be Windows Messenger.

Do you need either one? I dout it. Dump it.

LuComServer_2_6.EXE is Symantec LiveUpdate Engine COM Module. All I now
about Symantec/Norton is that they suck.

Try setting LiveUpdate so that you can check for updates manually.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Thanks for your help!

Tried several things:
- deinstalled messenger, according to
http://messenger.jonathankay.com/problem.aspx?ID=7
-> DCOM Events based on msmsgs.exe vanished, problems not
- Swiched Off Automatic LiveUpdates
-> no change
- Opened several ports and allowed LuComServer in XP Firewall (according to
Symantec)
-> no change
- deinstalled Symantec LiveUpdate
-> DCOM Events based on LuComServer vanished.
-> So I've no more errors in the EventLog, but the PC still sucks... no
reaction for several minutes after each dial up. I'm rather helpless.

Could it be something completely different? Maybe based od the ISDN
connection?

Any clues?

Click the [+] Related Knowledge Base articles
at the bottom to see a list of Knowledge Base articles.

ID: 10010
Source: DCOM
http://www.microsoft.com/technet/su...indows+Operating+System&LCID=1033&ProdVer=5.2

msmsgs.exe is the main process relating to the MSN Messenger Internet chat
tool installed by default on most Windows computers.

Depending on the version, msmsgs.exe can also be Windows Messenger.

Do you need either one? I dout it. Dump it.

LuComServer_2_6.EXE is Symantec LiveUpdate Engine COM Module. All I now
about Symantec/Norton is that they suck.

Try setting LiveUpdate so that you can check for updates manually.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

After dialing up the system (XP Pro SP2) hangs (connection may be
established by opening IE or done manually over network connections)
If an IE window is already open, I'm able to surf (connection is ok) but
clicks to start menu or desktop or CTRL-ALT-DEL don't work.
After 5 to 10 minutes all clicks are processed and everything works as
normal. In the event log there is always an error entry (ID10010): "The
server {ID} did not register with DCOM within the required timeout".
ID can be either
F3A614DC-ABE0-11D2-A441-00C04F795683 (C:\Programme\Messenger\msmsgs.exe)
or
72C2714F-4478-11D3-B537-00902771A435
(C:\Programme\Symantec\LiveUpdate\LuComServer_2_6.EXE)

Tried to change the modem, disabled DCOM with grc.com's DCOMBobulator
(checked the registry). Nothing changed.

Anybody can help?? Thanks!

 

[Wesley Vogel]

Beats me. I got rid of dialup ages ago. I only posted some info that I
knew and that I thought would help.

I would recommend that you reinstall LiveUpdate if Norton AV is your only
antivirus software. You need to have AV updates or your antivirus software
is worthless.

I use AVG 7 FREE myself and highly recommend it.

Get Your AVG 7 for free!
http://free.grisoft.com/freeweb.php/doc/2/lng/us/tpl/v5

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thanks for your help!

Tried several things:
- deinstalled messenger, according to
http://messenger.jonathankay.com/problem.aspx?ID=7
-> DCOM Events based on msmsgs.exe vanished, problems not
- Swiched Off Automatic LiveUpdates
-> no change
- Opened several ports and allowed LuComServer in XP Firewall (according
to Symantec)
-> no change
- deinstalled Symantec LiveUpdate
-> DCOM Events based on LuComServer vanished.
-> So I've no more errors in the EventLog, but the PC still sucks... no
reaction for several minutes after each dial up. I'm rather helpless.

Could it be something completely different? Maybe based od the ISDN
connection?

Any clues?

Click the [+] Related Knowledge Base articles
at the bottom to see a list of Knowledge Base articles.

ID: 10010
Source: DCOM
http://www.microsoft.com/technet/su...indows+Operating+System&LCID=1033&ProdVer=5.2

msmsgs.exe is the main process relating to the MSN Messenger Internet
chat tool installed by default on most Windows computers.

Depending on the version, msmsgs.exe can also be Windows Messenger.

Do you need either one? I dout it. Dump it.

LuComServer_2_6.EXE is Symantec LiveUpdate Engine COM Module. All I now
about Symantec/Norton is that they suck.

Try setting LiveUpdate so that you can check for updates manually.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

After dialing up the system (XP Pro SP2) hangs (connection may be
established by opening IE or done manually over network connections)
If an IE window is already open, I'm able to surf (connection is ok) but
clicks to start menu or desktop or CTRL-ALT-DEL don't work.
After 5 to 10 minutes all clicks are processed and everything works as
normal. In the event log there is always an error entry (ID10010): "The
server {ID} did not register with DCOM within the required timeout".
ID can be either
F3A614DC-ABE0-11D2-A441-00C04F795683 (C:\Programme\Messenger\msmsgs.exe)
or
72C2714F-4478-11D3-B537-00902771A435
(C:\Programme\Symantec\LiveUpdate\LuComServer_2_6.EXE)

Tried to change the modem, disabled DCOM with grc.com's DCOMBobulator
(checked the registry). Nothing changed.

Anybody can help?? Thanks!

 

[Guest]

Thanks for your advice.
I deinstalled everything from symantec/norton & MS Antispy but it's still
the same.
Tried to connect at another ISDN connection but it's the same there.
I will try to use an external modem, but I doubt to improve...
well, I might have to set up the whole system and check the connection after
every step. Or can you think of anything else?

Beats me. I got rid of dialup ages ago. I only posted some info that I
knew and that I thought would help.

I would recommend that you reinstall LiveUpdate if Norton AV is your only
antivirus software. You need to have AV updates or your antivirus software
is worthless.

I use AVG 7 FREE myself and highly recommend it.

Get Your AVG 7 for free!
http://free.grisoft.com/freeweb.php/doc/2/lng/us/tpl/v5

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thanks for your help!

Tried several things:
- deinstalled messenger, according to
http://messenger.jonathankay.com/problem.aspx?ID=7
-> DCOM Events based on msmsgs.exe vanished, problems not
- Swiched Off Automatic LiveUpdates
-> no change
- Opened several ports and allowed LuComServer in XP Firewall (according
to Symantec)
-> no change
- deinstalled Symantec LiveUpdate
-> DCOM Events based on LuComServer vanished.
-> So I've no more errors in the EventLog, but the PC still sucks... no
reaction for several minutes after each dial up. I'm rather helpless.

Could it be something completely different? Maybe based od the ISDN
connection?

Any clues?

Click the [+] Related Knowledge Base articles
at the bottom to see a list of Knowledge Base articles.

ID: 10010
Source: DCOM
http://www.microsoft.com/technet/su...indows+Operating+System&LCID=1033&ProdVer=5.2

msmsgs.exe is the main process relating to the MSN Messenger Internet
chat tool installed by default on most Windows computers.

Depending on the version, msmsgs.exe can also be Windows Messenger.

Do you need either one? I dout it. Dump it.

LuComServer_2_6.EXE is Symantec LiveUpdate Engine COM Module. All I now
about Symantec/Norton is that they suck.

Try setting LiveUpdate so that you can check for updates manually.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In lama01 <[email protected]> hunted and pecked:
After dialing up the system (XP Pro SP2) hangs (connection may be
established by opening IE or done manually over network connections)
If an IE window is already open, I'm able to surf (connection is ok) but
clicks to start menu or desktop or CTRL-ALT-DEL don't work.
After 5 to 10 minutes all clicks are processed and everything works as
normal. In the event log there is always an error entry (ID10010): "The
server {ID} did not register with DCOM within the required timeout".
ID can be either
F3A614DC-ABE0-11D2-A441-00C04F795683 (C:\Programme\Messenger\msmsgs.exe)
or
72C2714F-4478-11D3-B537-00902771A435
(C:\Programme\Symantec\LiveUpdate\LuComServer_2_6.EXE)

Tried to change the modem, disabled DCOM with grc.com's DCOMBobulator
(checked the registry). Nothing changed.

Anybody can help?? Thanks!