How to fix VSS errors in Windows Server 2. AIK IT Support. VSS Issues in Windows Server 2. Newer version of OS are giving us all lots of pain – so today i will share How to fix VSS errors in Windows Server 2. VSS Overview. VSS is a set of Component Object Model (COM) application programming interfaces (APIs) that provides standardized interfaces, enabling third- party backup and restoration software to centrally manage the backup and restore operations on a variety of applications. VSS also implements a framework that enables volume backups to be performed while applications on a system continue to write to the volumes. VSS has three components: Requestor—The application that requests the creation of a shadow copy. Provider—The interface that provides the functionality to actually make the shadow copy. Writer—Application- specific software that acts to ensure that application data is ready for shadow copy creation.
Requestors, providers, and writers communicate in the VSS framework to create and restore volume shadow copies. A shadow copy of a volume duplicates all the data held on that volume at one well- defined instant in time. A requestor initiates the backup and restore processes. The provider controls the processes and instructs a writer to prepare a dataset for backup. Describes the StorSimple backup target configuration with Veritas NetBackup. · I have tried several times to install a quicktime package on several clients, if i type this command out in the Packages > program command line it cuts off. When everything is ready, a requestor then instructs a provider to create a shadow copy. Lets See Now : How to fix VSS errors in Windows Server 2. You must be logged into the Server from console or RDP and you need to open command prompttype a command : vssadmin list writers. VSS Writers are listing but there are three writers are in Failed status ( System Writers, WMI Writer & ISS Metabase Writers)Now you need to open regedit and navigate to. HKEY_LOCAL_MACHINESOFTWAREMicrosoft. Event. System{2. 6c. Subscriptions. You need to right click subscription and delete that key ( Note: You must take a backup of registry keys to non os drive when you are doing any changes on system registry)right click and click exportsave it in non os drive in my case its D drive. Now right click the key and select Delete. Click Yes to confirm. Now its deleted. Right- click the following services one at a time. For each service, click Restart: COM+ Event System. COM+ System Application. Microsoft Software Shadow Copy Provider. Volume Shadow Copy. Open command prompt runcd /d %windir%system. Note The last command may not run successfully. All done as per the above image. Right- click the following services one at a time. For each service, click Restart: COM+ Event System. COM+ System Application. Microsoft Software Shadow Copy Provider. Volume Shadow Copywe can see the key is back now. Now you can see the System Writers missing and WMI Writer missingfor System Writer restart Cryptographic servicesfor WMI Writer restart Windows Managment Instrumentation Service. Now you can see System Writers and WMI Writer are stable now but we can not see ISS Metabase Writers missingfor ISS Metabase Writers restart ISS Admin Server but you need to be sure that you can take down the IIS Services on the Server. All VSS Writers are running and stable and please note you may also need a clean reboot which will also be good. Share your Feedback and Remarks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |