Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING SCCM upgrade 1702 to 1706 Failed to update database

Codi

Member
Messages
9
Reaction score
0
Points
1
Hello,

As of recent all of my Task Sequences are not being seen from any of my computers-- which is a totally different issue. I believe that doing the upgrade to 1706 from 1702 may fix this. I've attempted to do the upgrade but have been running into issues. I've combed the cmupdate log and it mentions a lot of issues with the SQL server, but from what I can tell there is nothing explicitly wrong and nothing that changed in the last few months, especially after the 1702 upgrade. I've done due diligence on the errors in the cmupdate log but can't seem to find anything specific. I've attached it after removing some of the identifying details.

It's telling me that the 1.46Mb file is too large for upload.. I uploaded it on Drive (https://drive.google.com/file/d/0B2v6RCsPCwe8ekZaNFF4VG91ZlU/view?usp=sharing) if there's another way I can upload it, please let me know as both the upload and inserting a code box are giving me errors.
 
Was the upgrade from 1702 to 1706 successful ?. Did you notice any errors ?. Log file show SQL server errors.

*** [42000][1750][Microsoft][SQL Server Native Client 11.0][SQL Server]Could not create constraint. See previous errors. CONFIGURATION_MANAGER_UPDATE
Failed to execute sql command -- ~-- Name : SC_Component_AK ~-- Version : 5.0.8540.1007 ~-- Definition : SqlKeys ~-- Object : K ~-- Description : <Please provide a description for this object> ~-- ~ALTER TABLE SC_Component ADD CONSTRAINT SC_Component_AK UNIQUE(SiteNumber, ComponentName, Name) CONFIGURATION_MANAGER_UPDATE
ERROR: Failed to execute SQL Server script: Create key sc_component_ak CONFIGURATION_MANAGER_UPDATE
ERROR: SQL Server error: <> CONFIGURATION_MANAGER_UPDATE
Failed to update database. CONFIGURATION_MANAGER_UPDATE
 
Hello, yes, I managed to upgrade to 1702 with absolutely no headache. The 1706 upgrade is the only one giving me fits. None of the settings or accounts were changed in the last few months hence my confusion.
 
Back
Top