I'm using Simba's ODBC driver for connecting Tableau to MongoDB.
I connected my workbook to MongoDB, developed my dashboard and everything went pretty smooth.
However, after I publish my workbook to Tableau server and try to open it, I get an error message:
"An unexpected error occurred. If you continue to receive this error please contact your Tableau Server Administrator.
Tableau Server encountered an error. Contact your Tableau Server Administrator.
Would you like to reset the view?"
Why can't I view this dashboard in Tableau Server?
You probably need to install the Simba's ODBC driver on the machine that runs your Tableau Server.
There are many reasons which can bring this error.
Driver mismatch on server machine.
Data volume too much for server to handle (does it take too much time for the server to load and then show this err or does it show it quickly after hitting url?)
It could simply be that there was some error while publishing the dashboard try again.
Related
I have an AWS RDS (PostgreSQL) that is inside a private network - only accessible via a VPN and Bastian Host.
I am able to establish connection from PBI Desktop to "PostgreSQL-RDS Instance." By creating SSH tunneling from my Laptop (localhost) to Bastian Host using ODBC Driver. With this approach all the data is imported onto PBI desktop(import mode).
But our requirement is to establish connection through a direct query to refresh data real time and generate the Reports Dynamically which I am not able to.
I entered the database credentials into the Power BI desktop tool, and it not working correctly in the power bi desktop, getting a Timeout Error.
I must use direct query, I can't use import.
Any help is appreciated.
An exact error that you are getting would help get to the root cause of the issue. However, a few basic troubleshooting steps that I'd suggest are:
Ensure that you have a compatible version of the software installed on your machine such as the Npgsql-4.0.9. AT times the latest version of the software usually causes issues.
Ensure that you remove the semicolon at the end of the query.
Once you get the query running successfully on the desktop version, when you publish it to the web version, the visuals will not be able to connect to the database unless an on-premises data gateway is setup. To do so, more details on setting up a data gateway to automatically refresh the dataset for the power bi web version are here:
Refresh AWS RDS database from Power BI Web you are successfully able to query directly
I'm using Power BI version 2.84 to connect to Postgresql server. In PBI desktop everything works fine, I can connect to the server, import and refresh data smoothly.
However when I publish it to PBI server, I can't refresh it anymore due to 'encrypted connection'. I have checked all of my connection settings and make sure they are not encrypted at all but the problem is still there.
Please let me know if you have any solution for this.
Cheers
I assume you are using direct query?
If you want to use direct query you will need to set up On-Premises data gateway.
on premise gateways
And then you should add gateway cluster in PowerBI web version gateway cluster:
Data gateway
I think everything is quite straightforward here.
But do you need direct query? If you are ok with refreshing your data a few times a day, you could set up a ODBC connection (when importing data, choose ODBC option not postgresql).
You would need to set up ODBC drivers, (Control panel -> Administrative tools -> Data sources) And create a new one (you should download Postgresql ODBC driver if you have none)
Then you also need to create On-Premises data gateway and set up refresh intervals.
I'm new to crystal reports and have been having an issue. The report is able to print properly on my system and on their host server however they have another server where everyone connects in through in and whenever we try to print from that server this error code pops up.
Any advice for a resolution is greatly appreciated.
Error code:
The server that the report is ran on when this issue occurs - as the message suggests, it seems like the table 'currencies' which you are using in the report does not exist in the database you are using on that server.
I suggest you logon to that server where you get the error message and make sure the 'Currencies' tables exists via SSMS.
I am getting the following error when trying to preview an RDL report.
I have full rights to the SQL SERVER
I have tested my connection to the datasource and it's fine
I have full rights to the reporting services (serverName/reports)
My datasource is set to windows authentication
The event viewer both on the local and remote machines shows nothing
SQL SERVER logs show nothing
Please note: this report is embedded within an on-premises CRM instance, but I need to update the report.
What am I doing wrong? Any troubleshooting guidance would be most appreciated.
In that case run your report in new solution / another solution. Your issue will sort out.
I faced the same issue. Now sorted.
We deployed a VB.Net application on a customer's computer that contains SSRS reports.
The application connects to the SQL Server database in the app without any problems. We installed SQL Server Data Tools so we could deploy the reports (rdl) and data source (rdl) files up to the report server. These deploy without any problems.
In SQL Server Data Tools we can "Preview" the reports without any problems as well.
We do run into a problem when attempting to view the report from Internet Explorer (run as an administrator).
We get the following error:
Cannot create a connection to data source 'DataSourceReports'
(this is the name we used for the TargetDataSourceFolder)
error:40 - Could not open a connection to SQL Server
We also get the same error when the app we deployed runs the reports.
Please let us know what is not set up correctly on the SQL Server side.
A likely possibility is that you are experiencing a double hop authentication problem. It's not clear from your explanation, but is the SQL Server database on a separate server from the report server? If so, then your credentials allow you to connect to the report server but Windows integrated security does not pass those credentials on to the SQL Server database if you are using NTLM on the report server. The report server tries to use Kerberos on your network to authenticate by way of ticketing to the SQL Server database, but you must have this configured correctly on your network. See this article if you want to use Kerberos: http://technet.microsoft.com/en-us/library/ff679930(v=sql.100).aspx.
Another (easier) solution is to open the data source on the report server and change the authentication to use stored credentials. Make sure the credentials you use have read permission on the SQL Server database. The downside of this approach is that you cannot use row-level security in your report by user unless you design your report to capture user information and set up the query or a filter on the dataset to restrict data by user. If that's not a concern, the stored credentials are easy to set up and maintain - and you're going to have to do this anyway if you want to use caching, snapshots, or subscriptions. For more information on stored credentials, see http://msdn.microsoft.com/en-us/library/ms159736.aspx.