Tag Archives: error

Fix: Storage Replica warning Events 10448 Storage Replica has failed an application IO

When checking the logs of the Storage Replica on a Windows Server 2016, 2019 or 2022, using the below command, you get the error saying that Storage Replica has failed an application IO.

Get-WinEvent -ProviderName Microsoft-Windows-StorageReplica -max 20

In this case, the replication is not working and there are no other issues pointing to what could be the problem. In my case the solution was to restart the Storage Replica service from the services.msc. After this, I ran the Get-WinEvent command again and it was replicating again.

 

(131)

Fix: Windows Server Backup The process cannot access the file

When running Windows Server Backup to another location and you get the error “The process cannot access the file because it is being used by another process”.

Capture

To fix this you would need to look on the backup logs from the location %windir%\logs\windowsserverbackup.

In the error log file you will find

Error in deletion of [C:\System Volume Information\001.dat] while pruning the target VHD: Error [0x80070020] The process cannot access the file because it is being used by another process.

In my case, what I have done is that I deleted all the files in the target folder of the backup, re-run the backup and it worked.

(6213)

Fix: Exchange error 0x800ccc6c – Verify that the mailbox exists and that the Exchange receive connectors are configured properly

When having especially SBS 2008 with the POP3 Connector to retrieve mail from an outside mailbox to your internal Exchange server, you may encounter the below error in the Event Viewer.

An error occurred while delivering mail to ‘mailbox@mydomain.com’ on the SMTP server ‘localhost’. The error code was 0x800ccc6c. Verify that the mailbox exists and that the Exchange receive connectors are configured properly.

Thou the error message is misleading, this problem can happen if the POP3 Protocol Errors meet the tolerance of the Exchange SMTP Receive connectors. Exchange will close an SMTP connection after a certain number of protocol errors. The default is 5.

To solve the issue, in my case I had to in increase the value of “MaxProtocolErrors” for the Exchange SMTP Receive connectors from Exchange Management Shell by using the below command.

Set-ReceiveConnector -identify “Name of Connector” -MaxProtocolErrors 999

After this, I have restarted the POP3 Connector retrieval of messages and it worked.

(3294)

Fix: The backup set holds a backup of a database other than the existing

When restoring a database from an SQL backup .bak, one usually creates a database and then selects the restore function. As soon as you try to restore the database you get the error saying “The backup set holds a backup of a database other than the existing“. This is because it fails to read the files from the restore and matching them to the newly created files.

The error says:

Restore failed for Server ‘SQLSRV01’. (Microsoft.SqlServer.SmoExtended)
Additional Information
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The backup set hold a backup of a database other an the existing ‘test_restore’ database.
RESTORE DATABASE is terminating abnormally. (Microsoft SQL Server, Error: 3154)

To solve this one should do the following:

– Don’t create an empty database and restore the .bak file on to it.
– Use ‘Restore Database’ option accessible by right clicking the “Databases” branch of the SQL Server Management Studio and provide the database name while providing the source to restore.

This should allow you to restore the database with no error and fix the error 3154.

(12681)

Fix: Hyper-V backup General access denied error (0x80070005)

When taking a backup using Windows Server Backup and during the backup you get an error as below

Writer Failures
Writer Id: {1072AE1C-E5A7-4EA1-9E4A-6F7964656570}
Instance Id: {017311EA-59CE-4B2E-830C-558BE6CEB39A}
Writer Name: Cluster Shared Volume
VSS Writer Writer State: 5
Failure Result: 80042336
Application Result: 80004005
Application Message: (null)
Component: BE389042-38BD-483E-9FD9-7E0F4CA466E466841cd4-6ded-4f4b-8f17-fd23f8ddc3de:c336e204-fbe8-46a4-a80d-faed6edafd94:SRVDCHVS02
Logical Path: (null)
Component Result: 800423F4 Component Message: Could not create backup checkpoint for virtual machine 'HYPDCORA01': General access denied error (0x80070005). (Virtual machine ID BE389042-38BD-483E-9FD9-7E0F4CA466E4) File Spec: C:\ClusterStorage\Volume1\virtual_machines\HYPDCORA01\Virtual Machines\\BE389042-38BD-483E-9FD9-7E0F4CA466E4.xml Recursive: 0 File Spec: C:\ClusterStorage\Volume1\virtual_machines\HYPDCORA01\Virtual Hard Disks\\HYPDCORA01.vhdx Recursive: 0 File Spec: C:\ClusterStorage\Volume2\\Oracle_Data.vhdx Recursive: 0 File Spec: C:\ClusterStorage\Volume1\virtual_machines\HYPDCORA01\Snapshots\\BE389042-38BD-483E-9FD9-7E0F4CA466E4-BackupSnapshot.xml Recursive: 0 File Spec: C:\ClusterStorage\Volume1\virtual_machines\HYPDCORA01\Virtual Hard Disks\\HYPDCORA01-ChildVhd.avhdx Recursive: 0 File Spec: C:\ClusterStorage\Volume2\\Oracle_Data-ChildVhd.avhdx Recursive: 0

After some research I found that it can be easily fixed. The issue occurs because most probably you have created a Shared volume and the VHDX file or Virtual Drive is in the root of the volume. To fix this, create a new folder called ‘Virtual Drives’ or whatever you wish and move the Virtual Drives onto that folder.

Restart the backup process and the issue will not occur

(4321)