SQL Server Error : 10021, Severity: 16. Execution terminated by the provider bec

SQL Server Error : 10021 Details

SQL Server Error: 10021
Severity: 16
Event Logged or not: No
Description:
Execution terminated by the provider because a resource limit was reached.
Severity 16 Description:
Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

For other ways to read and find error log location please our article https://sqlserver-dba.co.uk/error-log/sql-server-identify-location-of-the-sql-server-error-log-file.html

Solution for Resolving the Error

When we have encountered DCOM problem 10021, we utilise DCOM to enable remote execution of COM objects.

Here’s how to fix the problem:

1. Use an Administrator account to access the machine.
2. Type dcomcnfg into the Run box on the Start menu.
3. Navigate to Console Root, Component Services, Computers, My Computer, DCOM Config, Framework service in the left pane of the Microsoft Management Console (MMC) Component Services snap-in that appears.
4. Right-click Framework service and select Properties from the context menu.
5. Choose the Security option.
6. Select the Use Default radio button under Launch and Activation Permissions and click OK. (The default setting for Launch and Activation Permissions is Customize.)
7. Log off after closing the Component Services snap-in.

We were getting four DCOM failures before implementing these procedures.

SQL Server Error Code and solution summary

SQL Server Error: 10021
Severity: 16
Event Logged or not: No
Description:
Execution terminated by the provider because a resource limit was reached.