Home > Tech, Windows > Windows 7 Nonpaged Pool Srv Error 2017

Windows 7 Nonpaged Pool Srv Error 2017

I’m using my Windows 7 machine as a file server in addition to it being my Media Center. I’m mounting a Samba (smb) share using CIFS from my Linux server so I can synchronize files using rsync.  However, I ran into a problem after using the mounted share for a small amount of time.  I found a simple solution after a bit of research.

After running rsync for a short amount of time, I discovered that I was getting memory allocation errors related to the Windows share.  After unmounting, I attempted to remount the share and received the error:

mount error(12): Cannot allocate memory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

After checking the Event Viewer System log, I found the following error:

Source: srv
Event ID: 2017
Level: Error
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

Some research led me to find this Google Groups discussion about the problem and this Microsoft Technet article discussing the solution (look at the bottom of the page).  Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly.  Set the following registry key to ’1′:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

and set the following registry key to ’3′:

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

After making these changes and restarting, I haven’t seen this issue arise again.  Fixed!

  1. justin
    October 5th, 2009 at 12:57 | #1

    thank you SO MUCH. i’ve been having this problem with connecting my macbook to my pc for a massive backup and this is the first definitive solution. THANK YOU!

    • October 5th, 2009 at 15:33 | #2

      Glad someone else found use out of me writing this up. I mostly write these articles up for myself for future reference, but it’s good to know it is useful beyond this purpose as well.

  2. John
    October 15th, 2009 at 12:11 | #3

    I applied these setting and so far i haven’t had a freeze on large number of file transfer.
    Good Job Thanks.

  3. Kervinou
    October 25th, 2009 at 02:50 | #4

    in first, i’m french so sorry for my poor english ;)
    So Yes, thanks from me too…
    Same problem for me with RC and RTM version. I tested with size=2 instead of size=3 but problem reappared recently next to lot of data transfered.
    in fact normaly, size=2 should be good but in real world, it does not work ! ;-)

    then i replaced yesterday size=2 by size=3 and i’ll see within next few days how it works ;)
    so SeeU
    Kerv.

  4. October 25th, 2009 at 07:27 | #5

    @Kervinou: Yeah, I’ve had size=3 since I first posted this article and have had no problems at all. I hope size=3 works just as well for you!

  5. TiGerman
    October 31st, 2009 at 09:29 | #6

    Many thanks!

    What alive saver.

  6. Jon Campanali
    November 2nd, 2009 at 08:15 | #7

    This modification allowed my XP clients to see the Windows 7 shared folders. On the XP client, the error was “the specified server cannot perform the requested operation” when trying to map the drive. XP had no Event Viewer items logged. The Windows 7 machine had the srv 2017 error in Event Viewer, but nothing on the screen when the XP client attempted to map. I made the registry changes here, rebooted the Windows 7 machine only, walked over to the XP client and it mapped immediately. Thanks!

  7. mattywix
    December 20th, 2009 at 06:01 | #8

    Awesome! Pretty much exactly what I was doing. I found windows 7 64 bit doesnt support my ext2 driver, so I had to run a vmware fedora inside windows, passthru my usbdisks with ext2 partitinos to fedora and from there rsync them back onto windows.
    Didnt work until I found this article.
    What a pile of doggypoop windoze can be.
    Wish you could solve my ext2 on windoze 7 problem though ;)

    • December 20th, 2009 at 09:39 | #9

      Yeah, I decided to just put most of my data on an NTFS partition and share it rather than try to get Win7 to read Linux file systems. Let me know if you figure out the ext2 thing. It would be useful to know.

  8. Jason
    January 10th, 2010 at 20:48 | #10

    Thanks so much for posting! This was driving me nuts before I found this solution.

  9. David Trounce
    January 11th, 2010 at 12:59 | #11

    Many thanks. Changing the size=1 to size=3 parameter completely solved my file share issues with Vista x64 SP2.

    My Windows 7 x64 client was giving “Not enough server storage is available to process this command”. This was despite disabling SMB2 which seemed to solve the problem for XP clients. However I’ve now re-enabled SMB2 and everything works. size=3 is the only fix that is required. This fixes the underlying issue – event 2017, “server is unable to allocate from the system non-paged pool since it has reached it’s configured limit”.

    Increasing IRPStackSize to 50 (maximum) had no impact, it just delayed the inevitable.

    • January 11th, 2010 at 14:29 | #12

      Thanks for the additional detailed information! Once I saw that it was working for me I didn’t bother experiment at all. Hopefully future viewers of this post will see your comment and learn a bit more.

  10. KG
    January 20th, 2010 at 15:16 | #13

    I applied the size=3 key last month and so far have not had any issues despite connections from about a dozen machines every day and no reboots for 4 weeks. This is not a work-around – it’s the real fix :)
    Thanks for sharing!

    • January 20th, 2010 at 15:19 | #14

      Thanks for the confirmation! It’s good to see this working for so many people.

  11. Pvdb
    February 1st, 2010 at 15:56 | #15

    Thanks from me too.
    Amazing I did not find this after a search for the sharing problem.
    My XP machines also got kicked out of de win7 shares.

    Glad I still found it.

  12. Kevin Baugh
    February 7th, 2010 at 15:01 | #16

    Seems to have fixed my problems to thanks!

  13. Rick Bliss
    February 17th, 2010 at 09:39 | #17

    Worked for me too man. Thanks.

  14. Kurt
    February 20th, 2010 at 14:15 | #18

    Thanks very much for posting this. The problem didn’t crop up until I got a gigabit router in place, but once i did I started seeing this. Thought it was mobo/bad RAM initially, so this page really saved me some hassle. <3

  15. steven
    February 21st, 2010 at 23:19 | #19

    Yes, It really works for windows 7 64 bits file sharing with winXP.
    Thanks a lot!

  16. February 24th, 2010 at 23:02 | #20

    +1 Thanks, I’ve been having this trouble since a Samba update a few weeks ago. This is a brilliant piece of interweb advice.

  17. thunderbolt
    March 5th, 2010 at 01:28 | #21

    Thank you. Thank you. Thank you.

    Posted this tip to Apple Discussions:

    http://discussions.apple.com/thread.jspa?threadID=2139000&start=0&tstart=0

    … where for a long, long time, Mac OS 10 users have had troubles, not only connecting from the Mac to Windows Vista and Windows 7 machines (getting an “Error code -36), but also copying files (“Error code -41″).

    While copying attempts at the Mac command line would result in an error message: “cannot allocate memory”.

  18. Retlow
    March 5th, 2010 at 05:22 | #22

    I love the internet, and contributions like this one. Was the solution for the strange and in intermittent problem I had with Windows 7 clients. Thanks a lot!

  19. mutant
    March 5th, 2010 at 12:49 | #23

    I’m replacing a Sun Solaris 10(x86) box that I used for all backups from other machines on the LAN to Vista 64 (w/Adaptec 51245 w/24TB). This 2017 error was a major frustration. The above mods worked perfectly up to this point. I currently have four machines backing up to this box at the moment.

  20. chris
    March 8th, 2010 at 17:21 | #24

    you made my day

  21. March 22nd, 2010 at 17:54 | #25

    See here whats happening with wireshark:

    10.0.0.200 is the Windows 7 machine. 10.0.0.253 is the iMac.

    No. Time Source Destination Protocol Info
    23 6.200303 10.0.0.200 10.0.0.253 SMB Negotiate Protocol Response, Error: Out of memory

    Frame 23 (105 bytes on wire, 105 bytes captured)
    Ethernet II, Src: 02:23:54:80:b4:22 (02:23:54:80:b4:22), Dst: Apple_f2:be:60 (d4:9a:20:f2:be:60)
    Internet Protocol, Src: 10.0.0.200 (10.0.0.200), Dst: 10.0.0.253 (10.0.0.253)
    Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 49177 (49177), Seq: 1, Ack: 52, Len: 39
    NetBIOS Session Service
    SMB (Server Message Block Protocol)
    SMB Header
    Negotiate Protocol Response (0×72)

  22. Dallas Hinton
    March 23rd, 2010 at 11:40 | #26

    Thank you so much for documenting this fix. It has solved my network share issue (XP machines to a 7 server. Thanks!

  23. March 23rd, 2010 at 19:55 | #27

    I rarely comment on anything like this, but you literally just solved a 6 month problem for me. MUCH THANKS!!! /beer

  24. John
    March 28th, 2010 at 09:39 | #28

    This is great, you are doing microsoft’s job for them.
    I had this problem for a while and i couldn’t find related article on the microsoft website.
    Good Job !

  25. Rob S
    April 9th, 2010 at 02:12 | #29

    Built a new Win 7 64bit system and I have been getting several event log saying “The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.” I just entered the info in the regedit. I have been looking for a fix for 2 weeks now. Thanks I will let you know. Take care

  26. Merrick
    April 11th, 2010 at 06:43 | #30

    Worked!

    My configuration:
    Windows 7 64-bit as a host and multiple VMWare workstation clients. The clients lost the share drives with the error “Not enough server storage is available to process this command.”

    This fixed it. By the way, the first key did not exist, so I added it.

  27. Daniel Morin
    April 11th, 2010 at 09:39 | #31

    It’s working thank you!

  28. Shawn
    April 11th, 2010 at 15:11 | #32

    I have the same problem but am lost as to how to fix it. When I open regedit, I have nothing that says HKLM, I only see HKEY. How exactly do I edit it, if its not there?

    • April 12th, 2010 at 07:17 | #33

      HKLM stands for HKEY Local Machine. It will be one of the top level registry categories I believe. Drill down to find the specific keys noted in the article starting at HKEY Local Machine.

  29. Rob S
    April 12th, 2010 at 22:19 | #34

    Alan,

    You rock bro. I have been running for a couple of days now without any issues. Thanks for sharing this fix with everyone. Take care!

  30. Alec Keeler
    April 23rd, 2010 at 08:50 | #36

    Worked for me in connecting an XP VM to folders on the host, when running Workstation 7.0.1

    This was causing lots of compilion problems when using make in cygwin on the VM with make not being able to stat files

    Thanks for the info

    Alec

  31. GerryJ
    April 26th, 2010 at 08:17 | #37

    This solved the problem on my 2 Win7 64bit systems that I use as file servers.

  32. Niko
    May 5th, 2010 at 16:53 | #38

    Exactly the prescription! Thanks Doctor!

  33. Frank
    May 9th, 2010 at 18:36 | #39

    Great tip! Ran into the same issues as you did (mounting shares from a lot of other computers, including non-Windows systems). This fixes up the problem, and I’ve bookmarked you to ensure it’s among the tweaks I make on all new Windows 7 builds. Thanks.

  34. bigmoe
    May 19th, 2010 at 19:25 | #40

    thanks guys, fixed an issue ive been having for ages! :)

  35. kspn
    June 3rd, 2010 at 05:00 | #41

    Awesome! Thanks for the info I was trying to work out why my linux system was refusing to connect to my Windows 7 FileServer.

    Thanks for the info!

  36. Pimmsley
    June 7th, 2010 at 00:35 | #42

    Amazing ! thank you so much… I built a file server win 7 Pro 64bit and was having the same issues with mac clients… fix in place and testing have been 100% so far.
    Excellent work for sharing this fix.

  37. Omegis
    June 13th, 2010 at 16:09 | #43

    Thanks for the TIP !!!

  38. Naylor Braga
    July 29th, 2010 at 08:54 | #44

    Thanks my friend , I will be with same problem ,follow in his footsteps and solve my problem .
    bye

    Naylor

  39. Brian
    August 1st, 2010 at 22:55 | #45

    Hi,

    I had the same problem but following your instructions hasn’t seemed to fix my problem.

    Any other ideas?

    I can be reached at eterspam@gmail.com

    Thanks

  40. Lino
    August 2nd, 2010 at 02:55 | #46

    Hi, I’ve a very similar problem. In my case the samba server is a linux box and my windows xp is the client. When I try to copy big files (with few bytes works fine) I receive the same memory error. In this case your trick doesn’t work because the problem I suppose in on the server side but there are no Registry on linux :-(
    Any suggestions? Thanks :)

  41. the9375
    August 4th, 2010 at 09:04 | #47

    Mad props.

  42. August 4th, 2010 at 13:40 | #48

    Today we’ve faced this problem in one of the removed offices of the client on Windows 7 Ultimate (fully updated).

    Thank you! :beer:

  43. Al
    August 5th, 2010 at 15:08 | #49

    Thanks. This totally fixed my problem…

    Good stuff!

  44. Sam
    August 8th, 2010 at 14:13 | #50

    Hi, just wanted to say thank you as well. I am using windows 7 professional as a media server and to serve to a popcorn hour and western digital media player. Things were fine until I added the western digital media player, then I started to get the ‘no content available’ on both devices. It’s only been about 48 hours but I don’t see the error listed in th event viewer since I made the changes.

    Thanks a ton!

  45. BrianAz
    August 14th, 2010 at 01:41 | #51

    You rock! I had issues with my Dune media player seeing W7 SMB shares. Then I noticed the errors in my event log and a few google searches lead me to your solution. Thanks again!!

  46. erkme73
    August 19th, 2010 at 11:22 | #52

    THANK YOU THANK YOU!!! Windows 7 home being used at work (Workgroup) as a file sharing server was giving this error non-stop in the event viewer. Certain computers would give the error: “not enough server storage is available to process this command” and not connect to the shared drives.

    Thanks to Google, I found this hack, and haven’t had an error since. You are a saint!

  47. Phyllis Ingram
    August 23rd, 2010 at 15:25 | #53

    I believe I am having this same issue but my registry does not have these items in it:
    HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache
    and
    HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size
    being somewhat a novice I am not sure if or how I should try to add these items. I am getting the same error code

    Event ID: 2017
    The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

    Can someone help me figure out what i need to do. I am running windows 7, 64bit machine.

    thanks
    phyl

    • August 23rd, 2010 at 16:18 | #54

      If you are getting the same error, I would suggest you try this:

      1. Open a registry editor and make a backup of your registry
      2. Create the keys this article documents
      3. See if that fixes your problem
      4. If your problem is not fixed, use the backup registry to revert the changes you made (or simply delete the two registry keys you added.

      Good luck. Please let me know (in the comments here) if you were able to solve your problem. Thanks!

  48. mumrik
    August 30th, 2010 at 19:38 | #55

    Wow! This did the job! Someone should explain to MS that it would be a good idea to give users a hint in the event description what’s actually going on *grrr* ;-)

  49. Sean
    August 31st, 2010 at 16:38 | #56

    This worked! I’m very happy. Thanks for the post.

  1. July 21st, 2010 at 13:24 | #1
  2. August 3rd, 2010 at 03:46 | #2
  3. August 5th, 2010 at 17:33 | #3