Request new token no longer working?

[Jonathn]

Hullo,

I just thought I'd ask this question; your previous posts suggest to fix the problem with invalid token, you need to request a new token, well, I do this and for some reason it still fails immediately afterwards?

Debug information:

Quote:[2009/07/03 16:35:03] SERVER - Sending pulse
[2009/07/03 16:35:04] SERVER - Invalid token
[2009/07/03 16:35:07] SERVER - Connected
[2009/07/03 16:35:07] SERVER - Sending token reset request
[2009/07/03 16:35:07] SERVER - Token reset
[2009/07/03 16:35:24] SERVER - Connected
[2009/07/03 16:35:24] SERVER - Requesting latest client version
[2009/07/03 16:35:24] SERVER - Latest client version received
[2009/07/04 10:31:27] SERVER - Connected
[2009/07/04 10:31:29] SERVER - Requesting latest client version
[2009/07/04 10:31:29] SERVER - Latest client version received
[2009/07/04 15:16:26] SERVER - Connected
[2009/07/04 15:16:29] SERVER - Requesting latest client version
[2009/07/04 15:16:32] SERVER - Latest client version received
[2009/07/04 15:17:01] SERVER - Connected
[2009/07/04 15:17:01] SERVER - Sending pulse
[2009/07/04 15:17:04] SERVER - Invalid token
[2009/07/05 01:08:41] SERVER - Connected
[2009/07/05 01:08:41] SERVER - Sending pulse
[2009/07/05 01:08:43] SERVER - Invalid token
[2009/07/07 23:40:57] SERVER - Connected
[2009/07/07 23:40:58] SERVER - Requesting latest client version
[2009/07/07 23:40:58] SERVER - Latest client version received
[2009/07/07 23:45:58] SERVER - Connected
[2009/07/07 23:46:02] SERVER - Requesting latest client version
[2009/07/07 23:46:03] SERVER - Latest client version received
[2009/07/07 23:47:08] SERVER - Connected
[2009/07/07 23:47:08] SERVER - Sending pulse
[2009/07/07 23:47:09] SERVER - Invalid token
[2009/07/09 10:55:09] SERVER - Connected
[2009/07/09 10:55:11] SERVER - Requesting latest client version
[2009/07/09 10:55:11] SERVER - Latest client version received
[2009/07/09 15:57:23] SERVER - Connected
[2009/07/09 15:57:23] SERVER - Sending pulse
[2009/07/09 15:57:24] SERVER - Invalid token

I'm unsure how to proceed with this; I've got close to a million keypresses ready to pulse, and I know that when I reset the token, again, it's not going to work... Quite a few keypresses wasted.

I have a profile for my Tower and for my Laptop and I don't let the two cross over, so using the same profile on many computers isn't causing this issue.

Is there any practical suggestions you can give me to get this working again? I quite enjoy whatpulse to manage my keypress stats, but as of late it's not working out so great.

Thanks guys.

Jonathan.

[bobL]

I don't get it. How do you have one million keys if you keep resetting your token?

[Jonathn]

I reset it last 10 days ago. I do an awful lot of work on my computer. It's been doing this for months though. I lost all my keys last time too.

[bobL]

System specs

[Jonathn]

Windows Vista Home Premium x64
AMD Athlon 64 X2 Dual 5400+
4 GB RAM

Whatpulse prog. ver. 1.6.2.1

[bobL]

That's probably why, we don't support x64.

Wait until the next version, that might help but no promises.

[Jonathn]

That's odd. It's always worked previously Well. Thanks for clearing that up anyway.

[c-smith]

You should probablly try setting the Whatpulse client to pulse every 10k keys or so just so if you do get a problem you don't loose to much