Insufficient System Resources Exist to Complete the Requested Service

Follow

Summary

This Knowledgebase article provides more detail about the "Insufficient system resources exist to complete the requested service" error message.


More Information

The following types of "Insufficient system resources exist to complete the requested service" (ISR) have been identified:

  1. GenericDriverException: DRIVER ERROR: Driver.verify failed: Insufficient system resources exist to complete the requested service.
  2. Background information

    So far, we don’t have conclusive data about this type of error. At the first glance, the problem appears only during Full System Check on the active server. In many cases, the pairs were affected by ISR type 2 as well, which is fixed now. We don’t know which system resources are depleted when this problem occurs and if Heartbeat has an active role in the problem.

    Resolution

    N/A - Support should collect logs, SCOPE, and poolmon from the affected sites before and during the problem.

  3. Failed to create D:\NFlog\send\2006-08-07-12062.log java.io.IOException: Insufficient system resources exist to complete the requested service
  4. Background information

    This type error message appears on Windows 2000 and 2003 with no Service Pack starting with Neverfail Heartbeat V5.0. The problem will occur if Neverfail Heartbeat has been installed before applying the Windows Service Pack. It is highly unlikely for this problem to appear on Windows 2003 with Service Packs installed before installing Neverfail Heartbeat. The issue was identified to be a memory leak in Nfrg Paged memory tag.

    Resolution

    Neverfail Heartbeat V5.1.1 included a fix for this issue.

  5. WinErrorCode: 1450, WinErrorText: Insufficient system resources exist to complete the requested service.
  6. Background information

    This type error message occurs only on Exchange installations, on the passive server. Most of the time, the error will appear after a switchover on servers with the 3GB switch on. In the cases that have been investigated so far, the passive server MmSt Paged memory tag increases until the paged pool is exhausted.

    Resolution

    So far, we don’t have a solution for this problem, only a workaround. The customer will have to run with the 3GB switch disabled on the Secondary server. Keep in mind that this may decrease the Secondary server performance when it becomes active.
    Other possible recomendations:

  • reduce userva to 2900
  • set the memory trimming to 60%
  • add more physical memory


At this time, Support should collect logs, SCOPE, and poolmon from the affected sites before and during the problem.

  • Exception in WalkerNFBean: java.lang.Exception: Call to RegOpenKeyEx failed: on [registry_key_name] : Insufficient system resources exist to complete the requested service.
  • Background information

    The problem can be caused by third-party software accessing the registry key above incorrectly.  In this case, there is not an actual shortage of resources other than an internal Microsoft reference counter overflowing.  The problem can be verified by accessing the troublesome key manually with regedit; the result will be an "Access denied".

    Resolution

    Analysis of what third-party software might access the registry incorrectly ( regmon.exe from SysInternals) and as a last resort, apply the steps in Knowledgebase article #1318 -'How to Exclude a Registry Key from the Registry Walker', to exclude the registry key from the Registry Walker.

  • PersistentDirectoryLister.getChidlren() error :  java.lang.Exception: ListResultOfstream::open() failed to create file : \\?\C:\neverfail\r2\FSMTemp\filesxxxxx.txt Insufficient system resources exist to complete the requested service.
  • Background information

    We have encountered this type only once during a Full System Check operation on a large fileserver. The error is preceded by many of the following events:

    run() com.neverfail.newfilestatemgr.exceptions.ProtectedNotInProtectedSetException: The Protected : [filename] is not in the Protected Set

    The above notification can appear when there are disk errors or when removing a filter, which contains a large folder/file structure, from the protected set.

    Resolution

    N/A

  • Controller has noticed ExceptionEvent - Exception in CommsMgr: [M4]Cannot open log file xxxxx.log (NFChannelCannotOpenLogIOException) because Insufficient system resources exist to complete the requested service (IOException)
  • Background information

    This problem has always occurred in conjunction with the ISR type 2, so this may be related to the Nfrg Paged memory leak. We have not encountered ISR type 6 after V5.1.1, so this points out that type 6 is a consequence of type 2.

    Resolution

    May have been solved together with ISR type 2.

  • WorkContentCalculator.calcWorkAndCount() didnot complete successfully : PersistentList::open() failed to open file : \\?\C:\Neverfail\r2\FSMTemp\NativeListxxxxxx.txt WinError : Insufficient system resources exist to complete the requested service.
  • Background information

    The problem can appear during a Full System Check when a filter containing a large folder/file structure is removed from the protected set which causes a kernel memory resource leak.  The error is preceded by many of the following events:

    run() com.neverfail.newfilestatemgr.exceptions.ProtectedNotInProtectedSetException: The Protected : [filename] is not in the Protected Set

    Resolution

    Neverfail Heartbeat V5.0.3 contains the fix for this issue.

  • Failed to restart com.neverfail.registry.RegistryController com.neverfail.controller.ControlException: com.neverfail.helper.error.NFException: [B1]Failed to set filters: DeviceIoControl() failed: Insufficient system resources exist to complete the requested service.
  • Background information

    We have encountered only two cases of this type error message. For one, the logs showed clear memory pool depletion and HDD issues, and the other had the non paged pool empty before the error occurred. As we don’t have poolmon to view the memory tag allocations, we don’t know if Heartbeat had an active role in this problem.

    Resolution

    N/A - Support should collect logs, SCOPE, and poolmon from the affected sites before and during the problem.


    Applies To

    All Versions


    Related Information

    None

    KBID-1349

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.