what is {03E0E6C2-363B-11D3-B536-00902771A435}
I got in system event::
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 2007-01-03
Time: 20:30:24
User: NT AUTHORITY\SYSTEM
Computer: IEI-A64
Description:
The server {03E0E6C2-363B-11D3-B536-00902771A435} did not register with DCOM
within the required timeout.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


what do I need to do about it?

Don't know for sure but it's caused by Symantec software. You might
want to verify with their tech support.

John

GS wrote:

> what is {03E0E6C2-363B-11D3-B536-00902771A435}
> I got in system event::
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10010
> Date: 2007-01-03
> Time: 20:30:24
> User: NT AUTHORITY\SYSTEM
> Computer: IEI-A64
> Description:
> The server {03E0E6C2-363B-11D3-B536-00902771A435} did not register with DCOM
> within the required timeout.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> what do I need to do about it?
>
>

Have to disagree here. The Registry entry has to do with Windows Media
Center, not Symantec. At any rate, it appears to be an issue with DCOM not
being able to connect to a necessary service...

Honu


"John John" <(E-Mail Removed)> wrote in message
news:Ol$(E-Mail Removed)...
> Don't know for sure but it's caused by Symantec software. You might want
> to verify with their tech support.
>
> John
>
> GS wrote:
>
>> what is {03E0E6C2-363B-11D3-B536-00902771A435}
>> I got in system event::
>> Event Type: Error
>> Event Source: DCOM
>> Event Category: None
>> Event ID: 10010
>> Date: 2007-01-03
>> Time: 20:30:24
>> User: NT AUTHORITY\SYSTEM
>> Computer: IEI-A64
>> Description:
>> The server {03E0E6C2-363B-11D3-B536-00902771A435} did not register with
>> DCOM
>> within the required timeout.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>> what do I need to do about it?
>>
>>
>

The GUID {03E0E6C2-363B-11D3-B536-00902771A435} tells me it belongs to
Symantec. The OP can search the registry for the GUID and he/she will
find out who owns it. The problem with those 10010 DCOM server errors
is almost always with the application identified by the GUID, not DCOM
itself. The first step to correcting the problem is to identify the
GUID then take it from there. What registry entry tells you that it
belongs to WMP?

John

Hertz_Donut wrote:

> Have to disagree here. The Registry entry has to do with Windows Media
> Center, not Symantec. At any rate, it appears to be an issue with DCOM not
> being able to connect to a necessary service...
>
> Honu
>
>
> "John John" <(E-Mail Removed)> wrote in message
> news:Ol$(E-Mail Removed)...
>
>>Don't know for sure but it's caused by Symantec software. You might want
>>to verify with their tech support.
>>
>>John
>>
>>GS wrote:
>>
>>
>>>what is {03E0E6C2-363B-11D3-B536-00902771A435}
>>>I got in system event::
>>>Event Type: Error
>>>Event Source: DCOM
>>>Event Category: None
>>>Event ID: 10010
>>>Date: 2007-01-03
>>>Time: 20:30:24
>>>User: NT AUTHORITY\SYSTEM
>>>Computer: IEI-A64
>>>Description:
>>>The server {03E0E6C2-363B-11D3-B536-00902771A435} did not register with
>>>DCOM
>>>within the required timeout.
>>>
>>>For more information, see Help and Support Center at
>>>http://go.microsoft.com/fwlink/events.asp.
>>>
>>>
>>>what do I need to do about it?
>>>
>>>
>>
>
>

Hertz

HKEY_CLASSES_ROOT\CLSID\{03E0E6C2-363B-11D3-B536-00902771A435}
LocalServer32 (default) REG_SZ "C:\PROGRA~1\Symantec\LIVEUP~1.exe"
ProgID (default) REG_SZ Symantec.stCheckForUpdates.1
VersionIndependantProgID (default) REG_SZ Symantec.stCheckForUpdates


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Hertz_Donut wrote:
> Have to disagree here. The Registry entry has to do with Windows
> Media Center, not Symantec. At any rate, it appears to be an issue
> with DCOM not being able to connect to a necessary service...
>
> Honu
>
>

GS

How often has this error occurred? The server relates to Norton Live
Update. From Norton run Live Update. Does the Update service work?

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~





GS wrote:
> what is {03E0E6C2-363B-11D3-B536-00902771A435}
> I got in system event::
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10010
> Date: 2007-01-03
> Time: 20:30:24
> User: NT AUTHORITY\SYSTEM
> Computer: IEI-A64
> Description:
> The server {03E0E6C2-363B-11D3-B536-00902771A435} did not register
> with DCOM within the required timeout.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> what do I need to do about it?

nass wrote:

>
> "John John" wrote:
>
>
>>The GUID {03E0E6C2-363B-11D3-B536-00902771A435} tells me it belongs to
>>Symantec. The OP can search the registry for the GUID and he/she will
>>find out who owns it. The problem with those 10010 DCOM server errors
>>is almost always with the application identified by the GUID, not DCOM
>>itself. The first step to correcting the problem is to identify the
>>GUID then take it from there. What registry entry tells you that it
>>belongs to WMP?
>>
>>John
>>
>>Hertz_Donut wrote:
>>
>>
>>>Have to disagree here. The Registry entry has to do with Windows Media
>>>Center, not Symantec. At any rate, it appears to be an issue with DCOM not
>>>being able to connect to a necessary service...
>>>
>>>Honu
>>>
>>>
>>>"John John" <(E-Mail Removed)> wrote in message
>>>news:Ol$(E-Mail Removed)...
>>>
>>>
>>>>Don't know for sure but it's caused by Symantec software. You might want
>>>>to verify with their tech support.
>>>>
>>>>John
>>>>
>>>>GS wrote:
>>>>
>>>>
>>>>
>>>>>what is {03E0E6C2-363B-11D3-B536-00902771A435}
>>>>>I got in system event::
>>>>>Event Type: Error
>>>>>Event Source: DCOM
>>>>>Event Category: None
>>>>>Event ID: 10010
>>>>>Date: 2007-01-03
>>>>>Time: 20:30:24
>>>>>User: NT AUTHORITY\SYSTEM
>>>>>Computer: IEI-A64
>>>>>Description:
>>>>>The server {03E0E6C2-363B-11D3-B536-00902771A435} did not register with
>>>>>DCOM
>>>>>within the required timeout.
>>>>>
>>>>>For more information, see Help and Support Center at
>>>>>http://go.microsoft.com/fwlink/events.asp.
>>>>>
>>>>>
>>>>>what do I need to do about it?
>>>>>
>
>
> I Agree with Hertz it is a DCOM error with due respect John, for some reason
> a serivce or application didn't start or stoped.
> If the OP have Symantec then he/she the only one know.
> The OP should look in the Event Viewer for any Error messages can lead to
> the Culprit in this scenario.
> Also he/she should scan for malwares/graywares and viruses on Her/His
> computer to be sure if it is the deed or the make of Malwares/Viruses.
> If all clean then a Repair Install is the solution in some cases, but need
> to back up Data first before performing Repair install for XP.

See Gerry Cornell's post. While the error can be caused by DCOM itself
more often than not Event ID's 10010 in DCOM are caused by the
underlying application, not DCOM itself. If DCOM is broken generally
the error will happen with different CLSID/GUID's, not just with one
clisd. The first step to solving Event ID 10010 errors is to identify
the application associated with the error by searching the registry for
the CLSID/GUID string, most often the application identified is the one
not properly configured for DCOM, or it has programing bugs.

One can also run dcomcnfg.exe and see if he can find the CLSID/GUID or
application by name and see if configuration or custom security
configurations associated with the application can be corrected there.

John

I won't be surprised if it is related to Symantec live update or other
components of Symantec client security, Ghost.


I have to look and check tomorrow

Thank you all for the very useful info. much appreciated

"Gerry Cornell" <(E-Mail Removed)> wrote in message
news:OfFny$(E-Mail Removed)...
> GS
>
> How often has this error occurred? The server relates to Norton Live
> Update. From Norton run Live Update. Does the Update service work?
>
> --
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
>
>
>
> GS wrote:
>> what is {03E0E6C2-363B-11D3-B536-00902771A435}
>> I got in system event::
>> Event Type: Error
>> Event Source: DCOM
>> Event Category: None
>> Event ID: 10010
>> Date: 2007-01-03
>> Time: 20:30:24
>> User: NT AUTHORITY\SYSTEM
>> Computer: IEI-A64
>> Description:
>> The server {03E0E6C2-363B-11D3-B536-00902771A435} did not register
>> with DCOM within the required timeout.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>> what do I need to do about it?
>

Nass

Uninstalling Norton is often easier said than done. I agree with using
AVG rather than Symantec. You do not, however, provide an AVG link.

http://free.grisoft.com/freeweb.php

As I said earlier the OP should see if Live Update is working first.
The DCOM error could be a one off blip, which goes away after
rebooting.


--

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

nass wrote:
> "John John" wrote:
>
> To the OP:
> 2- I suggest Uninstalling the Symantec and if the Subscription ended
> download a free avast or AVG with ZA firewall and he/she will better
> OFF. http://www.avast.com
> http://www.pandasecurity.com for a scan online.
>
> Download the Spybot for malware and don't run it in Tea timer Mode:
> http://www.safer-networking.org
> 2= If all fail download the Hijackthis and send the report to one of
> many forums for analysis and troubleshooting:
> When all else fails, HijackThis v1.99.1
> (http://aumha.org/downloads/hijackthis.zip) is the preferred tool to
> use. It will help you to both identify and remove any
> hijackware/spyware. Post your log to
> http://aumha.net/viewforum.php?f=30,
> http://castlecops.com/forum67.html,
> http://forums.subratam.org/index.php?showforum=7, or other
> appropriate forums for expert analysis, not here.
> HTH.
> Please let us know.
> Regards,
> nass
> ----
> www.nasstec.co.uk

Hi Gerry,
Not with Symantec, I have a brand New Laptop reside here in the Office and
the Live Update doesn't work from the start, even with new install from the
CD, never mind being installed and get corrupted by somehow.
It is 2007 and the User can't get it back to get refund after opening the
Package
We had seen this many times if the Liveupdate with symantec gone it is gone
for good, clean install of the Application is needed.

The OP is infected with a worm/malwares or someting similar that corrupted
the liveUpdate and preventing the SYC from runing or getting updates.
If the OP can't uninstall SyC he/she can download the symantec uninstaller
Tool:
http://service1.symantec.com/SUPPORT...05033108162039

For the OP to be sure that it is LiveUpdate run the Live Update and see if
you will get Error like LLU800 or something similar that live updates can
update the software then you can click on the Help link to get more info and
solution from Symantec site.
Regards,
nass
-------
www.nasstec.co.uk


"Gerry Cornell" wrote:

>
> Nass
>
> Uninstalling Norton is often easier said than done. I agree with using
> AVG rather than Symantec. You do not, however, provide an AVG link.
>
> http://free.grisoft.com/freeweb.php
>
> As I said earlier the OP should see if Live Update is working first.
> The DCOM error could be a one off blip, which goes away after
> rebooting.
>
>
> --
>
> Regards.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> nass wrote:
> > "John John" wrote:
> >
> > To the OP:
> > 2- I suggest Uninstalling the Symantec and if the Subscription ended
> > download a free avast or AVG with ZA firewall and he/she will better
> > OFF. http://www.avast.com
> > http://www.pandasecurity.com for a scan online.
> >
> > Download the Spybot for malware and don't run it in Tea timer Mode:
> > http://www.safer-networking.org
> > 2= If all fail download the Hijackthis and send the report to one of
> > many forums for analysis and troubleshooting:
> > When all else fails, HijackThis v1.99.1
> > (http://aumha.org/downloads/hijackthis.zip) is the preferred tool to
> > use. It will help you to both identify and remove any
> > hijackware/spyware. Post your log to
> > http://aumha.net/viewforum.php?f=30,
> > http://castlecops.com/forum67.html,
> > http://forums.subratam.org/index.php?showforum=7, or other
> > appropriate forums for expert analysis, not here.
> > HTH.
> > Please let us know.
> > Regards,
> > nass
> > ----
> > www.nasstec.co.uk
>
>