SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded

I have got the following error SCCM Application Request FailedSqlException caught in SubmitNewRequest deadlock or retry count exceeded. This post will discuss the issue we were facing a few weeks ago when trying to request applications from “Company Portal” and “Software Center“.

I started getting different errors at different places. The error message that I received in Software Center was different from the one I got in Company Portal. I think the issue was interconnected. We will see both the error messages in this post.

First, we will discuss the issue while requesting the application from the software center because that’s my primary domain. I have seen a different issue related to Software Center can not be loaded. I also cover the company portal error message in this post.

Patch My PC

There was also an error related approve software requests via email. You will learn about the root cause of these issues and resolve them. You will learn how to fix the following problems in this post:

  • Issue 1 :- Unable to approve software requests via e-mail.
  • Issue 2:- Very few users getting attached errors while requesting software.

Software Center Error Application eMail Approval Request

You can see more details about Software Center Error Application eMail Approval Request. As soon as we clicked on application details and selected request, we got the below error in the software center.

The software center can not be loaded. There is a problem loading the required components for Software Center. You can try launching Software Center at a later time. If the problem continues, you can contact your helpdesk.

1E Nomad

The application requires administrator approval to be installed.
Submitting Request and status -> Approval Required.
Version: 87

SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded
SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded

The screenshot of the error given above is not much help because the error printed is generic. Now, it’s time to look at the log files as well.

That’s where our experts come into the picture. Anoop Nair has described everything we need to know about logs, and if you notice the blog is getting updated very frequently (If any addition in the logging mechanism of SCCM) https://www.anoopcnair.com/sccm-logs-files-list-of-configmgr-log-files/

We have to check 2 logs at the client end. Log names along with functions they report. There are server-side and client-side logs for the Software center that can not be loaded.

SCCM Client Side – Logs for Softwware Center Related Issues.

SCClient_<domain>@<username>_1.logRecords the activity in Software Center for the specified user on the client computer.
SCClient_<domain>@<username>_2.logRecords the historical activity in Software Center for the specified user on the client computer.

SCCM Server-side logs for Software Center Related issues.

SCNotify_<domain>@<username>_1.logRecords the activity for notifying users about software for the specified user.
SCNotify_<domain>@<username>_1-<date_time>.logRecords the historical information for notifying users about software for the specified user.

Company Portal Error Requesting the application

We were shifting the focus to Company Portal. We saw the below error while requesting the application from Company Portal. I tried asking the same application that we did via Software Center for better understanding. Error Screenshot below:

Company portal Application Error: Error Requesting the application. An error occurred while attempting to request the application.

SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded
Error screenshot while requesting an application from Company Portal – SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded

Troubleshooting

Now we will check the UserService.log on the Management Point to which this client is reporting. Go running – Type “Control smscfgrc.” It will have an “Assigned Management Point.” On that MP, we have to check the UserService log.

It clearly shows the deadlock error for multiple entries for an EventID, due to which it does not process the request.

SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded
User Service log screenshot on MP – SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded

Now we know what’s the problem so let’s check in to SCCM DB. Connect to the SCCM DB using SQL Management Studio and run the below query. You can see many other SQL queries in the previous post.

Select * from AlertEvents

SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded
SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded

The result of the SQL query will look like the screenshot below:

SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded
SQL Query output – SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded

We can see there are multiple AlertID’s as duplicates, which was causing this issue.

NOTE!Make sure you have a good backup of the site DB before you proceed further.

Solution to Fix Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded

Let’s try to fix the problem Failed SqlException caught in SubmitNewRequest deadlock or retried count exceeded.

The solution is very simple. Run the SQL Query Select * from AlertEvents

SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded 1
Sample SQL Query output

Now, it’s time to delete the duplicate entry of the alert ID from the database. Make sure you have taken the backup of the SQL database before you do the following SQL command.

Note the duplicate “AlertID’s.” In my case, it’s “16777224”. It will be different for your environment.

  • Open the SQL Management Studio.
  • Connect your Database Engine.
  • Right Click on your database CM_XXX and click on ‘New Query’
  • Copy the following SQL query to fix the issue (SqlException caught in SubmitNewRequest deadlock or retry count exceeded).
  • Click on the Execute button.

Now execute -> Delete from AlertEvents where AlertID = ‘16777224’

SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded
SCCM Application Request Failed SqlException caught in SubmitNewRequest deadlock or retry count exceeded

Now try requesting the application, and it should work without any issues. We noted that the email approval process for application requests was also not working due to this issue, and it was fixed later once we implemented this fix.

NOTE: MS Doesn’t support this DB tweaking, and you should involve MS Engineer before executing these SQL statements.

Disclaimer – The information provided on the site is for general informational purposes only. All information on the site is provided in good faith. However, we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on the website.

Author

My name is Deepak Rai and I am a Technical Lead on SCCM and Intune with more than 13 years of experience in IT. My main domain is SCCM 2012, CB, MECM, Intune, and Azure (Runbooks). I have worked on several platforms (Active Directory, Exchange, Veritas NETBACKUP, Symantec Backup Exec NDMP devices Like Netapp, EMC Data Domain, Quantum using Backup Exec 2010 and 2012, HP storage works 4048 MSL G3, Data Deduplication related troubleshooting.) in these 13 years but at last ended up to the technology from which I started as IT Engineer (SCCM).

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.