Same thing happened to me the other day. Upgrading to 6.0.2 resolved the issue.
Thanks Joe... we'll do the upgrade tonight after all our clients have logged off for the day. Hopefully we see the same results you did.
Would have been nice if some sort of warning message had been displayed.
That message does come from beta builds, which expire in 45 days. Yesterday would put the beta date back to about November 5th or so.
Regular license expiration has good nagging/warning for two weeks before expiration, but I'm not sure if beta expires use that same system.
Regardless, this is something very strange that should not be possible in 6000.10.1103.2100 (though obviously it is somehow). It's actually built straight into the product, so it's hard for me to be fathom how you could still be running the beta bits/code after installing the GA.
Edit: we are investigating this issue and have multiple customer reports. Yes, including yours Jamie.
I have the same issue (under 6000.10.1103.2100), with one exception:
the problem is intermittent. Sometimes the respective operation succeeds,
sometimes I get the error message discussed in this thread.
The two affected operations are uploading a workbook to the server
from T-Desktop 6.0, and downloading a previously uploaded workbook
from the server to my local machine.
I have not yet found a specific time interval for the failure.
Seems to be Russian roulette.
Our sys-admin is gone for the holidays, so I don't have access to
a 6.0.2 download. Will you post any insights you gain from your
One more data point about the failure:
I just tried to upload a workbook from
the desktop to the server. The upload
process found the version of the workbook
that was already on the server. Desktop asked
whether I want to overwrite. I OKed, and
then the failure occurred. So the interaction
can go part of the way.
Maybe that helps?
6.0.2 is freely downloadable at http://www.tableausoftware.com/products/server-trial (though if your sys admin needs to do the upgrade, that probably doesn't help you).
Support and Development are working hard on this issue as we speak (as I write this?). Contact firstname.lastname@example.org to get yourself in the notification loop if you have an affected server, and stay tuned for updates.