I have researched this for about tw months now. My backups using the built in Windows backus fails. I have gone through the procedures outlined everywhere on how to deal with this such as re-registering dll's and such. I still cannot perform a backup using the backup utility. This is a new server and had done this from the start. First it would work, then it would not, then it would, then not...you get the picture. The server is fully service packed and updated. The server does seem to run very sluggish ant many times.I get a ton of 8230 errors, The specified local group does not exist...Failed resolving account spsearch.
I also get several 10016 distributed com errors around midnight to 1AM; The error follows:
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 11/14/2012 12:52:10 AM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: OLSENHOWARD\spfarm
Computer: NT1.olsenhoward.local
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
and APPID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user OLSENHOWARD\spfarm SID (S-1-5-21-2826961360-2260095017-3414256892-1157) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Event 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">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-11-14T07:52:10.000000000Z" />
<EventRecordID>105617</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>NT1.olsenhoward.local</Computer>
<Security UserID="S-1-5-21-2826961360-2260095017-3414256892-1157" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{61738644-F196-11D0-9953-00C04FD919C1}</Data>
<Data Name="param5">{61738644-F196-11D0-9953-00C04FD919C1}</Data>
<Data Name="param6">OLSENHOWARD</Data>
<Data Name="param7">spfarm</Data>
<Data Name="param8">S-1-5-21-2826961360-2260095017-3414256892-1157</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
</EventData>
</Event>
Here is my VSSADMIN output:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {8cd937d0-6173-40ff-be69-b4a6cbfec94b}
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {8f0305c9-de83-4744-949b-185f79a9cd90}
State: [8] Failed
Last error: Timed out
Writer name: 'SharePoint Services Writer'
Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
Writer Instance Id: {17da5ea2-6197-4fc0-9737-c625f1bddf8a}
State: [8] Failed
Last error: Timed out
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {d7927ab3-9aaa-4e61-a924-13c07c4f6cf5}
State: [8] Failed
Last error: Timed out
Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
Writer Instance Id: {36f04712-8dab-4da5-b0f7-74fc76bbf43b}
State: [8] Failed
Last error: Timed out
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {660a79a8-adc3-4bfc-96f4-dee6c10c9aa9}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {9ed4156e-a732-4d4d-9e12-e24068705bf2}
State: [8] Failed
Last error: Timed out
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {70d77001-8288-4ed6-a9f1-6b4d8dfe2c64}
State: [8] Failed
Last error: Timed out
Writer name: 'TS Gateway Writer'
Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
Writer Instance Id: {90027fcc-7070-41d3-8a6a-c0a291b36e89}
State: [8] Failed
Last error: Timed out
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {d84e640c-cbcd-415e-a873-0290f3d94d8f}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {bba1c909-ff54-4027-90e2-c26bdf55d333}
State: [1] Stable
Last error: No error
Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
Writer Instance Id: {dbe7daae-e3da-4298-b793-ecc24fb373a1}
State: [8] Failed
Last error: Timed out
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {7696c9a6-b461-4a26-bb87-e7c5af70cfe2}
State: [8] Failed
Last error: Timed out
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {f67fab6f-3d0e-40b6-a22c-a3282f945766}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {f6db6a66-1ac9-46de-95e4-377467f72b57}
State: [1] Stable
Last error: No error
Writer name: 'SPSearch4 VSS Writer'
Writer Id: {35500004-0201-0000-0000-000000000000}
Writer Instance Id: {637b4d1c-65d6-43b9-8466-8c3136b67715}
State: [8] Failed
Last error: Timed out
Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {2b54c93c-7e98-4547-98e0-765b88a4c54c}
State: [8] Failed
Last error: Timed out
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {410d049f-e1f6-477d-98d5-362d096f1eb4}
State: [8] Failed
Last error: Timed out
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {21354818-3a49-45b2-9fb6-f3e45f2a7f76}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {4a748540-24a2-4e65-9f94-83d382a20096}
State: [8] Failed
Last error: Timed out
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {ade4b79a-a3d8-4809-9b6a-638bf6da124a}
State: [8] Failed
Last error: Timed out
C:\Windows\system32>
Please help as I have no other ideas on how to attack this.
Thanks, Todd