Help with errors in SMS_Discovery_Data_Manager component

[Lively]

Hello and thanks for reading.

 

I really just need a place to start with the errors we found. Long story short, we were looking into why one of our servers isn't showing in the console and found this. The DDM component is showing errors about every minute. Now everything appears to be working fine with pushing patches etc. However, we did have issues trying to delete old items from the console so we turned on the features for removing inactive clients.

 

I have attached the screen shots of the errors in the txt doc.

 

It appears to be an access issue to a SQL database. Rough guess is when SCCM is trying to retire data, it is denied access to that database and cannot remove the information. This install has been going for 9 months and appears to be going fine for what we use it for (Patching/Endpoint Protection/Reporting).

 

I just don't know where to look when checking the access rights. It would help if there was a database listed when the failures show up in the SQL log. Any help would be greatly appreciated.

 

 

From the SMS Discovery Data Manager Error Log:

 

 

Severity Type Site code Date
/ Time System Component Message
ID Description

Error Milestone P01 2/5/2013 2:46:20 PM SERVER
NAME SMS_DISCOVERY_DATA_MANAGER 2636 Discovery
Data Manager failed to process the discovery data record (DDR) "D:\Program
Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\R2LI5F68.RDR",
because it cannot update the data source.
Possible cause: On a Primary site, it is probably a SQL Server
problem. Solution: 1. Review the immediately preceding status
messages from this component about SQL Server errors. 2. Verify that this computer can reach the
SQL Server computer. 3. Verify that SQL
Server services are running. 4. Verify
that the site can access the site database.
5. Verify that the site database, transaction log, and tempdb are not
full. 6. Verify that there are at least
50 SQL Server user connections, plus 5 for each Configuration Manager
Console. If the problem persists,
check the SQL Server error logs.
Possible cause: On a secondary site, Discovery Data Manager probably
cannot write to a file on the site server, so check for low disk space on the
site server. Solution: Make more space
available on the site server.

Error Milestone P01 2/5/2013 2:46:20 PM SERVER
NAME SMS_DISCOVERY_DATA_MANAGER 620 Microsoft
SQL Server reported SQL message 8144, severity 16: [42000][8144][Microsoft][sql
Server Native Client 10.0]

Procedure or function
spSystemDecommission has too many arguments specified. :
spSystemDecommission    Please refer to
your Configuration Manager documentation, SQL Server documentation, or the
Microsoft Knowledge Base for further troubleshooting information.

 

 

From the DDM log file

 

 

Client registration updated. SMS_DISCOVERY_DATA_MANAGER 2/5/2013 2:44:14 PM 1732 (0x06C4)

*** exec dbo.spSystemDecommission 2097152234, false,
false,true SMS_DISCOVERY_DATA_MANAGER 2/5/2013 2:44:15 PM 1732 (0x06C4)

*** [42000][8144][Microsoft][sql Server Native Client
10.0][sql Server]Procedure or function spSystemDecommission has too many
arguments specified. : spSystemDecommission SMS_DISCOVERY_DATA_MANAGER 2/5/2013 2:44:15 PM 1732 (0x06C4)

CDiscoverySource_SQL::DecommissionDiscoveryItem - Error
decommissioning resource data. SMS_DISCOVERY_DATA_MANAGER 2/5/2013 2:44:15 PM 1732 (0x06C4)

CDiscoverDataManager::ProcessDDRs - Unable to update data
source SMS_DISCOVERY_DATA_MANAGER 2/5/2013 2:44:15 PM 1732 (0x06C4)

 

 

SQL server log file

 

 

2013-02-05 13:55:29.02 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:29.02 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database.
[CLIENT: <local machine>]

2013-02-05 13:55:29.04 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:29.04 Logon Login failed for user
'PROLIANCE\service1'. Reason: Failed to open the explicitly specified database.
[CLIENT: 172.16.1.15]

2013-02-05 13:55:29.10 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:29.10 Logon Login failed for user 'NT
AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified
database. [CLIENT: fe80::b5a1:988b:8420:6ca%13]

2013-02-05 13:55:29.11 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:29.11 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database.
[CLIENT: 172.16.1.15]

2013-02-05 13:55:29.18 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:29.18 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database.
[CLIENT: fe80::b5a1:988b:8420:6ca%13]

2013-02-05 13:55:29.25 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:29.25 Logon Login failed for user 'NT
AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified
database. [CLIENT: 172.16.1.15]

2013-02-05 13:55:29.25 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:29.25 Logon Login failed for user 'NT
AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified
database. [CLIENT: fe80::b5a1:988b:8420:6ca%13]

2013-02-05 13:55:29.45 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:29.45 Logon Login failed for user 'NT
AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified
database. [CLIENT: fe80::b5a1:988b:8420:6ca%13]

2013-02-05 13:55:30.11 Logon Error: 18456, Severity: 14, State: 38.

2013-02-05 13:55:30.11 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database.
[CLIENT: 172.16.1.15]

2013-02-05 13:55:32.03 spid18s A new instance of the full-text filter
daemon host process has been successfully started.

2013-02-05 13:55:32.05 Logon Error: 18456, Severity: 14, State: 38.

 

 

 

 

Errors.doc

[Lively]

Well we made some progress today.

 

The ddm log is clear after deleting/moving the file "D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\R2LI5F68.RDR" and the rest of the log was processed.

Once this was complete we saw the error messages in the component status stop.

 

So it appears the issue is resolved.

 

We still have an issue with deleting items from the console manually, but that will be another post at another time.

 

[Ocelaris]

Did you ever get this resolved, I'm having the exact same issue, I can't delete any records. I also found a ton of DDR records in the same folder, and basically we keep getting the Error...I can create new ones fine, but then I can't delete them.

 

CDiscoverySource_SQL::DecommissionDiscoveryItem - Error decommissioning resource data.

 

Also where did you find that SQL Log? I don't see that anywhere on the SQL Server... Thanks