This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 5%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After the COM 2019 update, many errors appeared on the management server. Initially, the update went through Windows update. Then I tried to update the database scripts manually. DW storage was updated without problems. But the main database in SCOM is not updated manually, writes "Time" p_MP import XML module "has a dependency on the missing "DBO. p_ManagementPackFinishInstall" object. The module will be created, but it will not be able to work properly while this object does not exist."
Hi @Сергей Колыбин ,
I would try and run the simplified patching (one-click-installer) for Update Rollup 2 and run it on your SCOM management server, it will update the management server role, update the databases with SQL scripts, and then import any Management Pack updates.
I would not recommend updating via Windows Update, as there has been many issues by doing that.
Some helpful links:
----------
(If the reply was helpful please don't forget to upvote or accept as answer, thank you)
Best regards,
Leon
I tried to update using the installer, but it gives an error in the logs
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.UpdateSQLScripts
UpdateSQLScripts|CustomActionData = 10.19.10407.0|C:\Program Files\Microsoft System Center\Operations Manager\Server\|SQL-SCCM|OperationsManager|SQL-SCCM|OperationsManagerDW
Getting management group...
Connected to management group.
UpdateSQLScripts|DB updation failed|Database updater management pack is not updated
MSI (s) (1C:74) [11:56:37:280]: NOTE: custom action _UpdateSql.1451A536_2C9B_42F2_A37A_C9C6460E7EEA unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _UpdateSql.1451A536_2C9B_42F2_A37A_C9C6460E7EEA returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Hi,
from what I see, the UpdateSQLScripts custom action is failoing, because:
UpdateSQLScripts|DB updation failed|Database updater management pack is not updated
So maybe the MP Import has failed. Can you please try to Install .NET 3.5 on the management server, and re-run the Update Rollup?
(If the reply was helpful please don't forget to upvote or accept as answer, thank you)
Thanks and Regards,
Stoyan
Net 3.5 is installed on the management server
After updating the scripts, the following error occurred on sql server
Error message 777971007, severity 16, state 1 was called, but a message with this error number was not found in the sys.messages table. If the error number exceeds 50000, make sure that the user-defined message was added using the sp_addmessage procedure.
Hi,
did you try to mauall import the MPs from "\Program Files\Microsoft System Center\Operations Manager\Server\Management Packs for Update Rollups\"?
Regards,
Stoyan
Hi
The following error occurs during manual import of MP packages
Failed to import the Web Application Availability Monitoring Solutions Library.
If any of the management packs in the import list depend on this management pack, you will not be able to install them.
Database error. Mpinfra_p_managementpackinstall failed with exception:
[[SOFTWARE ID: b1a8b50f-5e6e-de2b-301b-35133bd5e981][PU version: 10.19.10407.0][SOFTWARE PKT: 31bf3856ad364e35] database Error. MPInfra_p_ManagementPackInstall failed with an exception:
The stored procedure "dbo.p_ManagementPackFinishInstall"could not be found.
Hi @Сергей Колыбин ,
It looks like the DB is a big mess. I would definitely recommend you to open a support case with Microsoft, so that they can take a look at what exactly went wrong.
Just keep in mind that only MS can make changes directly in the DB, otheriwse you are in an "unsupported" scenario.
Regards,
Stoyan
I agree with @SChalakov here, I would STOP right here, and raise a support request before doing any more potential damage to your SCOM environment.
https://support.serviceshub.microsoft.com/supportforbusiness
Thank you for help