I have the same problem, I have 20 million rows in my fact table, could that be the problem? Any resolution so far?
I'm curious, did either of you get this resolved? We haven't officially switch over to 6.1 but I just tested it against my cube(SSAS 2008 R2) and had no issues. I pulled in over 38,000 rows of data with multiple measures and it all looked good.
I have one fact table that has close to 1.5 billion rows of data and it's partitioned out in sizes ranging from just over 2.2 million to 30 million so I don't think 20 million rows in your FACT table would be an issue.
We're investigating a 6.1 bug we're calling "#Error when System locale does not match database locale" specific to Analysis Services that we think may be the issue you're hitting here. Stay tuned for more details as we continue to investigate this. In the meantime, check your locales to see if this condition fits your situation?
SQL Server 2008 R2 SSAS Collation - Finnish_Swedish (Accent Sensitive)
SSAS Language - English(United States)
Windows 2003 R2 64 bit sp2 - Regional and location settings US English
Changing collation is not an option.
I have the same problem. My locales in Tableau is Danish and if I change the locale in Tableau to English (US) or my Windows Regional setting to USA then I still have the same problem.
A fix is needed please
Can you tell us when this bug is fixed? I'm preparing a demonstration for a prospect that uses a ssas cube.
A fix is needed indeed asap
This did not make the 6.1.1 maintenance release, but the fix is currently undergoing validation and with any luck should be included in our next maintenance release. I'll update here if that turns out not to be the case.
That is the timeline for the next maintenance release.
One of our customers have started delpoying 6.1 and will have to role it back if this issue is not resolved soon.
You can look at the release notes page for historical release dates and patterns: http://www.tableausoftware.com/support/releases
But I cannot promise a timeline for this next release, other than our general "we release monthly" maintenance schedule.
In extreme emergencies, you can contact support and talk about the possibility of getting an untested build.