SqlServerWriter 8 failed Non-retryable error can be easily resolved with Bobcares by your side.
At Bobcares, we offer solutions for every query, big and small, as a part of our SQL Server Support Service.
Let’s take a look at how our Support Team is ready to help customers deal with SqlServerWriter 8 failed Non-retryable error.
How to fix SqlServerWriter 8 failed Non-retryable error
Backups are crucial in many environments. In most cases, database backups are taken by third-party tolls like Netapp, Evault, Avamar, ComVault, and so on. Interestingly, backups fail in some cases due to SQL Server VSS Writer errors. We come across errors like No-retryable error or Timed-Out in these situations.
VSS writers can fail due to different reasons like two or more resources attempting to use the writer at the same time. We can find out which of the writers are in a failed state by running the vssadmin list writers command as an administrator.
We can resolve this issue with the following steps courtesy of our skilled Support Team:
- First, open the command prompt as Administrator and run the following command:
VSSadmin List writers
- The above command results in a list of Writers with their status.
- Next, locate the SqlServerWriter with the status “Failed”. After that head to the services and restart SQL Server VSS Writer.
- Then, restart Volume Shadow Copy and then take a look at the SqlServerWriter status once more.
In case we are still running into the error after following the steps above, we have to reinstall SQL Server Writer.
- First, head to Programs and Features and then uninstall Microsoft VSS Writer for SQL Server.
- Next, head to SQL Server Setup and then install SQL Writer via the “SqlWriter.msi” file.
- Now the status of the Writer will change to Stable.
[Looking for a solution to another query? We are just a click away.]
Conclusion
To sum up, our skilled Support Engineers at Bobcares demonstrated how to resolve SqlServerWriter 8 failed Non-retryable error.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
As we know backup is very critical, in many environments, database backups are taken by a third party tool like, Avamar, Evault, Netapp and ComVault, etc. In such cases, many times backup fails due to SQL Server VSS Writer error. You will see errors like Timed Out or Non-retryable error.
To troubleshoot the issue, you can follow below given steps.
- To check the ‘Writer status’ you need start the Command Prompt with “Run as Administrator” and execute below command.
VSSadmin List writers2. You will see number of Writers with their status.
3. If you see status of “SqlServerWriter” as “Failed“, then go to the services and restart the service “SQL Server VSS Writer”.
4. After that restart the service “Volume Shadow Copy” and then check “SqlServerWriter” status again.
If you are still observing the error, then you need to reinstall the SQL Server Writer. To do that please follow below steps.
- Go to “Program and Features” and uninstall “Microsoft VSS Writer for SQL Server”.
2. Go to your SQL Server Setup and install SQL Writer using “SqlWriter.msi” file.
3. Now check the Writer state again and you should be able to see it as “Stable”.
You can check more information about these VSS writer failureson below Microsoft article.
Various VSS Writer issues
Check all related articles
Здравствуйте!
Пытаюсь сделать архивную копию некоторых папок программой «Veeam Endpoint Backup» архивную копию не делает выдает вот такую ошибку
29.08.2016 15:09:28 :: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}].
Instance ID: [{f089a4e2-a605-4f85-8bcd-f26c21eac837}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
«Система архивации данных Windows Server» архивную копию тоже не создает
В журналах windows «приложение» есть такие ошибки
Событие отклонено модулем записи VSS с ошибкой 0x800423f4, Повторяющаяся ошибка средства записи. Эта ошибка вероятно будет
возникать снова при повторении попытки архивации.
. Изменения компонентов модуля записи, выполненные модулем при обработке события, будут недоступны запрашивающей стороне. Связанные события, поступающие от приложения, в котором размещен модуль записи VSS,
см. в журнале событий.
Операция:
Событие PrepareForSnapshot
Контекст:
Контекст выполнения: Writer
Код класса модуля записи: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Имя модуля записи: SqlServerWriter
Имя экземпляра модуля записи: Microsoft SQL Server 2012:SQLWriter
Код экземпляра модуля записи: {f089a4e2-a605-4f85-8bcd-f26c21eac837}
Командная строка: «C:Program FilesMicrosoft SQL Server90Sharedsqlwriter.exe»
Идентификатор процесса: 1924
Вывод команды sfc /scannow
Начато сканирование системы. Этот процесс может занять некоторое время.
Начало стадии проверки при сканировании системы.
Проверка 100% завершена.
Защита ресурсов Windows не обнаружила нарушений целостности.
Вывод команды vssadmin list writers
VSSADMIN 1.1 — Утилита теневого копирования тома
(C) Корпорация Майкрософт, 2001-2005.
Имя компонента записи: «Task Scheduler Writer»
Id компонента записи: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Id экземпляра компонента записи: {1bddd48e-5052-49db-9b07-b96f96727e6b}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «VSS Metadata Store Writer»
Id компонента записи: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Id экземпляра компонента записи: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «Performance Counters Writer»
Id компонента записи: {0bada1de-01a9-4625-8278-69e735f39dd2}
Id экземпляра компонента записи: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «SqlServerWriter»
Id компонента записи: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Id экземпляра компонента записи: {f089a4e2-a605-4f85-8bcd-f26c21eac837}
Состояние: [8] Неисправен
Последняя ошибка: Неповторяемая ошибка
Имя компонента записи: «System Writer»
Id компонента записи: {e8132975-6f93-4464-a53e-1050253ae220}
Id экземпляра компонента записи: {93d46651-9f1c-44ac-ba08-4a0c23c5fa4d}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «ASR Writer»
Id компонента записи: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Id экземпляра компонента записи: {44caef9a-4f8c-40f2-a0a4-3bb8b87027ad}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «BITS Writer»
Id компонента записи: {4969d978-be47-48b0-b100-f328f07ac1e0}
Id экземпляра компонента записи: {dbe41f83-2443-4ef6-a913-5772313d2f07}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «Registry Writer»
Id компонента записи: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Id экземпляра компонента записи: {20d7710c-cff0-4691-a4ff-30d4e7be94c8}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «COM+ REGDB Writer»
Id компонента записи: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Id экземпляра компонента записи: {3fb2f123-7432-477d-b07e-0bb063cc9469}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «Shadow Copy Optimization Writer»
Id компонента записи: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Id экземпляра компонента записи: {97c6f8a0-62ea-4885-ba5f-48f67a14aa30}
Состояние: [5] Ожидание завершения
Последняя ошибка: Нет ошибок
Имя компонента записи: «WMI Writer»
Id компонента записи: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Id экземпляра компонента записи: {585b97ad-5f52-4b57-88b3-1f764ec40996}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Вывод команды vssadmin List Providers
VSSADMIN 1.1 — Утилита теневого копирования тома
(C) Корпорация Майкрософт, 2001-2005.
Имя поставщика: «Hyper-V IC Software Shadow Copy Provider»
Тип поставщика: Программное обеспечение
Id поставщика: {74600e39-7dc5-4567-a03b-f091d6c7b092}
Версия: 1.0.0.0
Имя поставщика: «Microsoft Software Shadow Copy provider 1.0»
Тип поставщика: Системный
Id поставщика: {b5946137-7b9f-4925-af80-51abd60b20d5}
Версия: 1.0.0.7
Вывод команды vssadmin List ShadowStorage
VSSADMIN 1.1 — Утилита теневого копирования тома
(C) Корпорация Майкрософт, 2001-2005.
Сопоставление хранилища теневой копии
Для тома: (D:)\?Volume{d639b442-8b73-43a5-a5ac-8c6e8e53af7e}
Том хранилища теневой копии: (D:)\?Volume{d639b442-8b73-43a5-a5ac-8c6e8e53af7e}
Использованный объем хранилища теневой копии: 0 B (0%)
Выделенный объем хранилища теневой копии: 0 B (0%)
Максимальный объем хранилища теневой копии: 75 GB (15%)
Из того что уже наковырял:
Сделал Resize ShadowStorage увеличил до 15%
Удалил компонент «Система архивации данных Windows Server»
Регистрировал dll
@echo off
:: Shadow Copy and System Recovery Fix
:: Temporary refreshing pagefile and hyberfil may also help
:: look: http://support.microsoft.com/kb/2506576/ru
:: To generate the problem:
:: regsvr32 /u swprv.dll
:: ======= Stop services: «Volume Shadow Copy» and «MS Software Shadow Copy Provider» ========
cd /d %windir%system32
Net stop vss
Net stop swprv
:: ======= Unregister Block =======
regsvr32 /s /u ole32.dll
regsvr32 /s /u oleaut32.dll
regsvr32 /s /u vss_ps.dll
regsvr32 /s /u swprv.dll
regsvr32 /s /u eventcls.dll
regsvr32 /s /u es.dll
regsvr32 /s /u stdprov.dll
regsvr32 /s /u vssui.dll
regsvr32 /s /u msxml.dll
regsvr32 /s /u msxml3.dll
regsvr32 /s /u msxml4.dll
:: ======= Register Block =========
:: look http://support.microsoft.com/kb/940032/ru
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
:: ======= Trying to run services ====
Net start swprv
Net start vss
echo OK. Please, reboot Windows. & pause
но нет возможности перезагрузить сервер, в работе.
Что еще посмотреть?
Архивная копия папок на диске С: создается без проблем
-
AlexLeadingEdge
- Expert
- Posts: 437
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
A VSS critical writer has failed: SqlServerWriter
I installed a program called ACT! Premium yesterday which uses SQL Server 2014 and since then the backups have failed 55 times (retries).
27-May-16 9:52:43 AM :: Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{76301a1a-85cf-46df-ae7c-b30efafe3afc}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
Running «vssadmin list writers» in command prompt gives this error message:
Writer name: ‘SqlServerWriter’
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {76301a1a-85cf-46df-ae7c-b30efafe3afc}
State: [8] Failed
Last error: Non-retryable error
-
Dima P.
- Product Manager
- Posts: 13914
- Liked: 1453 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by Dima P. » May 27, 2016 2:19 pm
AlexLeadingEdge,
I guess, SQL writer might be stuck in ‘pending for reboot’ state and that’s why you got a backup error. Thanks for sharing!
-
AlexLeadingEdge
- Expert
- Posts: 437
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge » May 29, 2016 9:33 pm
Hi Dmitry,
It was working on Friday after a reboot but it is no longer working again this Monday morning 
The machine was off over the weekend.
30-May-16 8:45:36 AM :: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{a2c4b548-3a8b-4942-a341-00088397b26e}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
Veeam Support — Case # 01811311
-
AlexLeadingEdge
- Expert
- Posts: 437
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge » May 31, 2016 10:21 pm
1 person likes this post
From Konstantin (VEEAM):
I see that you have (or had) another backup software installed, which uses its own provider:
Provider name: ‘StorageCraft Volume Snapshot Software Provider’
Provider type: Software
Provider Id: {24602736-bed9-4619-91b0-243447c6409c}We do not recommend using another backup software side-by-side with Veeam. Please remove this StorageCraft software (if any), or use this link to remove Provider manually — http://hyper-v-backup.backupchain.com/h … -provider/ (please check that you’re removing the correct Id).
Additionally, please run the following command:
vssadmin delete shadows /all
Also there are a lot of errors in Application log with access denied errors.
Please check that SYSTEM account has full permissions to C: drive according to this article — https://technet.microsoft.com/en-us/lib … s.10).aspx
Then restart VSS service once again and try to run a backup.
SYSTEM has Full Control access so nothing to do. I have uninstalled Shadow Protect (old version, not used anyway) and rebooted. VEEAM Endpoint Backup is now running correctly. 
-
AlexLeadingEdge
- Expert
- Posts: 437
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge » Jun 15, 2016 12:06 am
I restarted the SQL Server and it still failed, then rebooted the machine and the whole machine became unresponsive, most likely losing USB keyboard and mouse. By the looks of it a file was installed to C: as «Program» and it caused all third party programs in «Program Files» to fail to start (including the Microsoft Keyboard and Mouse software!). I crashed the computer on restart three times and managed to get it to roll back to before the latest «Critical Update» (two days ago) and it went back to normal. I have renamed the random offending file to «Program1» and it seems to be fine now.
Backup has now run successfully.
-
AlexLeadingEdge
- Expert
- Posts: 437
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge » Jun 16, 2016 2:28 am
I have just uploaded it to Virus Total (https://www.virustotal.com/) to scan the file with all the major antivirus products. Only one said it was a threat (DrWeb called it «DLOADER.Trojan») but all the rest say it is ok. Virus Total gave it a 100 out of 100 for safety.
It says it is related to WRDATA, which is the folder that Webroot Antivirus uses to store its database and update files. By the looks of it Webroot has tried to update and failed, leaving a badly formed install 
-
AlexLeadingEdge
- Expert
- Posts: 437
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge » Jun 16, 2016 4:44 am
It has done it again
16-Jun-16 3:23:41 PM :: Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{c2950dc7-2afe-4bd0-8c0e-6e1fe062b780}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
-
mcrape
- Veeam Software
- Posts: 65
- Liked: 20 times
- Joined: Jun 27, 2011 7:39 pm
- Full Name: Matt Crape
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by mcrape » Aug 11, 2016 2:12 am
1 person likes this post
I had a similar issue, but mine involved the SQL VSS writer failing at install (see here).
My issue turned out that I had an old and / or corrupt dll (msvcr100.dll) in c:windowssystem32. I ended up renaming that file re-installing without issue. Not sure if it is the same issue, but it sounds similar so I thought I would chime in.
-
AlexLeadingEdge
- Expert
- Posts: 437
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge » Aug 11, 2016 4:33 am
mcrape wrote:I had a similar issue, but mine involved the SQL VSS writer failing at install (see here).
My issue turned out that I had an old and / or corrupt dll (msvcr100.dll) in c:windowssystem32. I ended up renaming that file re-installing without issue. Not sure if it is the same issue, but it sounds similar so I thought I would chime in.
Thank you, any help is always appreciated It appears to be related to a program we use called ACT! Premium, that installs SQL Server. It seems to install it badly, and when ACT! Premium is uninstalled it leaves the SQL Server in place so removing ACT! Premium doesn’t even fix the issue 
-
cmeis
- Lurker
- Posts: 2
- Liked: never
- Joined: Aug 17, 2016 10:25 am
- Full Name: Christian Meis
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by cmeis » Aug 17, 2016 10:29 am
Hello AlexLeadingEdge,
I’m fighting with the same problem, which is also occuring on workstations which have Act installed and are to be backuped by Veeam Endpoint Backup.
What did you do to make the VSS errors go away? Or do you have any further information about what the Act installer does «badly» when installing the SQL server (express)?
I have about 15 machines with failing backups due to this error now :-/
Any hints are warmly welcomed! 
Best regards,
Christian
-
AlexLeadingEdge
- Expert
- Posts: 437
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge » Aug 19, 2016 2:53 am
1 person likes this post
I uninstalled ACT; I wish I were kidding but it was a constant headache. I didn’t have the time or the inclination to figure it out, the trial period had expired and it couldn’t do everything we wanted it to do in the trial period time, and ACT were unwilling to give us an extension to the trial time. I then turned off the Sql Server VSS Writer under Services. VEEAM seems to need it running (without ACT) or turned off (maybe it turns it back on using its own conditions?), no idea why this works. A simple reboot didn’t seem to fix the error.
I also found that ACT blocked certain mapped drive folders from opening, giving me an eternal «Working on it…». Uninstalling ACT fixed that problem too.
-
Dima P.
- Product Manager
- Posts: 13914
- Liked: 1453 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by Dima P. » Jan 25, 2017 10:08 pm
Bruce,
Share you pain – our support team has to fix issues cause by this tool from time to time. Glad you are up and running now.
-
Bellsys2765
- Lurker
- Posts: 1
- Liked: 2 times
- Joined: Apr 06, 2017 2:01 am
- Full Name: Artie Maas
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by Bellsys2765 » Apr 06, 2017 2:16 am
2 people like this post
I know this is a old post but I recently ran in to the same issue with ACT, I was able to find this simple fix at the ACT forum Thanks to Andyman49 
https://community.act.com/t5/Act/Instal … 748/page/2
The problem is with permission set for ACT SQL instance needs to be change to Local Service from Local System
Control Panel
Administrative Tools
Computer Management
Services and Applications
SQL Server Configuration Manager
SQL Server Services
SQL Server(ACT7)
Change Log On from Built-in account: Local System to Built-in account: Local Service
-
brewcrew
- Lurker
- Posts: 1
- Liked: never
- Joined: May 22, 2017 8:14 pm
- Full Name: brewcrew
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by brewcrew » May 22, 2017 8:17 pm
Thank you for posting this here! I was having this problem since we setup a new ACT server on our VMWare host. The old ACT server backed up fine, but the new one would error out with this error. Changing the service did the trick for us!
-
LeifGunnar
- Lurker
- Posts: 1
- Liked: never
- Joined: Jun 12, 2017 8:46 am
- Full Name: Leif Gunnar Einmo
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by LeifGunnar » Jun 12, 2017 8:51 am
Hi AlexLeadingEdge & cmeis
Did you manage to resolv this issu regerading Veeam Endpoint Backup and the ACT software ??
Have a issue with one window 7 WS with ACT installed.
Thanks
Leif Gunnar
-
Mike Resseler
- Product Manager
- Posts: 7882
- Liked: 1203 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by Mike Resseler » Jun 13, 2017 5:28 am
Hi Leif,
The solution from BellSys2756 seems to work fine. If not, you can always contact our support department. (In that case, post the case ID and follow-up here) as they have fixed these already a few times (see post of Dima)
Cheers
Mike
-
Justin Hemming
- Lurker
- Posts: 1
- Liked: never
- Joined: Apr 19, 2018 2:16 pm
- Full Name: Justin Hemming
- Contact:
-
stubbint
- Service Provider
- Posts: 7
- Liked: 2 times
- Joined: Oct 13, 2011 2:14 pm
- Full Name: Trevor Stubbins
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by stubbint » Apr 11, 2019 5:04 pm
The same thing just happened to me. I’ve been backing up my laptop with Veeam for years and today is the first time I’ve seen this error. As far as I know, nothing has changed on the laptop. A reboot didn’t fix it, but stopping the SQL VSS writer service allows Veeam backup to run.
-
tom11011
- Expert
- Posts: 191
- Liked: 9 times
- Joined: Dec 01, 2010 8:40 pm
- Full Name: Tom
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by tom11011 » Jul 26, 2019 2:50 am
1 person likes this post
Hey group, I ran across this post and thought I would throw my 2 cents in.
I am running a development citrix server with its own database server installed. The problem began when a recent citrix upgrade had upgraded the SQL Express server from 2012 to 2014. After that, I was getting daily Veeam warnings as indicated by the original poster.
I tried the recommendation in this post of changing Network Service to Local Service but that didn’t work, nothing changed. But when I changed the SQL Service logon to the top circle «Local System», that seemed to fix it. No more warnings from Veeam.
Who is online
Users browsing this forum: No registered users and 26 guests
I am having some troubles with the Sql VSS writer. I am using a 3rd party backup solution, and it is failing because each time a snapshot is attempted the writer (SqlServerWriter) fails with a non-retryable error. The same thing happens with the built in
Windows Server Backup utility. There are a few notable entries in the Event Logs on the server. One names error 0x800423f4, the other0x80070005, which is an access denied error. Trouble is, the writer is set to run under the local system account, and the local
system account has SysAdmin privileges on the databases. I’ve spent quite a few hours over the past week or two attempting to solve this and have had no luck. Any ideas where this writer is failing? This is a SQL 2008r2 install.
Thanks,
Josh
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 18210
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BackupVirtualDeviceSet::Initialize: CoCreateInstance failure on backup device '{730A7E71-C123-4F80-A1E3-DEF2BDE8E112}3'. Operating system error 0x80070005(Access is denied.).
—————————————————————————————————————————————————————————————————————————————
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: SQL Server 2008 R2:SQLWriter
Writer Instance ID: {e37d5783-6dd3-4bde-ae44-c179982fb65b}
Command Line: "C:Program FilesMicrosoft SQL Server90Sharedsqlwriter.exe"
Process ID: 8984
—————————————————————————————————————————————————————————————————————————————
This is what the ‘vssadmin list writers’ command turns up for the SQL Writer after an attempted snapshot. Only way to recover it is to restart the server.
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {ac3d731f-6a0f-4537-8d6f-1ffad6dd9d8f}
State: [8] Failed
Last error: Non-retryable error
-
Edited by
Thursday, July 14, 2011 1:14 PM
readability
SqlServerWriter 8 failed Non-retryable error can be easily resolved with Bobcares by your side.
At Bobcares, we offer solutions for every query, big and small, as a part of our SQL Server Support Service.
Let’s take a look at how our Support Team is ready to help customers deal with SqlServerWriter 8 failed Non-retryable error.
How to fix SqlServerWriter 8 failed Non-retryable error
Backups are crucial in many environments. In most cases, database backups are taken by third-party tolls like Netapp, Evault, Avamar, ComVault, and so on. Interestingly, backups fail in some cases due to SQL Server VSS Writer errors. We come across errors like No-retryable error or Timed-Out in these situations.
VSS writers can fail due to different reasons like two or more resources attempting to use the writer at the same time. We can find out which of the writers are in a failed state by running the vssadmin list writers command as an administrator.
We can resolve this issue with the following steps courtesy of our skilled Support Team:
- First, open the command prompt as Administrator and run the following command:
VSSadmin List writers
- The above command results in a list of Writers with their status.
- Next, locate the SqlServerWriter with the status “Failed”. After that head to the services and restart SQL Server VSS Writer.
- Then, restart Volume Shadow Copy and then take a look at the SqlServerWriter status once more.
In case we are still running into the error after following the steps above, we have to reinstall SQL Server Writer.
- First, head to Programs and Features and then uninstall Microsoft VSS Writer for SQL Server.
- Next, head to SQL Server Setup and then install SQL Writer via the “SqlWriter.msi” file.
- Now the status of the Writer will change to Stable.
[Looking for a solution to another query? We are just a click away.]
Conclusion
To sum up, our skilled Support Engineers at Bobcares demonstrated how to resolve SqlServerWriter 8 failed Non-retryable error.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
-
AlexLeadingEdge
- Veteran
- Posts: 446
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
A VSS critical writer has failed: SqlServerWriter
I installed a program called ACT! Premium yesterday which uses SQL Server 2014 and since then the backups have failed 55 times (retries).
27-May-16 9:52:43 AM :: Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{76301a1a-85cf-46df-ae7c-b30efafe3afc}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
Running «vssadmin list writers» in command prompt gives this error message:
Writer name: ‘SqlServerWriter’
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {76301a1a-85cf-46df-ae7c-b30efafe3afc}
State: [8] Failed
Last error: Non-retryable error
-
Dima P.
- Product Manager
- Posts: 14024
- Liked: 1496 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by Dima P. »
AlexLeadingEdge,
I guess, SQL writer might be stuck in ‘pending for reboot’ state and that’s why you got a backup error. Thanks for sharing!
-
AlexLeadingEdge
- Veteran
- Posts: 446
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
-
Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge »
Hi Dmitry,
It was working on Friday after a reboot but it is no longer working again this Monday morning The machine was off over the weekend.
30-May-16 8:45:36 AM :: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{a2c4b548-3a8b-4942-a341-00088397b26e}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
Veeam Support — Case # 01811311
-
AlexLeadingEdge
- Veteran
- Posts: 446
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge »
1 person likes this post
From Konstantin (VEEAM):
I see that you have (or had) another backup software installed, which uses its own provider:
Provider name: ‘StorageCraft Volume Snapshot Software Provider’
Provider type: Software
Provider Id: {24602736-bed9-4619-91b0-243447c6409c}We do not recommend using another backup software side-by-side with Veeam. Please remove this StorageCraft software (if any), or use this link to remove Provider manually — http://hyper-v-backup.backupchain.com/h … -provider/ (please check that you’re removing the correct Id).
Additionally, please run the following command:
vssadmin delete shadows /all
Also there are a lot of errors in Application log with access denied errors.
Please check that SYSTEM account has full permissions to C:\ drive according to this article — https://technet.microsoft.com/en-us/lib … s.10).aspx
Then restart VSS service once again and try to run a backup.
SYSTEM has Full Control access so nothing to do. I have uninstalled Shadow Protect (old version, not used anyway) and rebooted. VEEAM Endpoint Backup is now running correctly.
-
AlexLeadingEdge
- Veteran
- Posts: 446
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge »
I restarted the SQL Server and it still failed, then rebooted the machine and the whole machine became unresponsive, most likely losing USB keyboard and mouse. By the looks of it a file was installed to C:\ as «Program» and it caused all third party programs in «Program Files» to fail to start (including the Microsoft Keyboard and Mouse software!). I crashed the computer on restart three times and managed to get it to roll back to before the latest «Critical Update» (two days ago) and it went back to normal. I have renamed the random offending file to «Program1» and it seems to be fine now.
Backup has now run successfully.
-
AlexLeadingEdge
- Veteran
- Posts: 446
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge »
I have just uploaded it to Virus Total (https://www.virustotal.com/) to scan the file with all the major antivirus products. Only one said it was a threat (DrWeb called it «DLOADER.Trojan») but all the rest say it is ok. Virus Total gave it a 100 out of 100 for safety.
It says it is related to WRDATA, which is the folder that Webroot Antivirus uses to store its database and update files. By the looks of it Webroot has tried to update and failed, leaving a badly formed install
-
AlexLeadingEdge
- Veteran
- Posts: 446
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge »
It has done it again
16-Jun-16 3:23:41 PM :: Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{c2950dc7-2afe-4bd0-8c0e-6e1fe062b780}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
-
mcrape
- Veeam Software
- Posts: 65
- Liked: 20 times
- Joined: Jun 27, 2011 7:39 pm
- Full Name: Matt Crape
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by mcrape »
1 person likes this post
I had a similar issue, but mine involved the SQL VSS writer failing at install (see here).
My issue turned out that I had an old and / or corrupt dll (msvcr100.dll) in c:\windows\system32\. I ended up renaming that file re-installing without issue. Not sure if it is the same issue, but it sounds similar so I thought I would chime in.
-
AlexLeadingEdge
- Veteran
- Posts: 446
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge »
mcrape wrote:I had a similar issue, but mine involved the SQL VSS writer failing at install (see here).
My issue turned out that I had an old and / or corrupt dll (msvcr100.dll) in c:\windows\system32\. I ended up renaming that file re-installing without issue. Not sure if it is the same issue, but it sounds similar so I thought I would chime in.
Thank you, any help is always appreciated It appears to be related to a program we use called ACT! Premium, that installs SQL Server. It seems to install it badly, and when ACT! Premium is uninstalled it leaves the SQL Server in place so removing ACT! Premium doesn’t even fix the issue
-
cmeis
- Lurker
- Posts: 2
- Liked: never
- Joined: Aug 17, 2016 10:25 am
- Full Name: Christian Meis
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by cmeis »
Hello AlexLeadingEdge,
I’m fighting with the same problem, which is also occuring on workstations which have Act installed and are to be backuped by Veeam Endpoint Backup.
What did you do to make the VSS errors go away? Or do you have any further information about what the Act installer does «badly» when installing the SQL server (express)?
I have about 15 machines with failing backups due to this error now :-/
Any hints are warmly welcomed!
Best regards,
Christian
-
AlexLeadingEdge
- Veteran
- Posts: 446
- Liked: 56 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by AlexLeadingEdge »
1 person likes this post
I uninstalled ACT; I wish I were kidding but it was a constant headache. I didn’t have the time or the inclination to figure it out, the trial period had expired and it couldn’t do everything we wanted it to do in the trial period time, and ACT were unwilling to give us an extension to the trial time. I then turned off the Sql Server VSS Writer under Services. VEEAM seems to need it running (without ACT) or turned off (maybe it turns it back on using its own conditions?), no idea why this works. A simple reboot didn’t seem to fix the error.
I also found that ACT blocked certain mapped drive folders from opening, giving me an eternal «Working on it…». Uninstalling ACT fixed that problem too.
-
Dima P.
- Product Manager
- Posts: 14024
- Liked: 1496 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by Dima P. »
Bruce,
Share you pain – our support team has to fix issues cause by this tool from time to time. Glad you are up and running now.
-
Bellsys2765
- Lurker
- Posts: 1
- Liked: 2 times
- Joined: Apr 06, 2017 2:01 am
- Full Name: Artie Maas
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by Bellsys2765 »
2 people like this post
I know this is a old post but I recently ran in to the same issue with ACT, I was able to find this simple fix at the ACT forum Thanks to Andyman49
https://community.act.com/t5/Act/Instal … 748/page/2
The problem is with permission set for ACT SQL instance needs to be change to Local Service from Local System
Control Panel
Administrative Tools
Computer Management
Services and Applications
SQL Server Configuration Manager
SQL Server Services
SQL Server(ACT7)
Change Log On from Built-in account: Local System to Built-in account: Local Service
-
brewcrew
- Lurker
- Posts: 1
- Liked: never
- Joined: May 22, 2017 8:14 pm
- Full Name: brewcrew
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by brewcrew »
Thank you for posting this here! I was having this problem since we setup a new ACT server on our VMWare host. The old ACT server backed up fine, but the new one would error out with this error. Changing the service did the trick for us!
-
LeifGunnar
- Lurker
- Posts: 1
- Liked: never
- Joined: Jun 12, 2017 8:46 am
- Full Name: Leif Gunnar Einmo
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by LeifGunnar »
Hi AlexLeadingEdge & cmeis
Did you manage to resolv this issu regerading Veeam Endpoint Backup and the ACT software ??
Have a issue with one window 7 WS with ACT installed.
Thanks
Leif Gunnar
-
Mike Resseler
- Product Manager
- Posts: 7951
- Liked: 1233 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by Mike Resseler »
Hi Leif,
The solution from BellSys2756 seems to work fine. If not, you can always contact our support department. (In that case, post the case ID and follow-up here) as they have fixed these already a few times (see post of Dima)
Cheers
Mike
-
Justin Hemming
- Lurker
- Posts: 1
- Liked: never
- Joined: Apr 19, 2018 2:16 pm
- Full Name: Justin Hemming
- Contact:
-
stubbint
- Service Provider
- Posts: 7
- Liked: 2 times
- Joined: Oct 13, 2011 2:14 pm
- Full Name: Trevor Stubbins
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by stubbint »
The same thing just happened to me. I’ve been backing up my laptop with Veeam for years and today is the first time I’ve seen this error. As far as I know, nothing has changed on the laptop. A reboot didn’t fix it, but stopping the SQL VSS writer service allows Veeam backup to run.
-
tom11011
- Expert
- Posts: 191
- Liked: 9 times
- Joined: Dec 01, 2010 8:40 pm
- Full Name: Tom
- Contact:
Re: A VSS critical writer has failed: SqlServerWriter
Post
by tom11011 »
1 person likes this post
Hey group, I ran across this post and thought I would throw my 2 cents in.
I am running a development citrix server with its own database server installed. The problem began when a recent citrix upgrade had upgraded the SQL Express server from 2012 to 2014. After that, I was getting daily Veeam warnings as indicated by the original poster.
I tried the recommendation in this post of changing Network Service to Local Service but that didn’t work, nothing changed. But when I changed the SQL Service logon to the top circle «Local System», that seemed to fix it. No more warnings from Veeam.
Who is online
Users browsing this forum: No registered users and 37 guests
I am having some troubles with the Sql VSS writer. I am using a 3rd party backup solution, and it is failing because each time a snapshot is attempted the writer (SqlServerWriter) fails with a non-retryable error. The same thing happens with the built in
Windows Server Backup utility. There are a few notable entries in the Event Logs on the server. One names error 0x800423f4, the other0x80070005, which is an access denied error. Trouble is, the writer is set to run under the local system account, and the local
system account has SysAdmin privileges on the databases. I’ve spent quite a few hours over the past week or two attempting to solve this and have had no luck. Any ideas where this writer is failing? This is a SQL 2008r2 install.
Thanks,
Josh
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 18210
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BackupVirtualDeviceSet::Initialize: CoCreateInstance failure on backup device '{730A7E71-C123-4F80-A1E3-DEF2BDE8E112}3'. Operating system error 0x80070005(Access is denied.).
—————————————————————————————————————————————————————————————————————————————
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: SQL Server 2008 R2:SQLWriter
Writer Instance ID: {e37d5783-6dd3-4bde-ae44-c179982fb65b}
Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
Process ID: 8984
—————————————————————————————————————————————————————————————————————————————
This is what the ‘vssadmin list writers’ command turns up for the SQL Writer after an attempted snapshot. Only way to recover it is to restart the server.
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {ac3d731f-6a0f-4537-8d6f-1ffad6dd9d8f}
State: [8] Failed
Last error: Non-retryable error
-
Edited by
Thursday, July 14, 2011 1:14 PM
readability
Здравствуйте!
Пытаюсь сделать архивную копию некоторых папок программой «Veeam Endpoint Backup» архивную копию не делает выдает вот такую ошибку
29.08.2016 15:09:28 :: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}].
Instance ID: [{f089a4e2-a605-4f85-8bcd-f26c21eac837}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
«Система архивации данных Windows Server» архивную копию тоже не создает
В журналах windows «приложение» есть такие ошибки
Событие отклонено модулем записи VSS с ошибкой 0x800423f4, Повторяющаяся ошибка средства записи. Эта ошибка вероятно будет
возникать снова при повторении попытки архивации.
. Изменения компонентов модуля записи, выполненные модулем при обработке события, будут недоступны запрашивающей стороне. Связанные события, поступающие от приложения, в котором размещен модуль записи VSS,
см. в журнале событий.
Операция:
Событие PrepareForSnapshot
Контекст:
Контекст выполнения: Writer
Код класса модуля записи: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Имя модуля записи: SqlServerWriter
Имя экземпляра модуля записи: Microsoft SQL Server 2012:SQLWriter
Код экземпляра модуля записи: {f089a4e2-a605-4f85-8bcd-f26c21eac837}
Командная строка: «C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe»
Идентификатор процесса: 1924
Вывод команды sfc /scannow
Начато сканирование системы. Этот процесс может занять некоторое время.
Начало стадии проверки при сканировании системы.
Проверка 100% завершена.
Защита ресурсов Windows не обнаружила нарушений целостности.
Вывод команды vssadmin list writers
VSSADMIN 1.1 — Утилита теневого копирования тома
(C) Корпорация Майкрософт, 2001-2005.
Имя компонента записи: «Task Scheduler Writer»
Id компонента записи: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Id экземпляра компонента записи: {1bddd48e-5052-49db-9b07-b96f96727e6b}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «VSS Metadata Store Writer»
Id компонента записи: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Id экземпляра компонента записи: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «Performance Counters Writer»
Id компонента записи: {0bada1de-01a9-4625-8278-69e735f39dd2}
Id экземпляра компонента записи: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «SqlServerWriter»
Id компонента записи: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Id экземпляра компонента записи: {f089a4e2-a605-4f85-8bcd-f26c21eac837}
Состояние: [8] Неисправен
Последняя ошибка: Неповторяемая ошибка
Имя компонента записи: «System Writer»
Id компонента записи: {e8132975-6f93-4464-a53e-1050253ae220}
Id экземпляра компонента записи: {93d46651-9f1c-44ac-ba08-4a0c23c5fa4d}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «ASR Writer»
Id компонента записи: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Id экземпляра компонента записи: {44caef9a-4f8c-40f2-a0a4-3bb8b87027ad}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «BITS Writer»
Id компонента записи: {4969d978-be47-48b0-b100-f328f07ac1e0}
Id экземпляра компонента записи: {dbe41f83-2443-4ef6-a913-5772313d2f07}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «Registry Writer»
Id компонента записи: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Id экземпляра компонента записи: {20d7710c-cff0-4691-a4ff-30d4e7be94c8}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «COM+ REGDB Writer»
Id компонента записи: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Id экземпляра компонента записи: {3fb2f123-7432-477d-b07e-0bb063cc9469}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Имя компонента записи: «Shadow Copy Optimization Writer»
Id компонента записи: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Id экземпляра компонента записи: {97c6f8a0-62ea-4885-ba5f-48f67a14aa30}
Состояние: [5] Ожидание завершения
Последняя ошибка: Нет ошибок
Имя компонента записи: «WMI Writer»
Id компонента записи: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Id экземпляра компонента записи: {585b97ad-5f52-4b57-88b3-1f764ec40996}
Состояние: [1] Стабильный
Последняя ошибка: Нет ошибок
Вывод команды vssadmin List Providers
VSSADMIN 1.1 — Утилита теневого копирования тома
(C) Корпорация Майкрософт, 2001-2005.
Имя поставщика: «Hyper-V IC Software Shadow Copy Provider»
Тип поставщика: Программное обеспечение
Id поставщика: {74600e39-7dc5-4567-a03b-f091d6c7b092}
Версия: 1.0.0.0
Имя поставщика: «Microsoft Software Shadow Copy provider 1.0»
Тип поставщика: Системный
Id поставщика: {b5946137-7b9f-4925-af80-51abd60b20d5}
Версия: 1.0.0.7
Вывод команды vssadmin List ShadowStorage
VSSADMIN 1.1 — Утилита теневого копирования тома
(C) Корпорация Майкрософт, 2001-2005.
Сопоставление хранилища теневой копии
Для тома: (D:)\\?\Volume{d639b442-8b73-43a5-a5ac-8c6e8e53af7e}\
Том хранилища теневой копии: (D:)\\?\Volume{d639b442-8b73-43a5-a5ac-8c6e8e53af7e}\
Использованный объем хранилища теневой копии: 0 B (0%)
Выделенный объем хранилища теневой копии: 0 B (0%)
Максимальный объем хранилища теневой копии: 75 GB (15%)
Из того что уже наковырял:
Сделал Resize ShadowStorage увеличил до 15%
Удалил компонент «Система архивации данных Windows Server»
Регистрировал dll
@echo off
:: Shadow Copy and System Recovery Fix
:: Temporary refreshing pagefile and hyberfil may also help
:: look: http://support.microsoft.com/kb/2506576/ru
:: To generate the problem:
:: regsvr32 /u swprv.dll
:: ======= Stop services: «Volume Shadow Copy» and «MS Software Shadow Copy Provider» ========
cd /d %windir%\system32
Net stop vss
Net stop swprv
:: ======= Unregister Block =======
regsvr32 /s /u ole32.dll
regsvr32 /s /u oleaut32.dll
regsvr32 /s /u vss_ps.dll
regsvr32 /s /u swprv.dll
regsvr32 /s /u eventcls.dll
regsvr32 /s /u es.dll
regsvr32 /s /u stdprov.dll
regsvr32 /s /u vssui.dll
regsvr32 /s /u msxml.dll
regsvr32 /s /u msxml3.dll
regsvr32 /s /u msxml4.dll
:: ======= Register Block =========
:: look http://support.microsoft.com/kb/940032/ru
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
:: ======= Trying to run services ====
Net start swprv
Net start vss
echo OK. Please, reboot Windows. & pause
но нет возможности перезагрузить сервер, в работе.
Что еще посмотреть?
Архивная копия папок на диске С: создается без проблем