none
Microsoft-Windows-DistributedCOM SBS 2008

    Frage

  • Hello,

    have following Error message in Event log every 24 hours.

    Protokollname: System
    Quelle:        Microsoft-Windows-DistributedCOM
    Datum:         31.08.2009 13:23:58
    Ereignis-ID:   10010
    Aufgabenkategorie:Keine
    Ebene:         Fehler
    Schlüsselwörter:Klassisch
    Benutzer:      Nicht zutreffend
    Computer:      SBS.domain.local
    Beschreibung:
    Der Server "{0B5A2C52-3EB9-470A-96E2-6C6D4570E40F}" konnte innerhalb des angegebenen Zeitabschnitts mit DCOM nicht registriert werden.
    Ereignis-XML:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="49152">10010</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-08-31T17:23:58.000Z" />
        <EventRecordID>244621</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>SBS.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">{0B5A2C52-3EB9-470A-96E2-6C6D4570E40F}</Data>
      </EventData>
    </Event>
    
    Free Translation of Error message: The Server {0B5A2C52-3EB9-470A-96E2-6C6D4570E40F} could not be registered with DCOM withing given time limit.

    I check in Registry to what a.m. ID belongs to which seems to be "VssSnapshotMgmt Class"
    As I have come along more DCOM Error I check DCOM Settings, however there is no such thing in there.

    Even Google has only 1 seach result when typing VssSnapshotMgmt Class DCOM, which is not a lot.

    Maybe someone else has an idea.

    Thanks
    Niels

    Montag, 31. August 2009 20:11

Antworten

  • Hi,

    Have excluded VSS and all SQL, Exchange, etc. services from the daily filescan.

    Problem has not reoccurred to date.

    Thanks
    Niels
    • Als Antwort markiert NielsLo Montag, 5. Oktober 2009 17:04
    Montag, 5. Oktober 2009 17:04

Alle Antworten

  • Hi Niels

    what build of SBS 2008 is installed? (winver.exe)

    Cheers
    Andrei
    Dienstag, 8. September 2009 07:46
    Moderator
  • Hi Andrei,

    Build version reads as Windows Server 6.0 (Build 6001: Service Pack 1)

    Niels

    Dienstag, 8. September 2009 14:17
  • Hi Niels

    what keys are there besides the Default one under HKCR\CLSID\{0B5A2C52-3EB9-470A-96E2-6C6D4570E40F} entry? any AppID?

    Andrei

    Dienstag, 8. September 2009 14:49
    Moderator
  • Hi Andrei,

    found the AppID which is  "56BE716B-2F76-4dfa-8702-67AE10044F0B"

    The ID belongs to Volume Shadow Copy Service itself.

    Can I trigger the registration myself in order to track why it is timing out?

    Niels
    Dienstag, 8. September 2009 15:27
  • Hi Niels

    what you could try is stopping/starting the Volume Shadow Copy Service and having a look at the event viewer.

    Also you could try following the troubleshooting steps in the below conversation, if this is not the article you were reffering to:

    http://www.tech-archive.net/Archive/Windows/microsoft.public.windows.server.sbs/2008-12/msg01793.html

    Andrei
    Mittwoch, 9. September 2009 07:45
    Moderator
  • Hi Andrei,

    Did step 1 & 2 and restarted VSS Service. However this does not seem to be the issue.

    After performing Step outlined in above Link I restarted the Server and got the Error at about 10:05 local time.

    Today I got it at about 13:21 local time. Most of the occurrences are between 13:00 and 14:00 as this is my Lunchbreak I never thought of user activity being responsible for it.

    However found out when setting up Avira Antivirus I took the lunchbreak into consideration.

    Have paused the Daily scan now. Lets wait and See.

    Scheinbar muessen die Leute von Avira hier nachbessern.

    Niels


    Donnerstag, 10. September 2009 18:59
  • Hi Andrei,

    System did not log a DCOM Error on Friday, Saturday and Sunday.

    Will make contact with Avira and revert with results.

    Thanks
    Niels
    Montag, 14. September 2009 13:25
  • Hi,

    Have excluded VSS and all SQL, Exchange, etc. services from the daily filescan.

    Problem has not reoccurred to date.

    Thanks
    Niels
    • Als Antwort markiert NielsLo Montag, 5. Oktober 2009 17:04
    Montag, 5. Oktober 2009 17:04
  • Hi Niels

    thanks for letting us know.

    Andrei
    Dienstag, 6. Oktober 2009 06:10
    Moderator