Query notification processing failed due to a sql exception

Analysis

=========

Event Type: Error

Event Source: DataAccessLayer
Event Category: None
User:  N/A
Computer:
Description:
Query notification processing failed due to a sql exception.

Action Plan

==========

This is caused by a high number of sql queries to the Datawarehouse database. 

The work around is to add an override for the Event Data Collector rule in the Data warehouse connection server scope.

The Execution Attempt Timeout Interval Seconds property was changed from 0 to 6 and the Max Execution Attempt Count was set from 0 to 10.

Restart the System Center service on the SCOM and any gateway servers.

Error ID:33510, DPM Could not find a suitable disk storage with enough free space for data source in SCDPM 2016

And it’s OK, because System Center 2016 Data Protection Manager running on Windows Server 2016, only supports  the new DPM Modern Storage feature which uses ReFs formatted volumes instead of disks.  The volume(s) must not reside on a Windows Dynamic Disks, just a basic disk which should be GPT if the disk is 2TB or larger.  Add the volume(s) to the DPM storage pool, then protection can succeed.
For more info about adding storage to DPM 2016, click here.

Azure Backup,All Backup job Fail - DPM could not execute a WMI query(33507)

Cause

======
The issue is caused by an incompatibility between Trend Micro and the DPM filter driver.

Action Plan

===========
When the antivirus was disabled MABS was able to create the Protection Group. But because running a server without an antivirus solution is not an option you can resolve the issue by adding the following registry key on any MABS server running with Trend Micro.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TmFilter\Parameters
Add DWORD (32 bit)
BypassDPMfilter, vaule of 1

VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

 VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

This is because the Hyper-V role is installed and this conflicts with VMware Workstation. To disable



Hyper-V from starting the following command can be used:

bcdedit /set hypervisorlaunchtype off

A reboot of of the Windows OS is necessary.



To enable the Hyper-V role again use the following command:

bcdedit /set hypervisorlaunchtype auto

A reboot of of the Windows OS is necessary.

OpsMgr Management Configuration process fails with timeout exception

Log Name:      Operations Manager 
Source:        OpsMgr Management Configuration 
Event ID:      29181 
Level:         Error 
User:          N/A 
Computer:      server.domain.com 
Description: 
OpsMgr Management Configuration Service failed to execute ‘DeltaSynchronization’ engine work item due to the following exception 
Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperationTimeoutException: Exception of type ‘Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperationTimeoutException’ was thrown. 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperation.ExecuteSynchronously(Int32 timeoutSeconds, WaitHandle stopWaitHandle) 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.ExecuteOperationSynchronously(IDataAccessConnectedOperation operation, String operationName) 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.WriteConfigurationDelta(IConfigurationDeltaDataSet dataSet) 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.DeltaSynchronizationWorkItem.TransferData(String watermark) 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.DeltaSynchronizationWorkItem.ExecuteSharedWorkItem() 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.SharedWorkItem.ExecuteWorkItem() 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.ConfigServiceEngineWorkItem.Execute()

Solution
========
We can increase the timeout using the following method on all management servers:

Make a backup of "x:\Program Files\System Center 2012\Operations Manager\Server\ConfigService.Config"
Increase the timeout values in ConfigService.config for the following:
<OperationTimeout DefaultTimeoutSeconds="30"> to 300 seconds
<Operation Name="GetEntityChangeDeltaList" TimeoutSeconds="180" /> to 300 seconds.
Restart the configuration service

SCDPM - An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80041024) (0x80041024))

Analysis

=========

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80041024) (0x80041024))

Solution

========
To resolve this issue open the settings of the affected virtual machine in the Hyper-V Console. Under Management go to Integration Services uncheck “Backup (volume shadow copy)”. After that, return to Data Protection Manager and perform a consistency check.

SCVMM 2016,Error (2912) An internal error has occurred trying to contact an agent when creating new VM

To solve this problem you could change the BITS port SCVMM is using during transfers:

1. On your VMM Server open the Registry

2. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings

3. Locate BITSTcpPort which should have a value of decimal 443. Change this to some port unused in your environment. (e.g. 8800)

4. Restart Virtual Machine Manager Service so that the change takes effect.