SQL error 14258 occurs while trying to run a job in SQL.

Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the cause for this error and how to fix it.

What causes SQL error 14258 to occur

Here are the different reasons for this error to occur.

1. If the lightweight pooling is set to 1 then it causes SQL Server to switch to fiber mode scheduling.

The main purpose of using the Lightweight pooling option is to provide a means to reduce the system overhead associated with the excessive context switching sometimes seen in symmetric multiprocessing (SMP) environments.

Setting lightweight pooling to 1 causes SQL Server to switch to fiber mode scheduling. Whereas the default value for this option is 0.

2. MAPI32.dll is being used and is using SQLMail which uses MAPI client to send an email.

Resolution for SQL error 14258

Now let’s see how our Support Engineers fix this error for our customers.

1. A lightweight pooling option is an advanced option.

If you are willing to use the sp_configure system stored procedure to change the setting, then you can change the lightweight pooling option only when it shows advanced options is set to 1. Normally, this setting takes effect after we restart the server.

We can set a lightweight pooling option back to the default value by running the below T-SQL code.

sp_configure ‘show advanced options’, 1
go
reconfigure
go
sp_configure ‘lightweight pooling’, 0
go
reconfigure

2. Another way to fix this error is to change the mail settings.

We change the mail setting to use Database Mail by following the below steps.

Access SQL Server Agent >> Alert System >> Properties >> Change Mail System to Database Mail.

This fixes the error.

[Need any further assistance in fixing SQL errors? – We’re available 24*7]

Conclusion

In short, this error occurs while trying to run a job in SQL. Today, we saw the resolution to this SQL error.