william
Thu Jan 19 18:46:01 CST 2006
Yes, I understand what you mean, it said "We're sorry
There is no additional information about this issue in the Error and Event
Log Messages or Knowledge Base databases at this time. You can use the links
in the Support area to determine whether any additional information might be
available elsewhere." Then I had following some of these instruction which
look like the issue, but it is helpless.
William
"Dave Nickason [SBS MVP]" wrote:
> I mean when you open the error from the event log and click on the link at
> the bottom. Usually for DCOMs, those bring you to a web page with specific
> instructions on how to fix the error.
>
> > For more information, see Help and Support Center at
> >
http://go.microsoft.com/fwlink/events.asp."
> >
>
>
>
> "William Shen" <william.shen@alcoa.com> wrote in message
> news:577270F5-42F6-4DD4-B136-F9AE5548D7F3@microsoft.com...
> > of course not. It just tell me the eventID: 10010, source: DCOM.
> >
> > "Dave Nickason [SBS MVP]" wrote:
> >
> >> If you click on the link in the event log error, does it bring you to a
> >> page
> >> that tells how to fix it? If so, just follow those instructions.
> >>
> >>
> >> "William Shen" <william.shen@alcoa.com> wrote in message
> >> news:F86F6749-0937-4E07-A204-1D2EC22C462E@microsoft.com...
> >> >3 of our DCs log the following error in the event viewer, they report
> >> >this
> >> > error again and again.
> >> >
> >> > "The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} 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."
> >> >
> >> > When start Windows Installer service, it stop reporting the error, but
> >> > after
> >> > bout minutes, the Windows Installer service is stopped automatically,
> >> > then
> >> > it
> >> > report the error again.
> >> >
> >> >
> >>
> >>
> >>
>
>
>