After B&R10 uninstall VSS is not working correctly.

 Sorry, i meant B&R10 SBS Edition and not the normal Windows Server Edition.

Hello Martin,

Thank you for your interest in [[http://www.acronis.com/enterprise/ | Acronis Corporate Products]]

Actually, the solution available in the article should have solved the issue.

Could you please follow the steps again to be sure that you have done everything correctly?

If the issue persists, please create a screen shot of the appropriate Registry Editor window (with all values available) and attach to your next post.

If you are not familiar with making screen shots, please read the below step-by-step instructions.

- Get to the window which you want to make a screen shot of;
- Hit the (Alt+)PrintScreen button on your keyboard;
- Run Paint usually available in Start\Programs\Accessories or another graphics application;
- Choose Paste command in Edit menu;
- Save the result picture in JPEG format being preferable.

Thank you.

 Hello,

the problem is, that the article is a little bit old and doesn't really compare to my enviroment. I'm not using Windows Server 2003, Acronis True Image 9.1/Echo or NTBackup. 

I'm using Windows Server 2008 SBS Standard 64bit Edition, Acronis Backup&Recovery 10 SBS Edition, Acronis Exchange Recovery and (for backup to tape) Backup Exec 12.5.

I've uninstalled the Acronis products after the trial period, just a day after our Backup Exec wasn'T able to use VSS on the SBS server.

But here is the screenshot u've wanted.

After configuring this value in the registry editor i've reboot the server.

Maybe this can help you, i used "vssadmin list writers" in the commandline:

[code]

vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes

(C) Copyright 2001-2005 Microsoft Corp.

Auf Reaktion wird gewartet.

Die Reaktion ist möglicherweise verspätet, falls eine Schattenkopie vorbereitet

wird.

Verfassername: "System Writer"

   Verfasserkennung: {e8132975-6f93-4464-a53e-1050253ae220}

   Verfasserinstanzkennung: {8fbb0b49-0c72-444f-a895-104067c11826}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "SqlServerWriter"

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

   Verfasserinstanzkennung: {94a89381-e7fb-497d-89b5-3a98bb8bbd7e}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "FSRM Writer"

   Verfasserkennung: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}

   Verfasserinstanzkennung: {add885bf-2ec8-49a7-bda6-b224d868a8ae}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "IIS Config Writer"

   Verfasserkennung: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

   Verfasserinstanzkennung: {8ccc4f43-791d-4e5f-9adb-5936b6877a20}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "NPS VSS Writer"

   Verfasserkennung: {35e81631-13e1-48db-97fc-d5bc721bb18a}

   Verfasserinstanzkennung: {c00ce803-0ffe-4ed9-b404-de5e96d57cf4}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "ASR Writer"

   Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   Verfasserinstanzkennung: {da4e067c-2764-4ed2-9b99-66b577d81fb7}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Registry Writer"

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

   Verfasserinstanzkennung: {c0f7e973-7256-4b73-ad64-3844b6517265}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Shadow Copy Optimization Writer"

   Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

   Verfasserinstanzkennung: {4a563abb-790a-4ab6-b7fb-06547ad4cce7}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "FRS Writer"

   Verfasserkennung: {d76f5a28-3092-4589-ba48-2958fb88ce29}

   Verfasserinstanzkennung: {4606f3d0-8d07-4890-b3d7-12fab370fdfb}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Dhcp Jet Writer"

   Verfasserkennung: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

   Verfasserinstanzkennung: {0efa5716-0499-4866-8222-7dfd946f7854}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "BITS Writer"

   Verfasserkennung: {4969d978-be47-48b0-b100-f328f07ac1e0}

   Verfasserinstanzkennung: {7f296938-693a-46e6-ac6c-67d572d263d6}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Certificate Authority"

   Verfasserkennung: {6f5b15b5-da24-4d88-b737-63063e3a1f86}

   Verfasserinstanzkennung: {89b34fdd-2bd1-4b8e-88bc-12b9ddcd2c0d}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "WMI Writer"

   Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Verfasserinstanzkennung: {b10d5d89-d53c-45c3-aebb-b972a6b72d56}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "NTDS"

   Verfasserkennung: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

   Verfasserinstanzkennung: {565f1ce1-66cc-4cc7-ac61-480fefc4bb72}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "IIS Metabase Writer"

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

   Verfasserinstanzkennung: {3823af03-61a1-434e-a161-daff617b9800}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "COM+ REGDB Writer"

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

   Verfasserinstanzkennung: {03ec90f3-fbb0-40a2-8879-13109d3cf861}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

Verfassername: "Microsoft Exchange Writer"

   Verfasserkennung: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

   Verfasserinstanzkennung: {9cc7601a-2808-4279-9402-e1b6b03f62ab}

   Status: [1] Stabil

   Letzter Fehler: Kein Fehler

[/code]

Ok, and that is what you get when you type "vssadmin list providers" in the commandline:

[code]

vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes

(C) Copyright 2001-2005 Microsoft Corp.

Anbietername: "Microsoft Software Shadow Copy provider 1.0"

   Anbietertyp: System

   Anbieterkennung: {b5946137-7b9f-4925-af80-51abd60b20d5}

   Version: 1.0.0.7

Anbietername: "Acronis VSS SW Provider"

   Anbietertyp: Software

   Anbieterkennung: {f782463b-33bb-4043-ad8d-60b728d26a6c}

   Version: 1.0

[/code]

Many thanks.

Hello Martin,

Thank you very much for the provided screenshot!

It looks like some traces of our programs were not deleted. Could you please check whether you deleted all registry keys according this article?

Also, please do the following to remove VSS from Components Services:

Start -> Settings -> Control Panel -> Administrative Tools -> Component Services. In the opened window plese expand: Component Services -> Computers -> My Computer -> COM+ Applications. After that, please find Acronis VSS provider and delete it.

Please let us know the results!

We are looking forward to hearing back from you at your earliest convenience.

Thank you.

 Hi again,

i have done all these steps in the article, i've found only 3-4 keys / files, the rest were allready deleted.

But i found this key (and deleted it):

HKEY_LOCAL_MACHINE\CurrentControlSet\Services\VSS\Providers\{f782463b-33bb-4043-ad8d-60b728d26a6c}

Now, when i type "vssadmin list providers" in the command prompt, i get Microsoft as the only VSS provider! Many thanks!

But if it works... we will see after a restart of the SBS 2008 Server in this night... i will let you know if the issue is solved. 

There is one strange thing in the registry-"DWORD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F} -> UpperFilter"... the first time i browsed to this part of the registry (wanted to do the step descriebed in this part of your article http://kb.acronis.com/content/1620) there were no strings set to the DWORD "UpperFilter"... i don't know what this is doing, in your explanations and screenshots i see there are 1 to 3 strings in it, but like i told you i've got none. "PartMgr" or "SnapVol"... i will try now the SnapVol string first.

 Hi all,

ok, it works! Backup Exec can use now MS VSS Provider. 

Many thanks for your advice.

Bye

Martin

Hello Martin,

Thank you for your response.

We are really glad to hear that you have found the solution.

Thank you.

Oleg,

I am sorry my reply will not contain the cheer expressed by other users of the Acronis 10 2008 Server backup application.

I also installed it to try out the features. It did not meet my needs, however another application did. After performing a full uninstall of Acronis, MS VSS fails.

My frunstration is that I did not initially think Acronis was the problem. After 3 days of troubleshooting, reinitializing VSS, etc, I finally reinstalled Acronis.

To my surprise, my other backup applicaiton now worked fine.

Removing Acronis caused other backup applications to fail.

It should be noted that prior to installing the Acronis software, all other backup applicaions worked fine.

It comes down to this. Acronis does not remove itself properly from Windows Server 2008. I had to finally search in these forums to find a soultion.

I ran the command line removal application and rebooted. That did not fix the problme.

I then had to end up using regedt32 to manually remove registry keys. Why Acronis can not do this itself, and requires me to dig around in the registry on a remote server is beyond me.

It's beyond any pratical software that should be sold. Seriously, I will forever discourage the use of any Acronis product in the future. If it can't even remove itself from a computer, I can not imagine the other bugs it posesses.

Acronis has been a huge waste of time for me.

Paul

Hello Paul,

Thank you for your notes.

I will submit a request to the appropriate department concerning the difficulties you have experienced. 

Please do not hesitate to ask additional questions if the provided information is not clear or you need a further assistance. 

Thank you.

Hi guys, I'm also having the same issue. When I try to click on the step by step instruction to remove the registry keys I get access denied so I can view what keys I need to delete from my server. Right now VSS is not working due to Acronis trial being removed. Please help me with this.

I also had these problems after uninstalling, and I'm running a successful backup by searching for and removing the key mentioned above

HKEY_LOCAL_MACHINE\CurrentControlSet\Services\VSS\Providers\{f782463b-33bb-4043-ad8d-60b728d26a6c}

In addition, I did a registry search and removed f782463b-33bb-4043-ad8d-60b728d26a6c which showed up under CurrentControlSet1 and CurrentControlSet2 I believe.

I also ran the clean uninstall utility, but I don't think that did anything helpful http://kb.acronis.com/content/6177

Lastly, I restarted the Volume Shadow Copy service under services.msc and vssadmin list providers is only showing MS, and backup is working

I experienced the same problem with a Backup and Recovery OEM Version. I guess that I solved the issue (the list of providers now only shows the MS), but I can check first after rebooting the server out of business times.

A lot of trouble and work for a problem which is now known since 2 years and not yet solved. I have made my decision to not use acronis products long time ago, but when I got this free OEM version with my NAS, I thought it could be a good idea to give it another chance. FAIL !

Hello John,

Welcome to our Forum, we're glad to greet you here.

We're sorry for you've faced this issue. It was actually fixed in the latest updates of Acronis software, and we haven't heard of it for a while.

You're using an OEM product which is a modified version of our software, but its latest build should also contain the fix for the problem. Please contact your NAS vendor for technical assistance regarding this question.

If the problem remains, please open a new thread with the following information: 

1. Exact sequence of steps performed
2. Detailed issue description
3. Acronis Info from the problem machine

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you.