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!
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!
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.
I applied these setting and so far i haven’t had a freeze on large number of file transfer.
Good Job Thanks.
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.
@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!
Many thanks!
What alive saver.
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!
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
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.
Thanks so much for posting! This was driving me nuts before I found this solution.
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.
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.
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!
Thanks for the confirmation! It’s good to see this working for so many people.
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.
Seems to have fixed my problems to thanks!