It sounds like the change to the data source broke the first workbook so some field was in use that was modified. Can you modify the published workbook in Desktop and then republish?
I have tried a number of changes in desktop, and it works fine there in the desktop app. However, the published version won't run. Other published workbooks are working fine.
2 of 2 people found this helpful
I'm having the same issue publishing a workbook in Tableau Server 9.0, while the second tab loads perfectly from the same underlying data source. I get "Unknown Server Error: An unexpected error occurred. If you continue to receive this error please contact your Tableau Server Administrator. Would you like to reset the view?"
Selecting yes just repeats the error. The workbook appears published but as Alisha notes, the error occurs on Tableau Server too.
Details of my instances:
Tableau Server Version: 9.0.2 (9000.15.0527.1215) 64-bit (via Chrome v43.0.2357.124)
Tableau Desktop Version 9.0.0 (9000.15.0318.1720) 64-bit (Windows 7)
The only bug fix in release notes mentioning a Logic Exception on Tableau Server dates back to 9.0.0 (April 6, 2015):
When using web authoring to edit a published workbook, if you deleted a sheet, then added a new sheet and saved it with the same name as the deleted sheet, an error displayed: "LogicException: Internal Error An unexpected error occurred".
There was mention of an Internal Error being resolved on Desktop 9.0.1 but it was specific to binning:
When creating bins on a measure with a name that includes the percent (%) character, the first bin was created successfully, but a subsequent attempt to create a bin would result in an error: "Internal Error An unexpected error occurred and the operation could not be completed" or Tableau would close unexpectedly.
I am also having the same problem. is there any resolution for this?
What version of Tableau Server and Windows Server are you using?
Even i get same error on Tableau desktop 9.1.1 and server running on windows server 2012 Standard Intel(R) Xenon CPU X5650 @ 2.67GHz 32 GM RAM.
Did anyone had same problem with mentioned server configurations.
1 of 2 people found this helpful
Alisha, I solved this issue by getting rid of the null values in my dataset/worksheet/dashboard. Obviously, this may not work for you but good luck.
1 of 2 people found this helpful
I had this exact same issue, and it turned out to be caused by publishing a dashboard built by a version of desktop (10.2.2 in my case) that was more advanced than the Tableau Server version (10.2.1 in this case). After I upgraded my server to the latest version, this error went away.
I also have same issue for multiple dashboards even both server and Desktop have the same version : 10.2.3. Removing NULL resolves the issue but a lot of work. It appears to me that Tableau 10.2 handles NULL differently than that of V10.0 as those dashboards worked perfectly before 10.2 upgrade. Here is an awesome summary of Tableau NULL handling https://community.tableau.com/docs/DOC-6244
1 of 1 people found this helpful
I know your post is a few weeks old - but do you recall if this issue was widespread (like all your views wouldn't work) or if was only some of them ? I am just running into this, but I've been a bit ahead of my server for a while. I've tested other view by republishing and they don't hit the same issues.
We too got the same error when we recently upgraded to version. 10.2.3 (10200.17.0614.1936) 64-bit. We have fixed in one report where NULL is coming but we have many reports having same issue. Did you guys got any FIX from Tableau support . Could you please let us know status on this.
I have asked publishers to fix their problematic workbooks one by one by changing the NULL for the fields used in filters. I have not had updates from Tableau about the fix yet although I sent all details about this bug to Tableau Support.
Sent from my iPad
Here is recent response I got from Tableau Tech Support :
The "LogicException: Internal Error - An unexpected error occurred and the operation could not be completed." error message that you're encountering is due to a Known Issue that was addressed in Tableau Server 10.3.1.
The fix for the above Known Issue is also being backported into a forthcoming Maintenance Release of Tableau Server 10.2.
I am working on Tableau Desktop 10.3.2 and Server 10.3.2 and am receiving this error.
I have tried "fixing" the NULLs to no avail.
Has anyone heard of this still happening?