none
BACKUP FUL - The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server

    Question

  • hi,

    I receive the following error when I run backup full:

    2010-06-30 06:51:44.31 spid76      BackupDatabase: Database Calibrator
    2010-06-30 06:51:44.34 spid76      Backup: Streams open
    2010-06-30 06:51:44.43 spid76      BackupDatabase: Checkpoint done
    2010-06-30 06:51:44.45 spid76      BackupDatabase: Work estimates done
    2010-06-30 06:51:44.46 spid76      BackupDatabase: Configuration section done
    2010-06-30 06:51:44.48 spid76      Backup:Copying data
    2010-06-30 06:53:18.32 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
    2010-06-30 06:54:52.08 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
    2010-06-30 06:56:25.85 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
    2010-06-30 06:57:59.63 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
    2010-06-30 06:59:33.38 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
    2010-06-30 07:01:07.16 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
    2010-06-30 07:02:40.91 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
    2010-06-30 07:04:14.69 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.
    2010-06-30 07:05:48.45 spid76      The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00000000003200 in file with handle 0x0000101C. This is usually a temporary condition and the SQL Server will keep retrying the operation. If the condition persists then immediate action must be taken to correct it.

    Enviroment:

    Windows Server Enterprise Edition Sp2 x86

    SQL Server sp3 CUP 4

    8 GB RM (\3GB \PAE \AWE)

    2 QuadCore

    Obs: Directory where i put the backup isnt compressed

    waiting_task_address session_id exec_context_id wait_duration_ms     wait_type                                                    resource_address blocking_task_address blocking_session_id blocking_exec_context_id resource_description
    -------------------- ---------- --------------- -------------------- ------------------------------------------------------------ ------------------ --------------------- ------------------- ------------------------ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    0x02DBCE38         76         0             29479547             ASYNC_IO_COMPLETION                                         0x00000001         NULL                 NULL                NULL                     NULL
    0x02FEE2F8         76         1             343                 BACKUPBUFFER                                                 NULL             NULL                 NULL                NULL                     NULL
    0x211C8118         76         2             15                 IO_COMPLETION                                                NULL             NULL                 NULL                NULL                     NULL

    (3 row(s) affected)
    Obs: I Already run checkdb on database, but I dont receive any error message..

    https://connect.microsoft.com/SQLServer/feedback/details/571950/backup-database-full-the-operating-system-returned-error-1450

    do you have some tips for me?

    Wednesday, June 30, 2010 8:19 PM

All replies

  • Hi,

     

    This doesn’t look like a SQL Server issue but it’s the OS issue as reported by Bob Dorr, Senior escalation engineer.

     

    You may want to remove /3GB switch the boot.ini file.

     

    I guess this is a direct result of enabling both /3GB and /PAE.

     

    When you add /3GB switch, user mode will take 3 GB and system kernel will have only 1 GB and if you also enable /PAE then the PTE (Page table Entries) size will increase from 4 KB to 8KB and this will reduce the number of PTE's within 1 GB and hence the OOM issues.

    Reference:

    http://blogs.msdn.com/b/psssql/archive/2008/07/10/sql-server-reports-operating-system-error-1450-or-1452-or-665-retries.aspx

     

     


    http://SankarReddy.com/
    Wednesday, June 30, 2010 8:34 PM
    Moderator
  •  

    Sankar, thanks for your reply!

    Yestarday at night I removed \3Gb from boot.ini on passive node, I expected do failover  to passive node today at noon, but late in the evening server receive bluee screen:

    Event Type:        Information

    Event Source:    Save Dump

    Event Category:               None

    Event ID:             1001

    Date:                    1/7/2010

    Time:                    04:05:41

    User:                     N/A

    Computer:          GALIANO

    Description:

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003f (0x00000000, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

     

    I think that error could be happen because the \3GB, What do you think?

    Now SQL Server is runing without swtich \3Gb on boot.ini on active note and I'm  monitoring and I could start the backup normally....

    I'll monitor this server for some days to sure that the problem was solved.

    regards,

    Thiago

     

     

    Thursday, July 01, 2010 2:40 PM