Jump to content


spyder

Established Members
  • Posts

    31
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by spyder

  1. 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!
  2. Up and running again! Thanks to anyweb (and Microsoft) we are now running 1702 and so far everything looks good!
  3. I have sent you the log now, thanks for taking the time to look at it!
  4. 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
  5. Yes, we tried upgrading yesterday (and again today) and ran into SQL problems. CMUpdate.log: *** [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-05 09:32:30 1312 (0x0520) ERROR: Failed to execute SQL Server command; CCISource::InsertObject returned -1 CONFIGURATION_MANAGER_UPDATE 2017-04-05 09:32:30 1312 (0x0520) ERROR: Failed to install default configuration items (FinalSqlOperations). CONFIGURATION_MANAGER_UPDATE 2017-04-05 09:32:30 1312 (0x0520) Failed to update database. CONFIGURATION_MANAGER_UPDATE 2017-04-05 09:32:30 1312 (0x0520) Not sure what is wrong yet. We have contacted our consultant who has done a couple of 1702 upgrades without any trouble, hopefully he can help us.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.