{"id":20229,"date":"2024-02-29T19:56:13","date_gmt":"2024-02-29T23:56:13","guid":{"rendered":"https:\/\/kevinjustin.com\/blog\/?p=20229"},"modified":"2024-02-29T20:02:11","modified_gmt":"2024-03-01T00:02:11","slug":"scom2016-sql-sysmessages-and-18054-events","status":"publish","type":"post","link":"https:\/\/kevinjustin.com\/blog\/2024\/02\/29\/scom2016-sql-sysmessages-and-18054-events\/","title":{"rendered":"SQL SysMessages 18054 events"},"content":{"rendered":"

 <\/p>\n

\"SCOM2016+<\/a>
SCOM2016+ SQL SysMessages 18054 events<\/figcaption><\/figure>\n

Whether you’re building a new SCOM2019, SCOM2022 environment or not, you might be missing these event details, and NOT even know!<\/p>\n

 <\/p>\n

It’s been a while for me, and I came across these, so posting for a fresh heads up!<\/p>\n

Leverage Holman’s TXT files to keep your logging up to maximum potential!\u00a0 Use the information below to resolve SCOM2016+ SQL SysMessages and 18054 events.<\/p>\n

Holman GitHub download – contains SQL TXT files to run on OpsMgr & DW databases https:\/\/github.com\/thekevinholman\/SQLFix18054EventsSysmessages<\/a><\/p>\n

 <\/p>\n

The Github TXT files to download contain a clear scope of messages.<\/p>\n

 <\/p>\n

SQL messages excerpt<\/h4>\n

—————————————–
\n— MOMv3 messages are 77798xxxx —
\n—————————————–<\/p>\n

———————————————–
\n— Discovery range: 77798-0000 to 77798-0049 —
\n———————————————–
\n— Managed type doesn’t exist.
\nEXECUTE sp_addmessage @msgnum = 777980000, @msgtext = N’The specified managed type doesn”t exist.’, @severity = 16, @lang = ‘us_english’, @with_log = false, @replace = ‘REPLACE’
\nGO<\/p>\n

— Relationship type doesn’t exist.
\nEXECUTE sp_addmessage @msgnum = 777980001, @msgtext = N’The specified relationship type doesn”t exist.’, @severity = 16, @lang = ‘us_english’, @with_log = false, @replace = ‘REPLACE’
\nGO<\/p>\n

— Source entity of the relationship doesn’t exist.
\nEXECUTE sp_addmessage @msgnum = 777980002, @msgtext = N’The specified relationship doesn”t have a valid source.’, @severity = 16, @lang = ‘us_english’, @with_log = false, @replace = ‘REPLACE’
\nGO<\/p>\n

— Target entity of the relationship doesn’t exist.
\nEXECUTE sp_addmessage @msgnum = 777980003, @msgtext = N’The specified relationship doesn”t have a valid target.’, @severity = 16, @lang = ‘us_english’, @with_log = false, @replace = ‘REPLACE’
\nGO<\/p>\n

— Discovery data from invalid managed entity is dropped.
\nEXECUTE sp_addmessage @msgnum = 777980004, @msgtext = N’Discovery data has been received from a rule targeted to a non-existent entity. The discovery data will be dropped.’, @severity = 16, @lang = ‘us_english’, @with_log = false, @replace = ‘REPLACE’
\nGO<\/p>\n

— Invalid relationship rejected by cycle detection.
\nEXECUTE sp_addmessage @msgnum = 777980005, @msgtext = N’Relationship {%s} was rejected because it would cause a containment cycle; relationship source = ”%s” and target = ”%s”.’, @severity = 16, @lang = ‘us_english’, @with_log = false, @replace = ‘REPLACE’
\nGO<\/p>\n

— Discovery data generated by invalid connector.
\nEXECUTE sp_addmessage @msgnum = 777980006, @msgtext = N’Discovery data generated by invalid connector:%s.’, @severity = 16, @lang = ‘us_english’, @with_log = false, @replace = ‘REPLACE’
\nGO<\/p>\n

— Discovery data generated by invalid rule, task, discovery.
\nEXECUTE sp_addmessage @msgnum = 777980007, @msgtext = N’Discovery data generated by invalid discovery source. Id:%s.’, @severity = 16, @lang = ‘us_english’, @with_log = false, @replace = ‘REPLACE’
\nGO<\/p>\n

Documentation links<\/h4>\n

Blog for 18054 events https:\/\/kevinholman.com\/2017\/08\/27\/scom-2016-event-18054-errors-in-the-sql-application-log\/<\/a><\/p>\n

SCOM 2016, 2019 and 2022: Event 18054 errors in the SQL application log<\/a><\/p><\/blockquote>\n