Jump to content




spyder

Upgrade to 1702 failed to update database



Recommended Posts

Hi all,

Yesterday we tried to upgrade from 1610. Pre-requisite check had no errors, but the upgrade failed at the 'Upgrade ConfigMgr database’ step.

CMUpdate.log error output (full log attached to this post):

*** [42000][50000][Microsoft][SQL Server Native Client 11.0][SQL Server]ERROR 547, Level 16, State 0, Procedure sp_SetupSettingsAndRules, Line 177, Message: The MERGE statement conflicted with the REFERENCE constraint “CI_CurrentRuleDetail_SettingID_FK”. The conflict occurred in database “CM_V01”, table “dbo.CI_CurrentRuleDetail”, column ‘SettingID’. : spRethrowError CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210)
ERROR: Failed to execute SQL Server command; CCISource::InsertObject returned -1 CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210)
ERROR: Failed to install default configuration items (FinalSqlOperations). CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210)
Failed to update database. CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:30 41488 (0xA210)
Failed to apply update changes 0x87d20b15 CONFIGURATION_MANAGER_UPDATE 2017-04-04 14:59:59 41488 (0xA210)

 

We retried the installation with the same result as before. There were two hotfixes for 1610 available, so we tried installing one of them, SCCM 1610 Update Rollup 3 (KB4010155), and it installed fine. We then restarted the server and tried once more with the 1702 upgrade, but it still failed with the same error.

Any ideas are highly appreciated at this moment. ConfigMgr seems to work fine and, strange enough, the console as well as the site says they're now upgraded to 1702 (5.00.8498.100).

 

Thanks,
Pär

CMUpdate_log.zip

Share this post


Link to post
Share on other sites


please update the status of this thread

Share this post


Link to post
Share on other sites
4 minutes ago, anyweb said:

please update the status of this thread


Up and running again! Thanks to anyweb (and Microsoft) we are now running 1702 and so far everything looks good!

A huuuge thank you for the help!

  • Like 2

Share this post


Link to post
Share on other sites

glad to hear it, to summarize Microsoft is aware of the issue and has produced a fix

  • Like 3

Share this post


Link to post
Share on other sites
3 hours ago, chrisiss said:

Hi, i am having the exact same problem, Do you have a solution please.

Thanks 

Chris

Hi Chris,

You should get in contact with anyweb, niall@windows-noob.com, since I made a promise not to share the solution he provided. But I'm sure he will help you.


Cheers,
Pär

Share this post


Link to post
Share on other sites

Hi Par,

ok i have sent an email, it looks like this may of taken out all my secondary site servers which is a major problem. And SMSexec cannot read the reg on the sccm db. 

He did mention that MS hs produced a fix tho ? 

And i have the 060417 release.. 

 

Edited by chrisiss
extra info

Share this post


Link to post
Share on other sites

Chris,

For us, it involved some sql editing to clean out the bad data, a solution provided by MS.

We have no secondary site, so we didn't experience any urgent issues.

According to anyweb, MS has "slipstreamed the fix", whatever that means. Maybe you need to re-download the files for 1702. Hopefully anyweb will reply soon...

 

Cheers,

Pär

  • Like 1

Share this post


Link to post
Share on other sites

hi Chris

after looking at your logs your error is not the same as Par's i'll see what i can find out but please contact me as you mentioned this morning so we can decide how to troubleshoot it, do you have any possibility of doing a teamviewer session with me ?

  • Like 1

Share this post


Link to post
Share on other sites

Hi anyweb,

I upgraded SCCM from 1610 Hotfix (KB4016483) to 1702 and the process ends with the error:

Failed upgrade ConfigMgr database.

CMUpdate.log:

INFO: Site Component Manager installation completed.    CONFIGURATION_MANAGER_UPDATE    2017-05-23 16:12:39    1308 (0x051C)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure    CONFIGURATION_MANAGER_UPDATE    2017-05-23 16:12:39    1308 (0x051C)
Turned on activation for service broker queue    CONFIGURATION_MANAGER_UPDATE    2017-05-23 16:12:39    1308 (0x051C)
Failed to apply update changes 0x87d20b15    CONFIGURATION_MANAGER_UPDATE    2017-05-23 16:12:39    1308 (0x051C)
Waiting for changes to the "\\sccm.server\SMS_VK1\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...    CONFIGURATION_MANAGER_UPDATE    2017-05-23 16:12:39    1308 (0x051C)
There are no pending update package to be processed.    CONFIGURATION_MANAGER_UPDATE    2017-05-23 16:22:39    1308 (0x051C)

Maybe you can help to correct this error.
Thank you

Share this post


Link to post
Share on other sites

hi Alv2005

can you email me your cmupdate.log and any additional details and i'll see what i can find out

 

cheers

niall

Share this post


Link to post
Share on other sites
20 hours ago, anyweb said:

hi Alv2005

can you email me your cmupdate.log and any additional details and i'll see what i can find out

 

cheers

niall

 

Helo,

Thank you in advance for your help.

Here is the log files  CMUpdate.log, ConfigMgrPrereq.log :

 

 

sccm_to-1702.zip

Share this post


Link to post
Share on other sites
On 5/24/2017 at 11:23 AM, Alv2005 said:

Helo,

Good Day,

Completely new to SCCM, tried to apply "1702 Hotfix Rollup (KB4019926) and failed. Completed download/replication/Prereq's. Failure comes back as -  Failed to apply update changes 0x87d20b15

Thank you in advance for your help.

Here is the log files  CMUpdate.log

 

SCCM.txt

Share this post


Link to post
Share on other sites

Is this only an issue if upgrading from 1610?

I'm planning an upgrade from 1606 to 1702; This topic just scared the shit out of me. I wouldn't know what to do if it fails.

Share this post


Link to post
Share on other sites

I having the same issue my CAS and one of the primaries PS2 sitting on its dedicated separate SQL server upgraded successfully  from 1606 - 1702 

 

But sadly the other primary PS1 sitting on its own dedicated DB ‘alone’ failed to upgrade with error message “[Failed]:Upgrading ConfigMgr database” Please any solutions to this. Have been researching...

 

Share this post


Link to post
Share on other sites
On 2017-06-13 at 11:19 AM, dinci5 said:

Is this only an issue if upgrading from 1610?

I'm planning an upgrade from 1606 to 1702; This topic just scared the shit out of me. I wouldn't know what to do if it fails.

Sorry for the late reply.
Shortly after we did our upgrade, Microsoft made some changes to their upgrade files, and I am pretty sure the problem is not there anymore. And with 1706 out any day now, you might as well go there.

Share this post


Link to post
Share on other sites
5 hours ago, Eze said:

I having the same issue my CAS and one of the primaries PS2 sitting on its dedicated separate SQL server upgraded successfully  from 1606 - 1702 

 

But sadly the other primary PS1 sitting on its own dedicated DB ‘alone’ failed to upgrade with error message “[Failed]:Upgrading ConfigMgr database” Please any solutions to this. Have been researching...

 

You should probably get in touch with anyweb/Niall and see if he can help you, as he helped us.
 

Share this post


Link to post
Share on other sites

yes if you have an Upgrade issue then contact me at niall@windows-noob.com and i'll see what I can do

Share this post


Link to post
Share on other sites

HI All,

I have almost the same issue updating from 1610 to 1702. SQL is 2012 and OS is 2008R2. In CMUpdate.log task failed:

INFO: sql object usertargetedsoftware_creationtimesmsdefaulttoday with hash SHA256:91FA555663F1479E8B2FDB5B09DD7ED3A22D4B1125955C91D3F78E0DDEE52A7C already exists.    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:21 PM    1800 (0x0708)
Successfully restored database role permission.    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:21 PM    1800 (0x0708)
Successfully reverted Site Control changes.    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:31 PM    1800 (0x0708)
INFO: Installing Site Component Manager ...    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
INFO: File \\?\C:\Program Files\Microsoft Configuration Manager\inboxes\sitecomp.box\shutdown.trn does not exist. No zapping needed.    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
Old build 8355 is detected installed    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
delete SMS_BUSINESS_APP_PROCESS_MANAGER component registry    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
INFO: Installing Site Component Manager...    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
INFO: Installing Site Component Manager under acct <NT AUTHORITY\SYSTEM> path <C:\Program Files\Microsoft Configuration Manager\bin\x64\sitecomp.exe>    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Unsecure    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
INFO: Running Post Auto Upgrade script.    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
INFO: Starting Site Component Manager...    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:32 PM    1800 (0x0708)
INFO: Started Site Component Manager service    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:34 PM    1800 (0x0708)
INFO: Site Component Manager installation completed.    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:34 PM    1800 (0x0708)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:34 PM    1800 (0x0708)
Turned on activation for service broker queue    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:35 PM    1800 (0x0708)
Failed to apply update changes 0x80004005    CONFIGURATION_MANAGER_UPDATE    8/21/2018 12:53:35 PM    1800 (0x0708)

 

Any idea how to solve?

Thanks in advance
 

Edited by vassil_p

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×