Could not clear '%1!s!' bitmap in database '%2!s!' because of error %3!s!. As a result, the differential or bulk-logged bitmap ...

Could not clear '%1!s!' bitmap in database '%2!s!' because of error %3!s!. As a result, the differential or bulk-logged bitmap overstates the amount of change that will occur with the next differential or log backup. This discrepancy might slow down later differential or log backup operations and cause the backup sets to be larger than necessary. Typically, the cause of this error is insufficient resources. Investigate the failure and resolve the cause. If the error occurred on a data backup, consider taking a data backup to create a new base for future differential backups.

Could not change the Publisher because the subscription has been dropped. Use sp_subscription_cleanup to clean up the triggers. ... Could not clean up change tables for database '%1!s!'. A failure occurred when attempting to clean up the database change ... Could not clean up the configuration by dropping the public synonym on the Oracle server instance. To drop the public synonym ... Could not cleanup change tables for capture instance '%1!s!' using low end point %2!s!. Refer to previous errors in the current ... Could not clear '%1!s!' bitmap in database '%2!s!' because of error %3!s!. As a result, the differential or bulk-logged bitmap ... Could not close network endpoint, or could not shut down network library. The cause is an internal error in a network library. ... Could not complete resource governor configuration because there is not enough memory. Reduce the server load or try the ... Could not complete setting up the no-sync subscription at the Distributor while the distribution cleanup agent is running. ... Could not compose Service Principal Name (SPN) for Windows Integrated Authentication. Possible causes are server(s) incorrectly ...