Fixing Operating System Error 1130

Helping businesses improve reliability and efficiency of SQL Server

Operating System Error 1130Last week I had a observe an interesting error. This error is directly related to the backup. One of our clients has the backup scheduled to run on the network share. From quite sometimes the backup jobs was failing, and when it fails it throws an error that reads like “Operating system error 1130”  there is not enough storage space available to process this command. You may be wondering why on the earth backups are stored directly on the network share. Believe me, there are few business decisions and/or practices for the backups that made this kind of setup for the backup. And, nowadays it is not so uncommon practice.

Here is what has happened, earlier, when the backup was configured it was the smaller number of connections that are being made to this server – let’s call it the backup server. Over the period, the requirement has changed, and databases recovery model has changed from SIMPLE to FULL. And, the number of servers utilizing the backup server has significantly increased. Since that’s the central and only backup server the client has, each SQL Server that is introduced has pointed the backup to occur there only.

While reading and researching about this error last week, what I have learned is that there is an IRPStackSize registry setting that we need to modify in order to fix this error.

Fixing Operating System Error 1130

Open your registry editor window, drill down until you find a below value. Before making any changes, take a backup of the registry key. Follow the steps:

    1. Open the Registry Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
    2. Add a new value
    3. The Default value is 15 which you can increase up to 50
Value Name: IRPStackSize
Data Type: REG_DWORD
Decimal: 15

The backup server in our case is Windows 2003 server and that’s why this setting applies to our case, but in general Operating System Error 1130 is related to the network. In most of the case, configuring retry after few minutes will work. In case you have some other solution to this issue, do let me know in the comment section below and I will more than happy to update and add that information to my blog post.

I hope you will find this tip useful. I would also suggest you browse through troubleshooting category of my blog space for more tips like this.

photo credit: Padmanaba01 Vietnam via photopin (license)

If you encounter such issues please refer to this article Resolving High CPU usage in SQL Server.