bruce wrote:Since Mid-December is a long time, is it possible that you're getting an error 503 from some other server between you and Stanford? It's possible (though unlikely) that a router somewhere has been overloaded, too.
Has your client been running continuously and have other WUs been uploaded successfully to other servers?
On this particular (multi-core) computer I run continuously with 2 clients (one GUI-client (the one with these problems) and one command-line client (but that one works fine)). In the period I only restarted the computer once. At startup the GUI-client starts automatically. But it sometimes crashes after a while, which results in a Visual studio request if I want to start debugging it (therefore I notice it) and thus I manually restart the GUI-client. This happened also 1 or 2x in this period (and both times I restarted the GUI-client).
Thus most of the time the client was online and capable of sending the results.
According to the logfile other WUs (which started before and after the one giving the problems) were uploaded without problems.
Also my other computer (with 2 command-line clients) and my PS3 don't show this problem (and all are sharing the same router to connect to my ISP). That is why I suspected the WU-server.
bruce wrote:You are in "good company" though. There are a number of other reports of problems with this server, so there's probably nothing you can do.
That is why I waited that long before I posted here. It has happened before that a server was down and I had to wait 1 or 2 days before the results were uploaded.
toTOW wrote:I also see the wininet error that was typical with a bad setting in old v5 clients ... if you're using this old client, make sure you disabled the "use IE setting" option.
/*quick-check */ The GUI-client is a v5-client (5.03) and it *had* "use IE setting" enabled. Although, as I replied to bruce a few lines back, other WUs were uploaded correctly and I never had this problem before. (The only problem I get is that the GUI-client sometimes (once a month) crashes and than I have to restart it by hand).
But it is now disabled. Let's hope that that resolved the problem.
BTW. The only reason that I still have this GUI-client is that I'm too lazy to uninstall it and replace it with a command-line version, since most of the time it is working correctly. (As you can see I'm not that great a fan anymore of the GUI-client, since it is the only client with which I have had problems. Note: The command-line client I use on this computer is also a V5 (5.04) client)