Error returned while creating the volume shadow copy:0x8004230f

blin2000
blin2000 used Ask the Experts™
on
Problems:

1. When trying to run backup in SBS 2003 to backup and local file to a local drive, I receive this message: Error returned while creating the volume shadow copy:0x8004230f.

2. The Shadows Copied of the drive properties shows: Failed to retrieve volumes that are eligible for shadows copies. Error 0x8004230f: The shadows copy provider had an unexpected error while trying to process the specified operation. The screenshot is here: http://www.chicagotech.net/troubleshooting/eventid12293.htm


3. The Event Viewer lists these ID ID 12293 and 8019

Event Type:      Error

Event Source:   VSS

Description:

Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::QueryVolumesSupportedForSnapshots(ProviderId,29,...) [hr = 0x8000ffff].

Event Type:      Error

Event Source:   NTBackup

Description:

End Operation: Warnings or errors were encountered.

Consult the backup report for more details.

What I did:

1. Have tried this article.

Article ID: 940032 - Last Review: October 11, 2007 - Revision: 2.2

Various issues may occur on a Windows Server 2003-based computer that is running the Volume Shadow Copy Service
2. Make sure RPC and VSS service start.
3. Tried clean boot.
4. Here are vssadmin list provider and writers results
C:\Documents and Settings\BLin>vssadmin list providers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'

   Provider type: System

   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}

   Version: 1.0.0.7

C:\Documents and Settings\BLin>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'

   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

   Writer Instance Id: {58545d0d-bb5e-4cf8-9c0b-c847c7c19ef7}

   State: [1] Stable

   Last error: No error

Writer name: 'SqlServerWriter'

   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

   Writer Instance Id: {b39f48e3-ce0a-4815-9211-8274fec93eca}

   State: [1] Stable

   Last error: No error

Writer name: 'MSDEWriter'

   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}

   Writer Instance Id: {69a03881-4df3-4ec5-a71f-d247123b0d40}

   State: [1] Stable

   Last error: No error

Writer name: 'COM+ REGDB Writer'

   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

   Writer Instance Id: {9cde9118-b7bf-4c1a-908a-8f0838726079}

   State: [1] Stable

   Last error: No error

Writer name: 'IIS Metabase Writer'

   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

   Writer Instance Id: {32c711a7-26d4-443a-8d7e-2ad7d6f18bfa}

   State: [1] Stable

   Last error: No error

Writer name: 'NTDS'

   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

   Writer Instance Id: {64dd3155-17a1-47f9-8a47-289cd080b68f}

   State: [1] Stable

   Last error: No error

Writer name: 'Registry Writer'

   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

   Writer Instance Id: {02a7c833-d592-4d04-bd27-8beb4d82950c}

   State: [1] Stable

   Last error: No error

Writer name: 'Event Log Writer'

   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}

   Writer Instance Id: {b7d5fdce-c5b1-4cd0-8419-8a56e46b9993}

   State: [1] Stable

   Last error: No error

Writer name: 'WINS Jet Writer'

   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}

   Writer Instance Id: {233639b0-6f40-45bd-8749-c41f8dd9b9fb}

   State: [1] Stable

   Last error: No error

Writer name: 'FRS Writer'

   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}

   Writer Instance Id: {89afbe0b-4a76-4425-bacc-84f8c5f4d057}

   State: [1] Stable

   Last error: No error

Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Writer Instance Id: {1eec33d2-f154-487f-b788-f22a88d9df9b}

   State: [1] Stable

   Last error: No error

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Commented:
http://kb.backupassist.com/articles.php?aid=2971
Or try a restart.. it makes wanredfull things for VSS :)
O. PierruSystem admin

Commented:
Hello,


1/ From the log you posted, I can't seem to find any 3rd party VSS writers. Am I right?

2/ What version of SBS/Windows Server 2003 are you running?

3/ Can you try to launch the SBS backup manually if you haven't tried already and see if the error occurs. If the error occurs, please post the corresponding SBS backup log.

4/ Can you launch NTBackup (not the SBS backup tool) and try to backup just 1 file from a volume which is "Shadow Copy enabled". Error?

Author

Commented:
1. I have tried reboot the server.
2. No 3dr party VSS writers.
3. SBS 2003 SP2.
4. Try NTBackup. It is the same error.
5. Here are the log
Backup Status
Operation: Backup
Active backup destination: File
Media name: "bobtest.bkf created 8/8/2009 at 3:44 PM"

Volume shadow copy creation: Attempt 1.

Error returned while creating the volume shadow copy:0x8004230f.

Error returned while creating the volume shadow copy:8004230f
Aborting Backup.

----------------------

The operation did not successfully complete.

----------------------
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

O. PierruSystem admin

Commented:
Can you post one of the latest SBS backup log (full)?

Author

Commented:
That one I posted is the latest. Or you talk something else.
O. PierruSystem admin

Commented:
Yes, it should be named something like: "Small Business Server Backup (0x).bkf"

Author

Commented:
I think you are looking for backup log. Here is.

8/8/2009 11:10 AM
-------------------------------
Date: 8/8/2009
Time: 11:10 AM
User: blin
-------------------------------

Backup Runner started.
Launching NTBackup: ntbackup.exe backup "@C:\Program Files\Microsoft Windows Small Business Server\Backup\Small Business Backup Script.bks" /d "SBS Backup created on 8/8/2009 at 11:10 AM" /v:yes /r:no /rs:no /hc:off /m normal /j "Small Business Server Backup Job" /l:s /f "L:\Backup Files\Small Business Server Backup (02).bkf" /UM
NTBACKUP LOG FILE: C:\Documents and Settings\SBS Backup User\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\backup08.log
=====================<BEGIN NTBACKUP LOG FILE>=====================
Backup Status
Operation: Backup
Active backup destination: File
Media name: "Small Business Server Backup (02).bkf created 8/8/2009 at 11:10 AM"

Volume shadow copy creation: Attempt 1.

Error returned while creating the volume shadow copy:0x8004230f.

Error returned while creating the volume shadow copy:8004230f
Aborting Backup.

----------------------

The operation did not successfully complete.

----------------------

=======================<END NTBACKUP LOG FILE>=====================
NTBackup finished the backup with errors.

For more information about failed backups, see the article on troubleshooting your backup at the following Web page: http://go.microsoft.com/fwlink/?LinkId=18414

Backup ended at Saturday, August 08, 2009 11:11 AM
Backup Runner finished.

Author

Commented:
I fixed it. I downlaod mbrwiz to upgardete teh signature. The details can be found this post: Error returned while creating Volume Shadow Copy:0x8004230f  - http://www.chicagotech.net/netforums/viewtopic.php?f=1&t=7083&sid=dd01f39cc962c681046103f9aba37d8e.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial