Quantcast
Channel: Configuration Manager 2007 Inventory forum
Viewing all articles
Browse latest Browse all 233

Errors in SMS_DISCOVERY_DATA_MANAGER, Message ID - 682

$
0
0

Hi All,

We are maintaining SCCM 2007 R3 environment. I am getting the below status message errors in my central server. I checked the machine details in resource explorer, it was having very old last hardware scan and last run on dates. But when I check it in the Inventory agent.log file, it was todays date.

Severity Type Site code Date / Time System Component Message ID Description Thread ID Process ID
Error Milestone GBR 12/09/2012 00:34:40 SERVER_XXXXX  SMS_DISCOVERY_DATA_MANAGER 530 Could not open file "j:\Microsoft Configuration Manager\inboxes\auth\ddm.box\asg1knzw.DDR" for reading. 12012 19188

Severity Type Site code Date / Time System Component Message ID Description Thread ID Process ID
Error Milestone GBR 12/09/2012 00:34:40 SERVER_XXXXX   SMS_DISCOVERY_DATA_MANAGER 530 Could not open file "j:\Microsoft Configuration Manager\inboxes\auth\ddm.box\aduyg7w8.DDR" for reading. 12012 19188

Severity Type Site code Date / Time System Component Message ID Description Thread ID Process ID
Error Milestone GBR 12/09/2012 00:34:40 SERVER_XXXXX   SMS_DISCOVERY_DATA_MANAGER 530 Could not open file "j:\Microsoft Configuration Manager\inboxes\auth\ddm.box\79hpit2r.DDR" for reading. 12012 19188

Severity Type Site code Date / Time System Component Message ID Description Thread ID Process ID
Error Milestone GBR 12/09/2012 11:18:42 SERVER_XXXXX  SMS_DISCOVERY_DATA_MANAGER 682 The data file "j:\MicrosoftConfiguration Manager\inboxes\auth\ddm.box\gm19zx1v.DDR" that was submitted by the client whose SMS unique ID is "GUID:0XXXX-XXXX-XXXX-B4F5-YYYYYYYYY", was rejected because the file was signed but the authentication key did not match the recorded key for this client. 12012 19188

Severity Type Site code Date / Time System Component Message ID Description Thread ID Process ID
Error Milestone GBR 12/09/2012 12:11:24 SERVER_XXXXX  SMS_DISCOVERY_DATA_MANAGER 682 The data file "j:\Microsoft Configuration Manager\inboxes\auth\ddm.box\i4pe1ohv.DDR" that was submitted by the client whose SMS unique ID is "GUID:0XXXX-XXXX-XXXX-B4F5-YYYYYYYYY", was rejected because the file was signed but the authentication key did not match the recorded key for this client.  12012 19188

I can understand that the SCCM client in the machine is in good status. Either the machine is not sending the details to MP or MP is unable to process the details and update in database which has sent by the machine. Could anyone help me on getting this resolved.

I could find some bad DDRs in the \\server_xxxx\j$\MicrosoftConfigurationManager\inboxes\auth\ddm.box\BAD_DDRS folder which is having the same above GUIDs. These bad DDRs is generated everyday and the .ddr file is available for these systems on all the days.

I could find the below lines in the ddm.log file as well for the same date and time which is in status messages.

CDiscoverySource::VerifyClientPublicKeys - Public keys do not match for client GUID:0XXXX-XXXX-XXXX-B4F5-YYYYYYYYY.

STATMSG: ID=682 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISCOVERY_DATA_MANAGER" SYS=SERVER-XXXXXXXX SITE=XXX PID=19188 TID=12012 GMTDATE=Wed Sep 12 11:11:24.203 2012 ISTR0="j:\Microsoft Configuration Manager\inboxes\auth\ddm.box\i4pe1ohv.DDR" ISTR1="GUID:0XXXX-XXXX-XXXX-B4F5-YYYYYYYYY" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Moving bad file i4pe1ohv.DDR to j:\Microsoft Configuration Manager\inboxes\auth\ddm.box\BAD_DDRS\i4pe1ohv.DDR

I request someone to advise at the earliest, this error is coming daily in my console and I need to find a solution and root cause.


Best Regards, Sukandha


Viewing all articles
Browse latest Browse all 233

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>