Hey community,

i`m reading these topics since years. All issues could be resolved so far. But since yesterday i`m really afraid. I think i can`t solve this issue without you specialists.

I´m running a Hyper V (Server 2012 R2 Core) with currently three VM`s on it.
I like to initiate a host based backup with "wbadmin".

The used command ist: wbadmin start backup -backupTarget:B:\ -hyperv:"VMS030"

The VM has three disks: Fast Storage 400gb, Slow Storage 500 GB, Paging on SSD`s 15 gb.
I assigned 30.720 megabytes of RAM to this VM.

The other VM`s are much smaller. The Backup is working on these VM`s without any errors.
Now... what`s special about this VM? The VM is a SBS2011 with Exchange, SQL Server and AD on it.

The wbadmin command fails with

Detaillierter Fehler: FEHLER - Vorgangsfehler im Volumeschattenkopie-Dienst (0x8
00423f4)
Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der
Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.

I´m looking for a workaround or a fix since hours on different error-ids. But cannot resolve it.
There WindowsServerBackup-Log tells me this:

Fehler des Writers
Writer-ID: "{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}"
Instanz-ID: "{02FFB0A1-6658-4EBF-A79E-ACD7C00038BB}"
Name des Writers: "Microsoft Hyper-V VSS Writer"
Status des Writers: "8"
Fehlerergebnis: "800423F4"
Anwendungsergebnis: "80004005"
Anwendungsmeldung: "(null)"
   Komponente: "1415E5AA-E823-4586-A84D-CF3DB849E8B4"
   Logischer Pfad: "(null)"
   Komponentenergebnis: "800423F4"
   Komponentenmeldung: (null)
       Dateiangabe: "A:\Virtual Machines\\1415E5AA-E823-4586-A84D-CF3DB849E8B4.xml", rekursiv: "0"
       Dateiangabe: "A:\\vms030.vhdx", rekursiv: "0"
       Dateiangabe: "P:\\vms030-pagin.vhdx", rekursiv: "0"
       Dateiangabe: "R:\\vms030-ressources.vhdx", rekursiv: "0"
       Dateiangabe: "A:\Snapshots\F60A2B69-C801-4656-AF69-6C4643FCA18D.xml", rekursiv: "0"
       Dateiangabe: "A:\Snapshots\F60A2B69-C801-4656-AF69-6C4643FCA18D\*", rekursiv: "0"
       Dateiangabe: "A:\\vms030_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
       Dateiangabe: "P:\\vms030-pagin_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
       Dateiangabe: "R:\\vms030-ressources_F60A2B69-C801-4656-AF69-6C4643FCA18D.avhdx", rekursiv: "0"
*-----------------------------*


Anwendungssicherung
Writer-ID: "{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}"
   Komponente: "1415E5AA-E823-4586-A84D-CF3DB849E8B4"
   Beschreibung     : Offline\VMS030
   Logischer Pfad: ""
   Fehler           : 80780175
   Fehlermeldung   : Eine Komponente wurde bei der Schattenkopie des Volumes übersprungen.

   Detaillierter Fehler  : 800423F4
   Detaillierte Fehlermeldung : Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.

This is the output of Backup Logs in Event Viewer

Die Beschreibung für die Ereignis-ID "5" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

EV_RenderedValue_0,00
2155348041
0
%%2155348041
12
06.12.2014 09:58:00
B:
0
<VolumeInfo></VolumeInfo>
06.12.2014 09:58:00
06.12.2014 09:58:28<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
01.01.1601 00:00:00
01.01.1601 00:00:00<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
19<ComponentStatus><ComponentStatusItem Name="1415E5AA-E823-4586-A84D-CF3DB849E8B4" LogicalPath="" Caption="Offline\VMS030" AppId="HyperV" WriterId="{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}" InstanceId="{02ffb0a1-6658-4ebf-a79e-acd7c00038bb}" ConsistencyCheckResult="-2139618955" ConsistencyCheckResultDetailed="-2147212300"/></ComponentStatus><ComponentInfo><ComponentInfoItem WriterId="{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}" InstanceId="{02ffb0a1-6658-4ebf-a79e-acd7c00038bb}" Name="1415E5AA-E823-4586-A84D-CF3DB849E8B4" LogicalPath="" Caption="Offline\VMS030" AppName="HyperV" hResult="-2139618955" hDetailedResult="-2147212300" IsFullBackup="1" FullBackupReason="0" Size="0" DataTransferred="0" TotalNoOfFiles="0" /></ComponentInfo>
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00
01.01.1601 00:00:00<SystemState IsPresent="0" HResult="0" DetailedHResult="0" /><BMR IsPresent="0" HResult="0" DetailedHResult="0" />
False
False
False
C:\Windows\Logs\WindowsServerBackup\Backup-06-12-2014_09-58-00.log
C:\Windows\Logs\WindowsServerBackup\Backup_Error-06-12-2014_09-58-00.log<TimesList></TimesList><TimesList></TimesList><TimesList></TimesList><TimesList></TimesList>
5<ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="1" SucceededComponents="0" />

Das Handle ist ungültig

And finally the Apps Errorlog from Eventviewer:

Die Beschreibung für die Ereignis-ID "1001" aus der Quelle "Windows Error Reporting" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0
Windows Server Backup Error
Nicht verfügbar
0
2
1
0x80780049
0x00000000
0x00000000
0x00000000
0x00000000
0x800423f4
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_13a53d7aa8e7829769665e4df6f1cf697e2cbfe_00000000_17a9bb93
0
6f6092af-7d2e-11e4-8144-c860008e5417
4100

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "517" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

06.12.2014 09:58:00
2155348041
%%2155348041

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "8224" aus der Quelle "VSS" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:


Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "517" aus der Quelle "Microsoft-Windows-Backup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

06.12.2014 09:58:00
2155348041
%%2155348041

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "1001" aus der Quelle "Windows Error Reporting" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0
Windows Server Backup Error
Nicht verfügbar
0
2
1
0x80780049
0x00000000
0x00000000
0x00000000
0x00000000
0x800423f4
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_13a53d7aa8e7829769665e4df6f1cf697e2cbfe_00000000_17a9bb93
0
6f6092af-7d2e-11e4-8144-c860008e5417
4100

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "16387" aus der Quelle "SPP" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

Microsoft Hyper-V VSS Writer
Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird, tritt der Fehler höchstwahrscheinlich erneut auf. (0x800423F4)
Unbekannter Fehler (0x80004005)

Das Handle ist ungültig

Die Beschreibung für die Ereignis-ID "8229" aus der Quelle "VSS" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

0x800423f4, Für den Generator wurde ein nicht vorübergehender Fehler festgestellt. Wenn der Sicherungsvorgang wiederholt wird,
tritt der Fehler höchstwahrscheinlich erneut auf.



Vorgang:
   PrepareForSnapshot-Ereignis

Kontext:
   Ausführungskontext: Writer
   Generatorklassen-ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Generatorname: Microsoft Hyper-V VSS Writer
   Generatorinstanz-ID: {02ffb0a1-6658-4ebf-a79e-acd7c00038bb}
   Befehlszeile: C:\Windows\system32\vmms.exe
   Prozess-ID: 1852

Das Handle ist ungültig

Do you guy`s have any clue how i can resolve this?

As i said ... i can backup a few smaller VM`s. Only the "Big one" fails.
I already thought about a disk space issue ... But there is at least 30 % of free space on each disk.

Thank you all!

Hello

i have HP server ( Windows server 2012 r2 )
some problems in my systems and i want to make format to the server and i have 6 Hyper -v Licenses
but if i make format and install the windows server a gain how can i get my windows server Licenses ?

thanks 

Host and VMs:  Server 2012 (Fully patched and unfortunatey not R2).

When this occurs the VM becomes unresponsive for a period of time and then this error is generated on host.  The other VM remains responsive w/o error at any point.  No backups or shadow copies should be taking place at this time and I've confirmed as much.  Backups are always successful when they run.  Have a bit of a strange setup here (Not designed by me).  Have two RAID arrays.  One is the C: partition at 275GB w/ 79GB free and the other is 557GB and it is offline and passed through to the VM as the SQL data drive.  This is how it was done and unfortunately how it needs to remain.  I do not get the below error daily but it does happen a few times a month but the time/day is never consistent.  Oddly though the VM isn't always unresponsive (At least the customer doesn't contact me if it is) when this error is generated.  Other day errors are exact except the VolumeShadowCopy number is different (See error below and you'll understand what I mean).  I have a sneaking suspicion that the issues is due to the lack of enough space to create a shadow copy of the VM on Host C: but I don't know why this wouldn't occur every day if that was in fact the issue.

The error I feel is causing the VM to become unresponsive: (Checking  Details|XML view in Event viewer for this error does point to the problematic VM)

The description for Event ID 36 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\HarddiskVolumeShadowCopy133
C:

The locale specific resource for the desired message is not present

Any help would be appreciated, the vendor of this POS server doesn't seem to have much insight and I'm left to try to resolve this myself it feels.

Dave

Hi

I have recently added 2 SAS HDD on my server and extend the array and volume to the logical disk. But somehow when it not showing the correct volume size as what the array is showing.

Please help.

On windows server 2012 R2 am able to create NFS share.

But when i look at the version i could see Mounted version 3 where i would like to use version 4.

can somebody help me to configure the NFS v4 on the windows server 2012 r2

Hello!

I have HP ProLiant DL320e Gen8 v2 Server and Windows Server 2012 R2. 
Currently I have Raid 1 configured with HP's Dynamic Smart array.

I need more free space to server. Currently there is 2x 1TB hdd's and new ones are 3TB.

I think that I have to:

1. backup current system. (with what?)
2. Remove current HDD's
3. Insert new HDD's
4. Create a new Raid 1 for new HDD's 
5. Restore from backup.

When I try to make backup with Windows Server Backup, I get an error: "Backup of volume C: has failed. The drive cannot find the sector requested.

Any tips for how to do this? Any help would be greatly appreciated.

Windows native backp fails to create an System Image, or a Complete PC Backup.

This occurs in Windows 7, 64 bit Professional, Windows 7, 32bit Ultimate, Windows Vista Business, 32 bit. It occurs in 6 different computers I've tried. All the backup drives are 3TB. I have tried Seagte USB and Hitachi USB drives. 4 of them. The Windows 7 Ultimate, 32bit machine has SP1. All operating systems are using the current Service Packs, and all of the MS Updates including all of the recommended harware drivers. All of the systems are using the latest BIOS, firmware and OEM drivers as well.

It looks like the issue may be causes by a deficiency in Windows related to the Advanced Format drive spec. All of the computers that qualified had the AF hotfix applied; Advanced Format Drives 512e 4k, Vista and 2008 - KB2470478, Windows 7, and 2008 R2 KB982018

Error messages follow:

The Backup Failed.

Error message: One of the backup files could not be created. (0x8078002A)

The request could not be perfomed because of an I/O error. (0x8007045D)

This deficiency seems to apply across the board to different hardware manufacturers of external hard drives.

From what I have heard, Western Digital may have a format utility that addresses this issue, but only for WD drives.

Help.

I'm trying to use an Advanced Format drive (4K sectors) with Server 2008 R2 Backup.

If I format the drive using Disk Management as normal. Windows will create a partition on the drive that is 4K aligned, and all is well. I can verify that the partition is aligned by running Acronis WD Align.

I then set up a scheduled backup in Windows Server Backup 2008 R2 and specify that I want to use the drive for backups only. Windows Backup then re-formats the drive for it's use. However after checking with Acronis WD Align the new partition that Windows Backup has created is NOT aligned on a 4K boundry. This causes performance problems.

If I use Acronis WD Align to re-align the partition correctly; Windows Backup will no longer recognise the drive as a valid backup destination.

Is there anything I can do to force Windows Backup to create a 4K aligned partition, or is my only option to buy new drives that use 512 byte sectors?

We need Windows Server 2008 R2 Standard x86 media. Please send me proper URL, where from we can download the software.

Hi, I have a windows 2012 standard server which i run windows server backup.

It logged the following error and deleted the backup(not a happy camper).

Event ID: 25

Source:  volsnap
Level: Error
Description:  The shadow copies of volume\\?\Volume{93896cfc-d904-11dd-8cb5-001ec9ef572e} were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied

The target is an external 1TB usb 2.0 drive. This backup is the only thing that is running against this disk.

So why does this happen?

Its only the io load of the usb-drive which would be of concern(right/wrong).

Why is it necessary to delete the entire backup?

I have checked on the features and i can see that both my window server backup and command line tools was enable, why can't i find the window server backup on all programs or system tools? 

How do i open it without it?

Thanks and Regards Cityuser

We're having an issue where every other day the system state fails. We use a 3rd party piece of software that uses WSB for the system state. We get the following in the eevnt logs:

Faulting application name: wbengine.exe, version: 6.1.7601.17514, time stamp: 0x4ce79951
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
Exception code: 0xc0000005
Fault offset: 0x0000000000055384
Faulting process id: 0x3560
Faulting application start time: 0x01d01197a2bdc7a1
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d6f0610d-7d8f-11e4-a8f7-5cf3fc557333

and the following when running vssadmin list writers:

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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {7655da00-923b-441b-bc40-d64e3d44aaa9}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {0e9c9681-5e67-4748-900c-b32ff7ebd072}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {3e4d034d-b955-428e-952b-0581f8e05203}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {3ee8ab83-468c-4cfe-8613-6946976820fb}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {2975a331-2068-4a6e-a16f-4635f5ce2856}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {43188986-6573-45a8-b871-4be3d189a45f}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {a9632f02-31e3-424c-8c87-69395dbf04e2}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {180f4d03-93aa-4947-b874-c2d0d7546ca0}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {231ceb2e-3b8c-40f1-8d02-22a4f263802d}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {60237974-e116-454e-b29c-6ffeffd1bd9d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {440c5208-9d3a-4c84-884c-f9a3d8ad2c1e}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {d6ae39a4-2c8b-4e48-9f79-12247b9fac5b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {c616d312-5e21-47df-9e59-100cf6ac6f0e}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {8f945f3b-d50b-47b8-9085-1416d0b094e1}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {50c005a1-35e8-4bc1-a0c1-1bcdc9351322}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {2bcebf65-9243-4ccd-bae2-6ae12efd9a51}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {4101713c-f207-431f-be52-1171f1227c0b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {aa053355-2571-4e37-ba1d-501127ab2846}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {7645b18a-8aa4-49d3-abd1-5d7debd4b3f3}
   State: [1] Stable
   Last error: No error

as i said - this happens every other day, the 3rd party software provider say this is a microsoft issue but this doesnt happen when running a system state directly from WSB

Hello!

I have a problem with two VM´s on a HP Proliant ML350p Gen8, that has Windows Server 2012R2 operating system with Hyper-V role installed.

Both VM´s are also 2012R2, one is DC/DNS/FILE/PRINT and the other one is Exchange 2013.

The problem itself is that, when Windows backup (wbengine.exe - Block level backup engine service) inside VM starts, it uses almost maximum CPU resource, so the VM´s CPUs are 100% used. Backup itself is not working, there is no network trafic. Only way to get rid of 100% CPU usage is to restart the server.

When i start backup manually (Backup once - scheduled backup options), it is working and the CPU usage is around 20-30%.

One VM (DC/DNS/FILE/PRINT) has 2x vCPU and Exchange has 4x vCPU.

The problem started suddenly, the backup were performing slowly and failed.

Backups are scheduled on different time. Host level Hyper-V backup of VM´s works without any problem.

The backup location is Synology DS414 NAS and the servers are set up using iSCSI, for connecting separate backup lun´s for each server.

The Hyper-V host and both VM´s are patched up-to-date. Ofcourse i have tried a lot of restarts, looking event log, VSSADMIN - cannot find any errors...

The network setup:

Hyper-V host has a team of two physical adapters, that is set up with a external virtual switch (shared with management operating system) and used by the VM`s normal network trafic.

Hyper-V host itself is using separte physcial network card, for connecting with iSCSI to Synology NAS.

I tried to set up another physical network card on the host and create a new virtual swich, add extra virtual nic to VM`s and use this for iSCSI traffic for Windows backup and it didnt make things better.

I need to find a solution, because i cannot restart the server every night for the backups to work.

Hello,

I just set up folder redirection for clients (My Documents etc.) and it's working, now i was wondering how to do the following things:

1. Create Volume Shadow Copy's on the client folders and how to set this up from the server so the client's speed won't suffer from creating this shadow copy's.

2. Imagine a user removing one of his files accidentilly, is there anything to configure so they can get accidential deleted files back?

So i'd like previous versions of files to be available if they accidentilly change something within a file (Like .doc files) and i'd like the file to be available from somewhere if they accidentilly totally delete it.

Please help me with this, it will be really appreciated,

Thanks in advance.

Marc

Hi All,

Hi,

My server's hard disk partition (compressed NTFS) is of 1.5 TB and it has shared folders on it and Volume Shadow Copies were configured. for more than a year there has not been any problem with the shadow copies. But suddenly it stopped taking the Shadow copies. The data size is now half of the total space. I have freed some space by deleting four oldest shadow copies. still there is no solution. Actual space allocated for shadow copies is 120GB.

Every day, it is scheduled to run at 1:00PM. In the Event Viewer, I have these messages

1. At 1:00:55PM, The Volume Shadow Copy service entered the running state.

2. At 1:00:55PM, The Microsoft Software Shadow Copy Provider service entered the running state.

3. At 1:05:45PM, The Volume Shadow Copy service entered the stopped state.

4. At 1:05:45PM, The Microsoft Software Shadow Copy Provider service entered the stopped state.

But if I run the scheduled task, the task is running.

What could be the reason? Please suggest.

Hi Experts,

Unable to run System State backup in Win2K8 STD 32Bit, due to Cryptographic Services failed. Please help me in fixing the same. Thanks

“I have checked VSSadmin list Writers , but there is no error found”.

Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details: AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed.

System Error: 0xC0000039 (unresolvable).

Log Name:      Application

Source:        Microsoft-Windows-CAPI2

Date:          10/21/2014 1:33:32 PM

Event ID:      513

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <HostName>

Description: Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details: AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed.

System Error: 0xC0000039 (unresolvable).

Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />

    <EventID Qualifiers="49154">513</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-10-21T08:03:32.000Z" />

    <EventRecordID>1257</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>GCDWINBLR4HBR02.IND.CORP.AD</Computer>

    <Security />

  </System>

  <EventData>

    <Data>

Details:AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed.

System Error:0xC0000039 (unresolvable)</Data>

  </EventData> </Event>

My internet explorer 11 stopped working. To solve this problem, I deleted it and got IE 10. As it also did not work, I deleted it and got IE 9. However the problem could not be solved.

Afriend has help me. He has connected Hotmail Inbox with Google Browser. I can now work but there is still a problem. The Internet Explorer had a Favourites List but the list was not transferred to Google Browser,

How could I import the Favourites List from IE into Google?

FB321

Hi,

We have a Windows Server 2012 Standard under ESXi 5.1  using it as a Terminal Server for 45 users with RDP. More or less, every two weeks the system became unresponsive. When the users try to enter, only present a Black Screen. When we try to use the System Console, it never log in. The only solution is turn it off and on again the vm. We did a research in the forums, but there are no issues regarding 2012 and this strange behavior.

Any ideas what may be happen?

Regards