I am using Tableau version 8.0.0. When i publish the report in Live server i get the following error **"TableauException: Field '[ACCOUNT_SCHEDULE_FACT].[DATE_DM]', which is included in a join clause, does not exist. Unable to connect to the server ". I have verified that the column DATE_DM exists in the table ACCOUNT_SCHEDULE_FACT. The server is up and running. The join condition in the report has been verified even for case sensitive issue.
However when i publish the same report in Development Server or when i check it in desktop (without publishing) it does not throw any error and works smoothly. The custom sql from tableau has been executed in our sql server database and it returns correct number of rows. Can somebody point out why this error is occurring or whether there is any workaround for this problem?
Thanks and regards
Gautam
Related
I am using DB2 receive location in BizTalk 2016 configured with select query in SQL Command field. When I try to enable the receive location, I am getting the below error message.
The adapter "DB2" raised an error message. Details "There was an error in the Receive location with URI: DB2://XXXX:XX/XX/XXX. Internal message: Couldn't parse object name from polling statement".
I came to know that problem is with CASE statement inside query statement. When I remove CASE statement, it is working as expected. But the same query including CASE statement is working in BTS 2013 R2.
I tried installing latest cumulative updates for both BizTalk and HIS i.e., BizTalk 2016 CU7 and HIS 2016 CU3 and still the issue is not resolved. Can any one suggest the resolution or fix available for this?
Move your query to a stored procedure, and have the adapter poll that.
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.
The context is OLAP cube development. After configuring my project though SQL Server Data Tools (SSDT, the new BIDS) I am unable to deploy the project.
Every time the deployment process is started I get an error like the one below:
File system error: The following error occurred while opening the file '\\?\D:\[...]\database\mssql\tmpdb\MDTempStore_1864_9_no8wd.tmp': Access is denied.
(The [...] denotes some part of the path I ommited for brievty)
I always get the same error, indicating that some .tmp file could not be accessed.
My environment:
OS: Windows Server 2008 R2 Standard, SP1
SQL Server: SQL Server 2012 (v11.0.2100.60), running on localhost
What I tried:
I have the File System access rights for the folder in question (at some point I even tried with Admin privileges on the machine, didn't help)
I tried to deactivate the anti-virus in case it was performing on-access-scan (still didn't help)
Attempts to deploy/process individual dimensions causes the same problem
Deploying dimensions or cubes programmatically through SMO (instead of SSDT) runs into the same problem
Deploying DataSource objects as well as DataSourceView objects works fine
Maybe some of you faced similiar issues or have further suggestions/ideas?
Thanks for you help!
So, I finally figured it out.
As expected it was a permission issue, but despite the error message hinting at some missing file system permissions, the cause of the problem was the user I configured the Data Source with.
The SQL User I specified was given the roles
db_datareader
db_datawriter
db_ddladmin
on the source database but this doesn't seem to be enough. When I tried to give him the server role sysadmin it started working.
This is probably overkill, one could further fine-tune the role assignment but for now it also works that way.
Just a suggestion here - have you tried running SSDT as an administrator? That is, right-click on SSDT and click Run As Administrator. Then try to deploy your project. It definitely sounds like a permissions issue.
Exact reason is SSAS Service user does not have an access to the folders that are specified in SSAS configuration (i.e error states it is Temp Folder). I think it is not directly related with SQL Server because it is just a file access error. Error is thrown before it reaches SQL Server.
Give full permission to SSAS Service User for those folders.
Regards
Onur
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.