I have seen cases where the "Uncaught TypeError: Cannot read property 'moveNext' of null" error was resolved by disabling client-side rendering.
To test please append the following parameter below to the URL of the view:
If the above test resolves the issue, you can disable Client-side rendering globally across Tableau Server by following the steps below:
1. On the Tableau Server machine, click the Start button, and then select All Programs > Accessories
2. Right-click Command Prompt and select Run as administrator
3. Type one of the following commands, based on your operating system:
On a 64-bit machine: cd C:\Program Files\Tableau\Tableau Server\[version]\bin
4. In the command prompt, run the following command:
tabadmin set vizqlserver.browser.render false
Please Note: Globally disabling client-side rendering can impact performance in other areas, and is not recommended as a permanent solution. I believe that it will be worthwhile to Submit a case to our support team.
You're in good hands with Paul
As a FYI - I had an issue sometime back ISSUES - Tableau Server 9.0.5 + Chrome 45.0.2454.85
Its probably not be connected at all, but I thought I would link the thread just in case... you never know!
These are always useful to read through...
Known issues > Known Issues | Tableau Software
Release notes > Release Notes | Tableau Software
Download site > Alternate Download Site | Tableau Software
Best of luck - if you find the issue/ solution please post back and share!
PS. I will move this thread to Server Administration.
I hope you're well?
Have you followed Paul's advice/ suggestion?
Paul works for Tableau support... I would try his advice first
By the way, what version of Desktop/Server are you using?
Thanks , I am well :D ohh yes I am just now testing with this "render=false" parameter and it seems working well. :) So should I follow the server setting steps as Paul wrote and that's all?
Thanks , I am well
Good to hear!
Paul's solution is a way round the problem, but it needs to be added individually to each viz.
(for performances reasons) Paul suggests not making a permanent change to the global settings but instead raising a support case with technical support - I guess that is to try and understand the problem and fix it instead of just working round it... it maybe that technical support make that change global, but its probably best for them to investigate first!
Sorry its not a complete solution but I hope it helps!