/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Upgraded SCCM to 1702. Now I can not import computers into All Systems (or any collection)

04/21/2017 3573 views

Before 1702 upgrade (my SCCM was 1610) I was able to import new computers to build associations for side by side Win10 deployments.  Now, after a 1702 console upgrade, I am getting the following error:


 Description = "Unexpected error when merging and updating discovery information";
    ErrorCode = 2152205056;
    File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspsite.cpp";
    Line = 1333;
    Operation = "ExecMethod";
    ParameterInfo = "SMS_Site";
    ProviderName = "WinMgmt";
    SQLMessage = "[23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of UNIQUE KEY constraint 'MachineIdGroupXRef_AK'. Cannot insert duplicate key in object 'dbo.MachineIdGroupXRef'. The duplicate key value is (GUID:<myguid>,
5).";
    SQLSeverity = 14;
    SQLStatus = 2627;
    StatusCode = 2147749889;


Blogs are pointing to a bug in 1702. Anyone know any additional information on MS fixes? A work around until a fix is provided by MS?

3 Comments   [ + ] Show comments

Comments

  • After SCCM1702 upgrade. There are no clients included in the system. In SQL, only infra servers and unknown machines appear.

    Error: Following computers have not been imported:

    · Name: xxx
    · MAC Address: xxx
    · SMBIOS GUID:
    · Source Computer:
    · Choose Target Collection: c_xxx
    Errors
    1 The SMS Provider reported an error.ConfigMgr Error Object:instance of SMS_ExtendedStatus{ Description = "Unexpected error when merging and updating discovery information"; ErrorCode = 2152205056; File = "e:\\cm1702_rtm\\sms\\siteserver\\sdk_provider\\smsprov\\sspsite.cpp"; Line = 1333; Operation = "ExecMethod"; ParameterInfo = "SMS_Site"; ProviderName = "WinMgmt"; SQLMessage = "[23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of UNIQUE KEY constraint 'MachineIdGroupXRef_AK'. Cannot insert duplicate key in object 'dbo.MachineIdGroupXRef'. The duplicate key value is (<myguid>, 5)."; SQLSeverity = 14; SQLStatus = 2627; StatusCode = 2147749889;};
  • I have the exact same problem. The post below suggests that there is a bug in 1702, but it's about duplicate machines.
    https://social.technet.microsoft.com/Forums/en-US/fadf5381-793f-4a9b-865d-17c6b9cddbe4/cm-1702-importcmcomputerinformation?forum=ConfigMgrPowerShell
    • Machines are not duplicated, because the machine deleted object from R_System. Machines can be imported many times and every time a new GUID is created (CM SQL dbo.MachineIdGroupXRef).That's right is another random GUID 1) In these cases, however, it always means the same ID. 2) The GUID in MachineIdGroupXRef table will not be deleted if the computer object is cleared. In this case, 1 causes greater concern. Workaround: Empty the dbo.MachineIdGroupXRef table.
  • Same problem here. I usually search All Devices for the conflicting GUID and delete it.

All Answers

0
Try this: KB4038659
Answered 01/08/2018 by: MaGRauN
White Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ