Sorry, I should have learned to wait just a little longer after four
years of dealing with seti@home's servers.  The problem apparently was
a server problem, because it resolved itself immediately after I made
the previous post.

I will now slap myself around the room several times.