When you run a non-component VSS backup (for example, byusing Azure Site Recovery (ASR) Agent) against volumes of servers hostingSQL Server 2016 instances, the backup jobs may report failure with thefollowing events logged in the Application Event log.
Writer Class Id:ID
Writer InstanceName: Microsoft SQL Server 2016:SQLWriter
Writer Instance ID:ID
Command Line:"C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
Error: Source:SQLWriter, Event ID:EventID
Sqllib error: OLEDB Error encountered callingICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 102
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 11.0
Error message: Incorrect syntax near '.'.
If you are using Azure Site Recovery, then the ReplicationHealth will show Critical status under the Severity column for the affectedinstances and the Replication Health Errors in the Dashboard show the followingerror:
VSS writer SQLServerWriter failed with error 0x800423f4during After DoSnapshotSet phase on the source machine.
The option to request non-component backup belongs to the VSS requestorapplication and is usually not visible to the user. An example ofapplication requesting such backups is Azure VM backup agent.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: