I did everything they said reseting and that didn't work Then I uninstalled(since I lost all my wu's) and reinstalled. . Now it says it can not connect to the server database. What a mess. Guess I just turn the whole thing off for a couple of days and try again..

I should have read this before I follow the recommendation on the known issue post. Like everyone else, I lost over 60 hours of work and everything went to waste....sigh....

Everything is reset, and nothing is left. Please update the known issue page and warn users that resetting will cause them to lost all their work. We don't want any more wasted computing power for the rest of the community!

nelsoc's post about hitting "retry communicatons" doesn't work.

Generates an error that the server cannot open the database.

I believe that none of the problems at the moment are 'fixable' at the client side. At a guess, the admins made some changes (perhaps to address what they saw as an SSL handling issue, perhaps something else). Those changes had 'unintended consequences' -- and so there was a bit of 'flailing about' regarding 'try this, try that, try something else' as suggestions at the client side -- none of which worked, some of which had adverse effects.

So a 'do nothing' approach on the client side makes sense for now. Of course that means there won't be data transfers until the project side figures out what effects their changes had and either reverts to a previous working configuration or can provide clear, cogent, working instructions for the client side changes needed.

I would hope to see something on the home page for that as most clients don't want to go into Dr. Who mode to track down solutions deeply embedded in the newsgroups.

I just got new work.

However temporarily, work is flowing.