locked
Daily (but not at schedualed av or backup times) DCOM event 10010 for VssSnapshotMgmt RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    - <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="2010-11-26T00:07:54.000Z" />
      <EventRecordID>368588</EventRecordID>
      <Correlation />
      <Execution ProcessID="0" ThreadID="0" />
      <Channel>System</Channel>
      <Computer>PET310.efplus3.local</Computer>
      <Security />
      </System>
    - <EventData>
      <Data Name="param1">{0B5A2C52-3EB9-470A-96E2-6C6D4570E40F}</Data>
      </EventData>
      </Event>
    I've seen
    http://www.eggheadcafe.com/software/aspnet/33679510/dcom-10010-error-on-sbs-2008.aspx and yes, it is the "VssSnapshotMgmt Class" and the AppID is {56BE716B-2F76-4dfa-8702-67AE10044F0B} "Volume Shadow Copy Service". All the access permissons are right, and I don't want to rebuilt MSDTC since everything else seems to be fine and downtime is unwelcome.
    http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/40ebd247-a423-432c-a85c-ab336d8dfffb/ I have 8gb RAM and the server is just Exchange and company web, no major load... we do run ForeFront, which is a pig...
    http://social.technet.microsoft.com/Forums/de-DE/windows_Serverde/thread/98fdbf9b-2587-4acf-b0da-3e80e5e95b95/ is more interesting, but the errors popup in my log at different times, not always at the AV scan time:
    Error 12/3/2010 5:32:53 AM DistributedCOM 10010 None
    Error 12/2/2010 4:07:14 AM DistributedCOM 10010 None
    Error 12/1/2010 1:08:35 AM DistributedCOM 10010 None
    Error 11/30/2010 1:06:32 AM DistributedCOM 10010 None
    Error 11/28/2010 10:31:34 PM DistributedCOM 10010 None
    Error 11/27/2010 10:08:09 PM DistributedCOM 10010 None
    Error 11/26/2010 6:04:11 PM DistributedCOM 10010 None
    Error 11/25/2010 4:07:54 PM DistributedCOM 10010 None
    There seem to be a smattering of people with the same issue, e.g.
    But no real solutions yet.
    Friday, December 3, 2010 7:39 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    How much memory in your SBS 2008 server?

    Also, have you experienced in other symptooms? specificially any system crashes or automatic restarts of the server?

    -Kevin Weilbacher (SBS MVP)
    "The days pass by so quickly now, the nights are seldom long"
    KW Support MVP Blog
    MVP's do NOT work for Microsoft. We give our time freely to support the SBS community!
    Sunday, December 5, 2010 2:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    8GB in the server, as I said in the post, and as I also said, everything seem to be working find. No downtime, no un-commanded restarts, no crashes, no problems /other/ than this error.
    Monday, December 6, 2010 10:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Bump... I'm up to 5 of these a day... no apparent rhyme or reason. Any ideas how to troubleshoot this?
    Thursday, December 9, 2010 1:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    After appearing many days in a row, this error has suddenly stopped showing up. As far as I can tell, nothing was done that should have resolved it... no updates installed. It just stopped on its own.
    • Marked as answer by James Newton Friday, December 17, 2010 7:10 PM
    • Unmarked as answer by James Newton Monday, January 3, 2011 5:52 PM
    Friday, December 17, 2010 7:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    And they are back again... started up again on the 19th, then 21st, 23,24, 26 thru 29 each day, and 31st thru today the 3rd. Just once a day. Different times, but usually either in the early morning or late at night.

    Wierd unexplained random errors in the event log make me nuts.

    I've had :

    • 1 occurance of the good old 2424/3760, which seems to plague so many. I get very few, and many other people see this so I don't worry so much.
    • a 5066 FSEVsapi. Probably just someone sending a huge attachement. A few of these are expected.
    • a couple of 32092 MS Fax, we are getting lots of faxes so a few will be voice calls, hang ups, or failures from the other end... these are expected.

    And nothing else bad in the logs in the last day at least.

    Monday, January 3, 2011 6:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Still finding these errors...

     

    I looked up the {0B5A2C52-3EB9-470A-96E2-6C6D4570E40F} and it is apparently VssSnapshotMgmt. Googling that shows up a number of people who are having this same error. 2 of them seem to have made it go away by installing more RAM... but seriously? 6GB isn't enough? One guy went from 4 to 12... Wow... a SBS server with 12 GB of ram. Seems excessive to me, but I'll look into the cost.

    Thursday, February 10, 2011 7:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Upgraded the server from 8 to 16GB RAM. This error still occurs, but may be less frequent. I was getting it every single day. For example, this month I got it on day 1, 2, 3, 4, 5, 6, 8, 9, 11, 12, 15, 16, 19, 21. The server RAM was upgraded on the 12th. So this issue is apparently /related/ to RAM, but not completely solved by it.... unless someone wants to say that 16GB isn't enough for an underutilized SBS 2k8 server...
    Monday, October 24, 2011 4:11 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I find these too, on many SBS2008 installations I service. Sometimes once a day, sometimes more frequent. Sometimes at the scheduled shadow copy time, sometimes during backup, sometimes without any apparent reason. Sometimes they stop all by themselves, only to reappear months later. There are many discussions about this in several forums, but no real solution, only a lot of magical handwaving propositions which sometimes help but more often don't.

    Obviously there are deeper problems here which Microsoft is unable to get solved.

    First of all, the error reporting is insufficient. The message tells neither what the failing DCOM service is (ok, you can find out by searching the registry, but still ...) nor who tried to register it (which is essential for finding the triggering event) nor, most important of all, why the registration failed.

    Second, the "online help" link is particularly unhelpful in this case: "Report the error to the application developer" indeed. This error has been reported to the application developer (ie. Microsoft) many times, and nothing has been resolved.

    Friday, December 21, 2012 2:01 PM