Today’s blog article will not be very long, but I hope very helpful for all of you (and spare you some headaches), who already installed SCOM 2016 Update Rollup 6 and are experiencing this particular issue.
Who is affected:
The actual problem occurs only for SCOM operators, who have scoped views (are member of a specific SCOM role), while working in the SCOM console. This means that if you are a SCOM Administrator you won’t probably experience the behaviour, described below.
Affected are SCOM 2016 environments with Update Rollup 6 installed. SCOM 2016 UR5 is not affected.
What are the symptoms:
While the operator works in the console, it crashes and displays the following error:
“Incorrect syntax near the keyword ‘CREATE’.”
In addition to the console crash, the following events are logged on the management server your console is connected to.
Log Name: Operations Manager
Source: OpsMgr SDK Service
Event ID: 26319
An exception was thrown while processing GetRelatedManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions for session ID uuid:f9350488-087d-42f7-94f8-50637d932652;id=62.
Exception message: The creator of this fault did not specify a Reason.
Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Incorrect syntax near the keyword ‘CREATE’.).
Log Name: Operations Manager
Event ID: 33333
Data Access Layer rejected retry on SqlError:
Request: MT_Select_Rel_ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd — (ParentIds=457c209e-d14b-0721-be20-c3bf55447dab), (Depth=0), (UserRoleIds=ca6b2edd-1fc2-4d72-9624-40b772315976), (UserScopeIds=S-1-5-21-1234567-1867602182-418732521-1225,S-1-5-21-1234567-1867602182-418732521-513,S-1-1-0,S-1-5-32-555,S-1-5-32-545,S-1…), (OperationId=e8b526b8-2404-4b2a-ab56-db3d9c7ef6aa)
Message: Incorrect syntax near the keyword ‘CREATE’.
This behaviour is bug, identified with the “Microsoft.EnterpriseManagement.DataAccessService.Core.dll” library in its UR6 version (7.2.12066.0). This has also been confirmed by Kevin Holman in the comment section of his article:
UR6 for SCOM 2016 – Step by Step
The affected file version is:
The SCOM Product Group is also informed about this bug and will release a fix for this most probably with SCOM 2016 Update Rollup 7. Until then we also have a working workaround (I have already tested it in multiple environments).
In order to work around the behavior you need to revert the version of the affected library (Microsoft.EnterpriseManagement.DataAccessService.Core.dll) to its UR5 version (7.2.12016.0)
How to do that:
Copy the file “Microsoft.EnterpriseManagement.DataAccessService.Core.dll” from an environment with Update Rollup 5 and then paste it in the SCOM installation directory (for example “C:\Program Files\Microsoft System Center 2016\Operations Manager\Server”) on all of your management servers, while replacing the existing (UR6) one.
I have found out that I cannot paste it without stopping the SDK (System Center Data Access), the System Center Management Configuration Service and the Microsoft Monitoring Agent first, so this is also something you need to consider.
If you have no access to a UR5 environment, you can download the file (you need to rename it back from .txt to .dll) from my personal OneDrive here.