Resolved Question

Runtime Error R6016

Hello Guys,
I get on a computer the "Runtime Error R6016 - Not enough space for thread data"
I looked on Google, not very helpful.
I do not want to install anything to fix the issue and I don't want to restore the computer.
I was wondering if anyone could help me fix the issue without installing any other software.
The computer has Windows 7 and the error message appears with the path to C:\Windows\system32\..hostprotocol.exe or something like this, can't remember for sure.
Thanks in advance!

Discussion is locked

NickNn1 has chosen the best answer to their question. View answer
Reply to: Runtime Error R6016
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: Runtime Error R6016
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.

Best Answer

- Collapse -
I don't think you can be helped.

All the fixes I've read involve installing this or that or some system restore (which is NOT system recovery.)

HOWEVER "hostprotocol.exe" is more interesting. You could try disabling the indexer. This is all over the web but I see John Rudby tell how at:

I'd try that.

But I fear it's the usual malware infection but as you don't want to install anything you may have to muddle along.

- Collapse -

That's a computer at work, I did the /scannow, chkdsk commands and no errors in result, checked if Visual C++ needed repair, nothing, we have a good AV program, Virus definition is up to date, No Windows Updates to be is frustrating...system restore is impossible as the user has made a lot of modifications to the files, it will only annoy him don't even dare saying about reinstalling the Windows.
Thanks Bob, will keep trying to fix it, even though have no clue how Grin

- Collapse -
Oh, it's not yours?

Did you disable the indexer?

System Restore does not affect user files. And no one goes without backups. I mean what if the HDD just fails? Are they ready?

- Collapse -

Didn't disable the indexer as it may not be good for the user, he is creating quite a few files, scanning and sending e-mails, It will only create problems in the future i believe. The error happened once.
The PCs get backed up every night, so if I will do a restore in the afternoon there will be a bit of information lost as the users have the good habit of saving the files locally.
I was thinking to copy the SearchProtocolHost.exe from my PC to the user's.

- Collapse -
We've disabled it for years.

Can you share the downside?

- Collapse -

Not sure what downside is, This is my first thread.
I believe you want an image of some sort about the error.
I can't provide any screenshots due to company's policies.

- Collapse -
I understand that.

Since it's a company just move to calling Microsoft for a fix. I worried you would not find a solution due to the limits you lead with. However there was a clue there and something I would try to lighten the load on what can trigger that error.

- Collapse -

The error message has like title Microsoft Visual C++
Says : Runtime Error R6016 Not enough space... and the path : %Windir%/system32/searchprotocolhost.exe
Can't say more than this I'm afraid.

- Collapse -
Which is why I thought about the indexer.

We know it can blow up on some files and since replacing it from another machine is never the right move (we use SFC to check the OS files) I thought the next move is to turn that off.

There's other tweaks to the indexer such as limiting what folders it works on but as you appear to be the IT lead I'll let you try that.

- Collapse -
I am new in IT and I know it

I am sure I am an IT newbie, You know the thing better than me, I worked in IT for less than a months, quite sure you have years of experience. Don't understand how turning the indexing off will solve a problem that appears once every 90 times(the lowest number I saw on forums)
Thanks for your help any ways, sorry for taking your time.

- Collapse -
No problem.

I'm sorry I was unclear. Sometimes with Microsoft products there is no "cure" except to avoid what triggers the problem. Since we know that indexing can blow up, we can side step the issue by turning it off or limiting what gets indexed.

Here's a really old example. It's very old. Long ago I found a .jpeg that would lock up Windows Explorer. Worse yet, if you copied it to the desktop then the user's account would lock up on log in.

I thought it was a fine thing to carry with me to a Microsoft seminar and ask for some help. What happened?

After explaining the issue to Microsoft (I was in Redmond no less) the response was "Don't do that." and "Don't put that file on the desktop."

At no point did any softie consider this to be an error or bug worthy of fixing. For me this was a great lesson in how Microsoft works.

- Collapse -
I see what you mean now

I will unchek the box in the properties of the disk then, or will consult with the manager which ones to uncheck from the advance list and will see if the user will experience the problem again in the future.
I only thought the issue could be resolved as you would resolve a printer issue, can't print, check the ink, paper, printer on...yale yale...
I saw on forums ideas of modifying the code in order to solve the issue, as a 1st line, don't think I can do that or use any known good software other that the ones we have license for.
Thanks for your help!

- Collapse -
Good luck.

Sorry it took this many posts to share the stories why I thought about this change.

- Collapse -

If you share this with one or more other users, then it's likely each user has had a quota set on how much hard drive space they are allotted. So, it can appear you have half a drive left of room, b ut still have hit the end of your quota assigned by your boss or IT department for each user. In XP it's in the performance area I believe.

CNET Forums

Forum Info