SCOM 2019 UR2 Patch Update: SQL Script Error: There is already an object named ‘FK_MaintenanceModeStatus_BaseManagedEntity’ in the database

Nachiappan Muthukaruppan 1 Reputation point
2020-09-23T20:04:44.857+00:00

Hi Team,

We followed old process to update UR2 on SCOM 2019.

Everything went smooth, but while we try to execute the DB Query, Got the below Error. Can we ignore this error?

Msg 2714, Level 16, State 5, Line 3934
There is already an object named ‘FK_MaintenanceModeStatus_BaseManagedEntity’ in the database.
Msg 1750, Level 16, State 1, Line 3934
Could not create constraint or index. See previous errors.

System Center Operations Manager
System Center Operations Manager

A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.

0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. SChalakov 10,941 Reputation points MVP Volunteer Moderator
    2020-09-28T13:55:53.8+00:00

    Hi,

    so you are running the automated procedure?

    Thanks for updating us!

    Regards,
    Stoyan

    Was this answer helpful?

  2. Nachiappan Muthukaruppan 1 Reputation point
    2020-09-28T13:19:02.043+00:00

    Hi Leon and Stoyan,

    MS Update: They have tested in LAB and confirmed.

    “From this behavior I can say it’s safe to determine that the new .msp files used to update to UR2 automatically import the MPs, AND automatically run the SQL script.”

    Was this answer helpful?

    0 comments
  3. Leon Laude 86,216 Reputation points
    2020-09-23T20:39:56.397+00:00

    Hi @Nachiappan Muthukaruppan ,

    May I ask why you sre not using the simplified patching (one-click-installer) instead?

    If you get an error when executing the SQL scripts, do not continue. Try re-running the script several times until it completes without errors.

    If your scripts are being blocked, you might have to shut down the services (sdk, config, and healthservice) on your management servers, to break their connection to the databases, to get a successful run, but this should be very rare in SCOM 2016 and later.

    If nothing of the above helps, I would create a support request to Microsoft.

    ----------

    (If the reply was helpful please don't forget to upvote or accept as answer, thank you)

    Best regards,
    Leon

    Was this answer helpful?

  4. SChalakov 10,941 Reputation points MVP Volunteer Moderator
    2020-09-23T20:30:48.3+00:00

    Hi @Nachiappan Muthukaruppan ,

    I would try to restart the related services on your management servers and then try again. This sounds like a very strange beahvior. I would also encourage you to contact Microsoft directly if restarting the SCOM related services on your management servers does not help. Maybe they have encountered similar behavior and can get you a quick fix or a workaround.

    Regards,
    Stoyan

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.