We are currently Running SCCM 2012 CU2 on SQL Server 2008 R2 SP2

When trying to delete a device from within the console we get the below error:

ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
 CauseInfo = "3";
 Description = "Error deleting discovery data in SQL";
 ErrorCode = 2168655109;
 File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspresource.cpp";
 Line = 390;
 Operation = "DeleteInstance";
 ParameterInfo = "SMS_R_System.ResourceId=16777558";
 ProviderName = "WinMgmt";
 SQLMessage = "[42000][8144][Microsoft][SQL Server Native Client 10.0][SQL Server]Procedure or function spSystemDecommission has too many arguments specified. : spSystemDecommission";
 SQLSeverity = 16;
 SQLStatus = 8144;
 StatusCode = 2147749889;
};

-------------------------------
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException
Failure deleting management object

Stack Trace:
   at Microsoft.ConfigurationManagement.AdminConsole.Common.StatusReportingWindow.ShowProgress(Action action, TimeSpan blockBeforeShow)
   at Microsoft.ConfigurationManagement.AdminConsole.CollectionMenuActions.LaunchUtilities.DeleteMenuAction(Object sender, ScopeNode scopeNode, ActionDescription action, IResultObject selectedObjects, PropertyDataUpdated dataUpdatedDelegate, Status status)

-------------------------------

System.Management.ManagementException
Generic failure

Stack Trace:
   at Microsoft.ConfigurationManagement.AdminConsole.Common.StatusReportingWindow.ShowProgress(Action action, TimeSpan blockBeforeShow)
   at Microsoft.ConfigurationManagement.AdminConsole.CollectionMenuActions.LaunchUtilities.DeleteMenuAction(Object sender, ScopeNode scopeNode, ActionDescription action, IResultObject selectedObjects, PropertyDataUpdated dataUpdatedDelegate, Status status)

-------------------------------

When looking at SMSProv.log we see the following error as well:

*~*~[42000][8144][Microsoft][SQL Server Native Client 10.0][SQL Server]Procedure or function spSystemDecommission has too many arguments specified. : spSystemDecommission     ThreadID : 4816 , DbError: 8144 , Sev: 16~*~* SMS Provider 2/7/2013 4:35:32 PM 4816 (0x12D0)CDiscoverySource_SQL::DecommissionDiscoveryItem - Error decommissioning resource data.

*~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspresource.cpp(390) : Error deleting discovery data in SQL~ SQL Error: [42000][8144][Microsoft][SQL Server Native Client 10.0][SQL Server]Procedure or function spSystemDecommission has too many arguments specified. : spSystemDecommission~*~* SMS Provider 2/7/2013 4:35:32 PM 4816 (0x12D0)

*~*~Error deleting discovery data in SQL [42000][8144][Microsoft][SQL Server Native Client 10.0][SQL Server]Procedure or function spSystemDecommission has too

Failed to DecommissionDiscoveryItem err code = 3 SMS Provider 2/7/2013 4:35:32 PM 4816 (0x12D0)many arguments specified. :

spSystemDecommission~*~* SMS Provider 2/7/2013 4:35:32 PM 4816 (0x12D0)

I've searched the forums and haven't seen anyone discuss this as it pertains to SCCM 2012. Any suggestions would be appreciated.

Thanks!!

It looks like the SQL server is the problem at hand. Is the SQL server remotely located?

Silly question, but have you tried giving your SCCM and SQL server a good ol' fashioned reboot?

Have a good look through your SQL and the associated server events to see if there is anything going on there.

*~*~[42000][8144][Microsoft][SQL Server Native Client 10.0][SQL Server]Procedure or function spSystemDecommission has too many arguments specified. : spSystemDecommission     ThreadID : 4816 , DbError: 8144 , Sev: 16~*~* SMS Provider 2/7/2013 4:35:32 PM 4816 (0x12D0)CDiscoverySource_SQL::DecommissionDiscoveryItem - Error decommissioning resource data.

I don't think that a reboot would solve that issue.

HappyWindowsAdministrator: you mentioned "SQL Server 2008 R2 SP2". Have you installed >CU6 (which is required)? This also has most likely nothing to do with the error message though.

From looking at the patch level question (we are actually having the same issue).  

If he is on SP2, then he just needs CU 1.  On Sp1 he needs CU6.  On SP2, it includeds CU1 -> CU5.  

Info is where I found that. 

Nigel,

The SQL Server is on the same server as SCCM2012. Rebooting was tried before posting here and it did not help.

Torsten,

We aren't experiencing any other issues within SCCM 2012 aside from deleting computer objects. Furthermore, the following URL indicates SP2 is supported with out any cumulative updates. (http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLSrvReq) You may be thinking of SP1 CU6.

Any additional assistance would be appreciated.

Thanks again.

You may be thinking of SP1 CU6.

On Torten's note about the reboot, this is nearly always a good step to take before you reach out for support. How many times server reboots have fixed weird SCCM issues I can no longer count. That said, I agree, it probably wouldn't fix the issue, but it's always worth a shot and I'm glad you had already done it!

Now to your problem, after having read through your logs again, I realise I did miss the glaring "Error deleting discovery data in SQL" bit the first time. You should probably have a tonne of SMS Discovery Data Manager errors as well.

It reminds me of similar issues with 2007, caused by malformed or bad DDRs. If you browse to "<SCCM Install Dir>\inboxes\auth\ddm.box\regreq\" you usually see an RDR file stuck there, which you can move to some backup location to fix the issue (or at least temporarily). I surmise that the reason for the SQL errors is that the record is malformed, which causes the stored procedure to throw the errors and prevent further processing.

On Torten's note about the reboot, this is nearly always a good step to take before you reach out for support. How many times server reboots have fixed weird SCCM issues I can no longer count. That said, I agree, it probably wouldn't fix the issue, but it's always worth a shot and I'm glad you had already done it!

Now to your problem, after having read through your logs again, I realise I did miss the glaring "Error deleting discovery data in SQL" bit the first time. You should probably have a tonne of SMS Discovery Data Manager errors as well.

It reminds me of similar issues with 2007, caused by malformed or bad DDRs. If you browse to "<SCCM Install Dir>\inboxes\auth\ddm.box\regreq\" you usually see an RDR file stuck there, which you can move to some backup location to fix the issue (or at least temporarily). I surmise that the reason for the SQL errors is that the record is malformed, which causes the stored procedure to throw the errors and prevent further processing.

Hi Nigel,

Although your suggestion didnt solve our issue it does confirm the DDR/RDRs are malformed. When looking through the files contained in that folder I'm seeing a lot of extraneous charachters at the beginning of the file (right before the <system> tag.

   FV     <System>
BEGIN_PROPERTY
<8><SMS Unique Identifier><19><64><GUID:eef320f5-9f85-4abc-99af-51a0eceb8897>

I've tried manually removing the extra charachters and saving the file, however it then gets moved to the BAD_DDRS folder and sits there.

Any idea how to troubleshoot this further?

I'm not sure if those characters are an issue or not as I don't have anything to compare with in front of me right now. I'm speculating wildly here now, but I suppose it's possible that the records were processed into the database with undetected errors of the kind you mention and that they only throw exceptions when certain types of queries are executed against them. As a bit of an experiment to see if it's discovery data causing the problem, you could try creating a device manually and then deleting it.

For a more legitimate troubleshooting step, I would recommend running an SQL server profiler trace, trying to delete the computer, then seeing what specific tables are being accessed. You might then be able to inspect those tables for signs of bad data. Don't do anything directly to the SCCM database as it is not supported by Microsoft.

I also add here, you might be at the point now where you consider calling Microsoft support directly.

Was there any more with this?  I'm having some similar messages come up "Procedure or function spSystemDecommission has too many arguments specified. : spSystemDecommission"  Plus I have 43000 ddr files in the ddm.box and 2000 RDR files in the regreq folder under there.

==>Resident site of <ELM>.  Discovery property <AD Site Name> matches (MD1)	SMS_DISCOVERY_DATA_MANAGER	3/6/2013 10:22:08 AM	8616 (0x21A8)
CDiscoverDataManager::ObsoleteOldRecords - Client's SMSID and Previous SMSID are same which will result in self obsoleting. Therefore Skipped obsoleting.	SMS_DISCOVERY_DATA_MANAGER	3/6/2013 10:22:08 AM	8616 (0x21A8)
Found record 2097157909 with duplicate SID. This record will be decommissioned.	SMS_DISCOVERY_DATA_MANAGER	3/6/2013 10:22:08 AM	8616 (0x21A8)
*** exec dbo.spSystemDecommission 2097157909, false, false,false	SMS_DISCOVERY_DATA_MANAGER	3/6/2013 10:22:08 AM	8616 (0x21A8)
*** [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	3/6/2013 10:22:08 AM	8616 (0x21A8)
CDiscoverySource_SQL::DecommissionDiscoveryItem - Error decommissioning resource data.	SMS_DISCOVERY_DATA_MANAGER	3/6/2013 10:22:08 AM	8616 (0x21A8)
CDiscoverDataManager::MergeExisitingRecordWithSameSID - Unable to update data source and decomission duplicate record.	SMS_DISCOVERY_DATA_MANAGER	3/6/2013 10:22:08 AM	8616 (0x21A8)
CDiscoverDataManager::ProcessDDRs_PS - SQL problem detected.  Will retry later.	SMS_DISCOVERY_DATA_MANAGER	3/6/2013 10:22:08 AM	8616 (0x21A8)
CDiscoverDataManager::THREAD_ProcessNonUserDDRs - Failed to manage files in inbox.  Will retry in at least 60 seconds	SMS_DISCOVERY_DATA_MANAGER	3/6/2013 10:22:08 AM	8616 (0x21A8)

I'm have much of the same issue, 

Error in the DDM.log:

CDiscoverySource_SQL::DecommissionDiscoveryItem - Error decommissioning resource data.

3,000 items in the DDM.box folder, and I can't delete any systems in CM 2012... Any help would be appreciated?