BU fails SBS 2011 Std/ ESXi 5.1: Information Store (1188) Shadow copy instance 1 aborted

Hi

BU stops after 1 minute and i have error on the event vievewer as mentioned on the topic. The target is a iSCSI disk.

"vssadmin list writers" list one error :
Writer name: 'SPSearch4 VSS Writer'
   Writer Id: {35500004-0201-0000-0000-000000000000}
   Writer Instance Id: {cce7ad76-4955-4464-af94-7f73c81cf229}
   State: [8] Failed
   Last error: Inconsistent shadow copy


I'll allready recreated SBS BU from scratch.

Here are two errors at the event viewer:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
"Log Name:      Application
Source:        ESE
Date:          27.4.2014 9:24:43
Event ID:      2007
Task Category: ShadowCopy
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HIDEDINFO2.HidedInfo.local
Description:
Information Store (1188) Shadow copy instance 1 aborted.

For more information, click http://www.microsoft.com/contentredirect.asp.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESE" />
    <EventID Qualifiers="0">2007</EventID>
    <Level>2</Level>
    <Task>16</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-27T06:24:43.000000000Z" />
    <EventRecordID>805894</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HIDEDINFO2.HidedInfo.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Information Store</Data>
    <Data>1188</Data>
    <Data>
    </Data>
    <Data>1</Data>
  </EventData>
</Event>"

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          27.4.2014 9:24:43
Event ID:      521
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      HIDEDINFO2.HidedInfo.local
Description:
The backup operation that started at '¿2014¿-¿04¿-¿27T06:24:12.851000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" />
    <EventID>521</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-27T06:24:43.100466900Z" />
    <EventRecordID>805896</EventRecordID>
    <Correlation />
    <Execution ProcessID="9692" ThreadID="9260" />
    <Channel>Application</Channel>
    <Computer>HIDEDINFO2.HidedInfo.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BackupTime">2014-04-27T06:24:12.851000000Z</Data>
    <Data Name="ErrorCode">2155348129</Data>
    <Data Name="ErrorMessage">%%2155348129</Data>
  </EventData>
</Event>

Allready performed this (cosmetic?) procedure:
http://support.microsoft.com/kb/2537096


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Finally I have this:
Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          27.4.2014 9:25:03
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:      
User:          HIDEDINFO\spfarm
Computer:      HIDEDINFO2.HidedInfo.local
Description:
The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID 77c7ba1d-8fa5-4a1c-9868-2d66b6090d82) threw an exception. More information is included below.

The device is not ready.  
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
    <EventID>6398</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>12</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-27T06:25:03.302596400Z" />
    <EventRecordID>805898</EventRecordID>
    <Correlation ActivityID="{88F240F2-6FFE-4FC7-A346-4CA17C527B3F}" />
    <Execution ProcessID="6240" ThreadID="6344" />
    <Channel>Application</Channel>
    <Computer>HIDEDINFO2.HidedInfo.local</Computer>
    <Security UserID="S-1-5-21-609451712-3025167268-1801966297-3153" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition</Data>
    <Data Name="string1">77c7ba1d-8fa5-4a1c-9868-2d66b6090d82</Data>
    <Data Name="string2">The device is not ready.  </Data>
  </EventData>
</Event>

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

We don't uswe SharePoint at this site. There is only on drive (C:) installed.

What to do?
RimFire007Asked:
Who is Participating?
 
RimFire007Connect With a Mentor Author Commented:
Removing NT Backup (used for migration) solved the actual problem. Just backed up the Computer.

Aha, there are no´errors anymore for vss-writers. I did fix some BPA-recommendations but I believe that removing the NTBackup were the key.

Here is the currnet list anyways.

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: {bca57123-c4a7-4ee7-938f-acc72eab5ec6}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {d661fe9f-9d2e-40d4-8feb-5968eab45333}
   State: [1] Stable
   Last error: No error

Writer name: 'SharePoint Services Writer'
   Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
   Writer Instance Id: {17930fce-baf5-4763-a73f-bed7e6d7a46c}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {46fac360-4fbb-4a18-92b8-b205a66eae87}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {d0ed7da2-17b6-4295-9fc8-c68da4fee484}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {1e634323-00da-42f6-9e5e-f5171f8487a6}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {b02ee37d-bd91-4681-89a5-dc5c7b2493d8}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {2b9a7097-e547-4308-ac9a-3ab3b350169d}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {29146dee-24ef-4c82-986c-e79c4a1f351a}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {51378fad-b1c8-4a3b-bc3f-83ef5e7d23cc}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {ffbb446a-3202-467a-83fd-c8279866a6ea}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {95e5af2b-a142-4632-b111-d08b1a7ac70f}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {a470cebf-7471-436d-8732-384881a4d5c2}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {ef2beae4-13c9-41d2-a070-27cc5bc74d56}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {7cdd7b6d-1125-4ece-9c6d-312b91de5a4d}
   State: [1] Stable
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {318ba397-f8b2-4115-9c1e-fcbd0b5b76f9}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {041d8a99-21aa-42a1-9a30-710b029713d5}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {88005651-1e69-4e18-b5f6-01171f1e3b7e}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {2efb001f-d2cf-4b42-9901-15e61641d5a3}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {c6176788-46b5-4c00-8286-e5e5610710aa}
   State: [1] Stable
   Last error: No error
0
 
RimFire007Author Commented:
Additionally

There were NTBackup installed at the Computer(due to migration at 2012). Just removed it and rebooting the Computer now.
0
 
GiladnCommented:
what is this writer -  cce7ad76-4955-4464-af94-7f73c81cf229 ?

can you post output of "vssadmin list writers" ?

in addition, try to search in registry, or even back it up (export) and delete this writer (i've googled and didn't find the vss supplier). after that reboot the server and try again.

Hope this helps,

G
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
RimFire007Connect With a Mentor Author Commented:
The problem were solved removing  NTBackup.

http://kwsupport.com/2012/12/uninstall-nt-backup-utility-after-sbs-migration/

Thanks for paying attention.
0
 
GiladnCommented:
Great. I'm glad you have backups now ;-)
0
 
RimFire007Author Commented:
Removing the NT backup and perhaps some BPA suggested fixes solved the problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.