Compartilhar via

Event 18054 errors in the SQL application log – in SCOM 2012 R2 deployments

  • Artigo

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    February 11, 2016
    Hi Kevin,
    I am unable to view the scripts attached with the article.
  • Anonymous
    February 11, 2016
    Hi Kevin,
    I am sorry could view the script in the link given below. Thanks
    https://gallery.technet.microsoft.com/SQL-to-fix-event-18054-c4375367
  • Anonymous
    February 16, 2016
    I recently had an interesting customer issue. We were deploying a new management group to do some performance
  • Anonymous
    September 12, 2016
    Hi Kevin,I have the exact same thing - SCOM 2012 R2 after moving SCOM DB.But I'm unable to access the link in the article. Please advise.Thanks,Orit.
  • Anonymous
    February 21, 2017
    Hi Kevin,Just wanted to know if this query needs to be run against either master or OpsMgr database. Please help and suggest both query should run against which database.Thanks Sone
  • Anonymous
    May 02, 2017
    The comment has been removed
    • Anonymous
      May 02, 2017
      If you are missing that one, you are likely missing them all. Why not just run the whole script. That's what I'd recommend.
      • Anonymous
        May 02, 2017
        Thanks for your response Kevin. Much appreciated
      • Anonymous
        May 08, 2017
        kevin,I am at the latest SCOM 2012 R2 UR12. Are these scripts applicable to my env. And also do these scripts need to be run against OperationsManager and OperationsManagerDW respectively ? Thank you.
  • Anonymous
    July 04, 2017
    Hi Kevin, The team at dbatools.io wrote a great PowerShell Module that easily copies theses messages - https://dbatools.io/functions/copy-sqlcustomerror/