Insufficient disk space to continue indexing - Fixed by relocating Index to another drive

One day recently, on my personal Windows 7 Home computer, I began noticing that indexing of my Outlook Exchange box was incomplete.  I know that in those situations, I can go to Indexing Options in Control Panel, then Advanced and click to Rebuild the Index, but a strange problem occurred.  The Indexer showed an error I'd never seen before: "Insufficient disk space to continue indexing. Search results might not be complete".

This was even more strange considering I have a 2TB C drive with 1.8TB free!

I tried rebuilding the index, just to encounter the same error.  I edited the registry to force Windows Search to restart/rebuild itself, but had the same issue.

Finally after troubleshooting for what seemed like hours, I found craigp's thread outlining his success on this post entitled "Indexing "insufficient Disk Space Error"" here (about 4/5 down the page): http://forum.wegotserved.com/index.php?/topic/10310-indexing-insufficient-disk-space-error/

He had moved his Index Location to his D drive and that fixed it.

Not having another physical internal drive to point the Index to, I went ahead and partitioned my C Drive and created a 10GB L:\ Drive (I had a lot of drive letters already in use).  I created a folder called Windows Index in the root of that drive (you should make a folder in your new location for the Index to go).

I then went back to Indexing Options in Control Panel, then Advanced and clicked the Select New button to specify a new Index Location path and pointed it to L:\Windows Index.

The Index proceeded to rebuild, and is now working fine!

Mac OSX Connection Failed Accessing Windows 7 Shares - Memory Allocation Error

We had a customer who wanted an inexpensive way to serve shares to about 10 computers in their office, and we put in a high-end desktop with Windows 7 Pro.  The "Server" worked fine for this purpose for all of the XP and 7 computers in the office, but the owner had an iMac which would consistently connect to the SMB shares and act fine, and then disconnect and not show any computers available on the local network.

We tried everything from going from wireless to wired, to checking sharing access, but nothing would fix it - it was always temporary and the next day we'd get a call that he was disconnected again.  His error would conssitently say "Connection failed: The server 'xyz' may not exist or is unavailable at this time" and look like this:

Finally we came across this article entitled "Windows 7 Nonpaged Pool Srv Error 2017" located here: http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

Essentially, the article states that in certain situations when Linux/Unix-based computers are accessing Windows 7 shares (Macs are Unix based), Windows can run into memory allocation issues.

The author of the post noted in the Windows Event Viewer that there was an Error 2017 reflecting the following:

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.

We checked our Windows 7 "Server" and sure enough had tons of this exact error.

The solution below, suggested in that article, worked for our client and they are no longer calling us about this issue:

On the Windows 7 computer, 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

Reboot the Windows 7 sharing computer and the problem should be solved.

Hopefully this works for you!