Search failed error - need help
i get this in the log... Search failed. Make sure that torrent client {uTorrent 1.6.1} is running and that at least one torrent is working. can someone explain what that is and how to fix it. TIA

That error happens when you select the "Always get new values" option, which parses the values from your real client (utorrent in this case) to NRPG (peer id, port, client key), you need to have this option enabled when you are using NRPG alongside your real client in the same tracker. If you are not using NRPG and utorrent at the same just ignore the message or disable the option because NRPG will generate values by itself. To avoid that message you have to turn on utorrent or disable "Always get new values" option.

Thanks jvs! I just wanted to add that that error won't cause you any trouble if you're not using NRPGRM along with your real client, just ignore it

i get the same error. i have ut 1.6.1 running and it is uploading a torrent, but i get this error in NRPG, 12> Client changed: uTorrent 1.6.1 <12> Looking for utorrent process... <12> utorrent process found! <12> Search failed. Make sure that torrent client {uTorrent 1.6.1} is running and that at least one torrent is working. it can see the utorrent process, but can't search for the strings. on the other hand, i opened RatioMaster 1.3.5 with the memory reader and it was able to read all the strings successfully. how do i fix this with NRPG.? thanks.

This message has not only been driving me nutz, but keeping the program from working on my system. Thanks a billion for solving this! BIG help jvs, am celebrating. Soon as I unchecked it, the program started singing along again, no errors. I was using Ratiomaster along with the client, but it kicked up a remote error along the bottom as well as this same message in the log.

I've been having the same problem with the la-*test*-('") version too :/ Seems like the memory reader is simply not working. I'm on Windows Vista with uTorrent 1.6.1

Yea, know what you mean... celebrated too soon as mine didn't keep working afterward. Still having this issue, no resolution so far. Maybe next version? Let's hope. Good luck with yours! :^)