Method 4: Use the Windows Installer CleanUp Utility. Use the Windows Installer CleanUp Utility to remove the files and the registry settings that make up the Windows Installer configuration information for Acrobat or for Reader.

MABS creates additional snapshot on server after BMR backup. MABS consumes additional storage by retaining avhdx files that are not required after backup. How to get and install MABS V4

This article describes an issue in which snapshots are not deleted after you perform a backup operation by using Volume Shadow Copy Service (VSS) in Windows Server 2012 R2. A hotfix is available to resolve this issue. Before you install this hotfix, check out the Prerequisites section.

This issue occurs because the Snapshot Agent uses SMO Miscrosft.SqlServer.Smo.dll to script articles. SQL server 2016 adds a new SMO property IsNativelyCompiled for In-Memory functions/stored procedures. This property isn't presented in SQL Server whose version is earlier than SQL Server 2016.

A large data size is known as a binary large object (BLOB). You can load blobs of data, such as an image, into the Data Model from data sources that support this data type such as SQL Server. You can also use Power Query library functions, such as File.Contents and Web.Contents, to load and store blob content to the Data Model.

This article describes an issue that occurs when a snapshot creation is running in Windows RT 8.1, Windows 8.1, Windows Server 2012 R2, Windows 8, or a Windows Server 2012. The issue is resolved in a hotfix that is described in this article and has a prerequisite.

Fixes an issue that triggers operating system error 32 when you restore a database from a striped backup set that contains FILESTREAM data in SQL Server 2012 SP3, 2014, or 2016.

You take a snapshot of the CSV. You delete the files. You create some files and delete some older snapshots in parallel. In this situation, the snapshot CSV snapshot file is corrupted. Resolution. To resolve this issue in Windows 8.1 or Windows Server 2012 R2, install update 2955164, or install the hotfix that is described in this article.

Fixes a memory issue that occurs when you run Replication Snapshot Agent in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2. When this issue occurs, a "Failed to read column data" error message is logged in the SQL Server Agent error log.

When you try to apply a snapshot for the newly added view, Distribution Agent fails, and the view is not added to the subscriber. This issue occurs if the default location is inaccessible. The following error messages may be logged in the SQL Server error log: