{"id":5985,"date":"2019-02-20T15:17:31","date_gmt":"2019-02-20T21:17:31","guid":{"rendered":"https:\/\/kevinjustin.com\/blog\/?p=5985"},"modified":"2019-02-20T15:17:31","modified_gmt":"2019-02-20T21:17:31","slug":"troubleshooting-service-map-pack","status":"publish","type":"post","link":"https:\/\/kevinjustin.com\/blog\/2019\/02\/20\/troubleshooting-service-map-pack\/","title":{"rendered":"Troubleshooting Service Map pack"},"content":{"rendered":"

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Updated 14 Mar 2019<\/strong><\/span><\/p>\n

 <\/p>\n

If you get these exceptions like me, the issue has been raised, with a deliverable targeted for SCOM2019UR1.<\/p>\n

Disable the rule to reduce noise.<\/p>\n

 <\/p>\n

 <\/p>\n

Are you using Service Map Management pack, and getting errors?<\/p>\n

\"\"<\/p>\n

 <\/p>\n

This alert is based on the 46651\/46652 event ID in the Operations Manager event log<\/p>\n

From SCOM Console > Authoring Tab > Management Pack Objects > Rules<\/p>\n

Search in ‘Look for:’ bar GenericException (yes no space in between)<\/p>\n

 <\/p>\n

Rule<\/strong><\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

Rule Details<\/strong><\/p>\n

\"\"<\/p>\n

 <\/p>\n

To enable debug on the MS<\/h2>\n

 <\/p>\n

For collecting logs, please do the following:<\/p>\n