Asked by:
SCCM 2012 SP1 and WSUS

Question
-
I am having one heck of a week. I tried to upgrade a SCCM Site created by someone else that was not done well. Needless to say the install fell on its face. I have to revert to SCCM RTM, fix all the broken issues from doing so, then upgrade again. This forced me to remove WSUS and reinstall that as well including a new database. Not it is green and does do SOME syncing but not all. I am getting a flood of the error messages below and my SCEP definition are not coming down, this is the biggest piece for us atm. Please help.... I am tired, drawn out from doing SCCM SP1 and SCOM CU7 in one weekend. Thank you all in advance.
Failed to sync update 830597be-c102-4175-9b97-debcaea2f683. Error: Failed to save update 830597be-c102-4175-9b97-debcaea2f683. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate
Tuesday, March 5, 2013 8:24 PM
All replies
-
If your on Server 2008R2, you need to have WSUS 3.0 SP2 and install KB2720211 and KB2734608. SP1 will also reset the WSUS ports back to default so that can break the WSUS Configuration Component.
Wednesday, March 6, 2013 4:58 AM -
If your on Server 2008R2, you need to have WSUS 3.0 SP2 and install KB2720211 and KB2734608. SP1 will also reset the WSUS ports back to default so that can break the WSUS Configuration Component.
Removed role, Uninstalled and removed download directoy. Installed again, added both Hotfixes added role. All seemed well till more started showing up. Nothing on any sites seems to be able to point to where the issue might reside, permissions, IIS, versioning, nothing.... At a complete loss. I am out of ideas to try as I have done uninstall/reinstall in every veriation I can think of. Why there can not be a more discriptive error message I do not know.
Failed to sync update 801aeb09-b016-4d38-81f9-d09ef526d93f. Error: Failed to save update 801aeb09-b016-4d38-81f9-d09ef526d93f. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate
Wednesday, March 6, 2013 4:02 PM -
Pattern noticed... as you can see it is the DefineUpdate source that is failing... is this the SCEP definition files, if so they are what I need the most! Other updates are being processed No Problem. Its not a complete failure of WSUS it is selective.
CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate
- Edited by TLC426 Wednesday, March 6, 2013 4:12 PM
Wednesday, March 6, 2013 4:12 PM -
OK Fix found and its now working. This issue is the updates from the uninstalled WSUS server left behind traces in the SMS database. The process was checking these entries and not getting back the data they needed to validate and allow the download to occure. This created a situation where unlimited uninstalls and reinstalls would do absolutly no good unless I waited a week, then the old records would get tombstoned out self resovling the issue. But who wants to let virus definitions get old? So we uninstalled the WSUS database and all. Ran a series of SQL Query commands to clean out the old updates out of SCCM. Reinstalled WSUS and synced a product WSUS knew about. Out of the Box it does not know about Forfront with out at least one sync occuring. So we synced XP, then added forfront and synced again and all went well.Thursday, March 7, 2013 2:35 PM
-
It would be awesome if you could post the sql queries that you ran so others can benefit from your solution.
Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com
Wednesday, May 22, 2013 4:22 PM -
This one sets all updates to expired
UPDATE v_Updateinfo SET isTombstoned = 1, isExpired = 1
This one deletes the references to the update metadata
(this query may time out if you have thousands of updates… which will require you to run it many times…)DELETE FROM CI_ConfigurationItems WHERE EXISTS (SELECT * FROM CI_ConfigurationItems AS ci LEFT OUTER JOIN CI_UpdateInfo AS cui ON ci.CI_ID = cui.CI_ID LEFT OUTER JOIN CI_CICategories AS cicat ON ci.CI_ID = cicat.CI_ID LEFT OUTER JOIN CI_CICategories_All AS cicat_all ON ci.CI_ID = cicat_all.CI_ID LEFT OUTER JOIN CI_CategoryInstances AS catid ON cicat.CategoryInstanceID = catid.CategoryInstanceID LEFT OUTER JOIN CI_CategoryInstances_Flat AS catid_flat ON cicat.CategoryInstanceID = catid_flat.CategoryInstanceID LEFT OUTER JOIN CI_CIHash AS cihash ON cicat.CI_ID = cihash.CI_ID LEFT OUTER JOIN CI_LocalizedProperties AS loc ON ci.CI_ID = loc.CI_ID LEFT OUTER JOIN CI_UpdateCIs AS uci ON ci.CI_ID = uci.CI_ID WHERE (ci.IsTombstoned = 1) AND (ci.IsExpired = 1))
This one deletes the references to the content filesDELETE FROM CI_Contents con WHERE EXISTS (SELECT * FROM CI_Contents con LEFT OUTER JOIN CI_ContentFiles as fi on con.Content_ID = fi.Content_ID LEFT OUTER JOIN CI_ContentPackages AS pkg ON con.Content_ID = pkg.Content_ID WHERE (ContentHash IS NULL))
Wednesday, May 22, 2013 4:32 PM -
thanks!
Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com
Wednesday, May 22, 2013 4:35 PM -
I´ve the same Problem, While executing update metadata step getting below error
The DELETE statement conflicted with the REFERENCE constraint "CI_CurrentErrorDetails_CIID_FK". The conflict occurred in database "CM_ABC", table "dbo.CI_CurrentErrorDetails", column 'CI_ID'.
It would be greatly appreciated if you could help with this problem
Wednesday, May 29, 2013 12:25 PM -
Not sure why your even touching "dbo.CI_CurrentErrorDetails", are you sure you copied and pasted with out the system editing the copy for you. I know copy and paste doesn't always work. I sometimes have to paste into notepad and fix what the process felt needed changed. Did you run debug first? What did that return?Wednesday, May 29, 2013 1:36 PM
-
I have copy into a notepad and paste it.
First time I got
Msg 208, Level 16, State 1, Line 1
Invalid object name 'CI_CIHash'.
Then I removed the line "LEFT OUTER JOIN CI_CIHash AS cihash ON cicat.CI_ID = cihash.CI_ID " coz their is no table called CI_CIHash in the database.
I ran only the select query and got 297943 rows with all the updates deatils
SELECT * FROM CI_ConfigurationItems AS ci
LEFT OUTER JOIN CI_UpdateInfo AS cui ON ci.CI_ID = cui.CI_ID
LEFT OUTER JOIN CI_CICategories AS cicat ON ci.CI_ID = cicat.CI_ID
LEFT OUTER JOIN CI_CICategories_All AS cicat_all ON ci.CI_ID = cicat_all.CI_ID
LEFT OUTER JOIN CI_CategoryInstances AS catid ON cicat.CategoryInstanceID = catid.CategoryInstanceID
LEFT OUTER JOIN CI_CategoryInstances_Flat AS catid_flat ON cicat.CategoryInstanceID = catid_flat.CategoryInstanceID
LEFT OUTER JOIN CI_LocalizedProperties AS loc ON ci.CI_ID = loc.CI_ID
LEFT OUTER JOIN CI_UpdateCIs AS uci ON ci.CI_ID = uci.CI_ID
WHERE (ci.IsTombstoned = 1) AND (ci.IsExpired = 1)
but while try to delete it
DELETE FROM CI_ConfigurationItems
WHERE EXISTS
(SELECT * FROM CI_ConfigurationItems AS ci
LEFT OUTER JOIN CI_UpdateInfo AS cui ON ci.CI_ID = cui.CI_ID
LEFT OUTER JOIN CI_CICategories AS cicat ON ci.CI_ID = cicat.CI_ID
LEFT OUTER JOIN CI_CICategories_All AS cicat_all ON ci.CI_ID = cicat_all.CI_ID
LEFT OUTER JOIN CI_CategoryInstances AS catid ON cicat.CategoryInstanceID = catid.CategoryInstanceID
LEFT OUTER JOIN CI_CategoryInstances_Flat AS catid_flat ON cicat.CategoryInstanceID = catid_flat.CategoryInstanceID
LEFT OUTER JOIN CI_LocalizedProperties AS loc ON ci.CI_ID = loc.CI_ID
LEFT OUTER JOIN CI_UpdateCIs AS uci ON ci.CI_ID = uci.CI_ID
WHERE (ci.IsTombstoned = 1) AND (ci.IsExpired = 1))
Msg 547, Level 16, State 0, Line 1
The DELETE statement conflicted with the REFERENCE constraint "CI_CurrentErrorDetails_CIID_FK". The conflict occurred in database "CM_001", table "dbo.CI_CurrentErrorDetails", column 'CI_ID'.
The statement has been terminated.
Wednesday, May 29, 2013 3:06 PM -
Has anyone been able to resolve this? I get the same error too when running the delete commandWednesday, July 10, 2013 7:10 PM