I've created a Crystal Report project with MS Access DB backend on our development server in 1st. Step. The path is smth. like H:...\db\my.db. After compiling the project, I've deployed it on another Server and start it over mstsc.exe to open a remote session on it.It functions.
In step 2 I inserted a subreport with a data source in the same db and linked it with the main report over id field. Checked it on development server and copied to production one. Now, when I try to stat the report I'm prompted to log in and the Server and Db name are shown to be ones from development server.
Is there any way to set all reports data sources and links programmatically at the runtime?
Can you use integrated security? Or did you want the connection's userID and password stored with the report?
Related
SQL Server 2016 reporting. The SSRS service runs as an account that has read access in the database I'd like to run reports from.
I'd like to create a server level data source object that would use the Windows service account to connect, instead of storing the credentials in the data source itself. Is there a way to do so?
The "Without any credentials" option doesn't work, I've tried.
We have an SSRS with Oracle as data source. Creating report Works, but creating subscriptions doesn't.
On the Data Source configuration page,i use Oracle internal user and enabled "Credentials stored securely on the report server". If i click Test Connectiong, it says the connectiong was succesful.
Creating a subscription gives the error "Subscriptions cannot be created because the credentials used to run the report are not stored, or if a linked report, the link is no longer valid."
Something i found out is that the reports i create have as data source :
Data Source=localhost;Initial Catalog=Production and Windows Integrated Security as credentials.
Shouldn't Oracle be the data source and what can i do to correctly configure the subscriptions?
seems datasource credentials are your windows credentials, try changing it to your oracle database credentials. check below link for more information of connection strings.
https://learn.microsoft.com/en-us/sql/reporting-services/report-data/oracle-connection-type-ssrs
I am trying to set up the scheduler for reports in SSRS.
I currently have read access to query the
database needed but I now need write permission to develop
and schedule reports according to this article.
What's the minimum database write permission that would allow me
to run and schedule reports in SSRS? I am using read
access just for using SSRS and not for any DBA work.
You don't need any database permissions to set up a schedule.
First, your SSRS reports live in the Report Server database specified in the Reporting Services Configuration Manager. If SSRS did not have write access to it's own Report Server database, you would not be able to create reports or any other content.
You are probably accessing another database with customer data with read only access. You do not need write access to this database to create schedules.
SSRS accesses the report server database via the account configured as a Service Account in the Reporting Services Configuration Manager.
You will have to have your user granted the necessary permissions in SSRS in order to create and modify schedules. You can configure that by clicking the gear at the top right. If you are in the Administrators group on the local machine you will have full admin rights to the SSRS portal (that is the BUILTIN\Administrators role and it will override any permissions set in SSRS).
Schedules execute via the SQL Server Agent on the SSRS SQL Server. Your service account should be able to create and execute jobs via SQL Server Agent.
If all of this is set up right and you're getting a specific error trying to create schedules, I encourage you to post that information.
We are planning to deploy reporting service using Microsoft Reporting Server 2012. As I understand it, there will be three components;
Database (SQL Server)
SSRS (Reporting Server)
IIS (Web front end) - SharePoint (alternate Front end)
In setting up the Proof-of-Concept, the dev installed SSRS and SQL Server on same box (let's call it the DB server) and is redirecting client browser to a URL on DB Server from web front end.
Is it possible to architect the solution so that the web front end is the only destination for client browsers, SSRS lives on its own dedicated server separate from both the Web server and the DB Server?
How will authentication work in this scenario? We are using integrated authentication using Enterprise AD.
Configurations I have used in the past are these:
SQL Server on one server; SSRS native on another server. Users accessed reports via the SSRS Report Manager web UI that comes with SSRS.
SQL Server on one server; SSRS install in SharePoint Hosting mode on another server. Users accessed reports via SharePoint.
I am not 100% sure what you mean by “web front end is the only destination for client browsers”. If you mean that the end user only hits a web server, and not the database server to get reports, then either one of the above will work. If you have an existing intranet site that you want to host reports in, you can do so via web parts, if you are using MS technologies. You will still need SSRS setup somewhere so you can deploy reports, and the web part would read from it. Or, you can continue the redirect to either Report Manager or SharePoint if you go that route.
As far as authentication: the authentication between SSRS and SQL Server is usually done via an AD (Active Directory) user/service account that SSRS runs under, and also has access to the databases is uses on the SQL Server.
The authentication that allows users to browse and execute reports is usually done via AD as well. You can add all users to a central AD group and give that group Browser permissions on the SSRS server. This authentication would still apply if you use web parts to host reports outside of SSRS Report Manager.
The authentication that SSRS uses to pull the data that ends up showing in reports is usually SQL Server authentication, or whatever authentication that your data source supports where you can send a user name and password (which is stored within a shares data source on SSRS).
More Info
I am using Report Server 2012 and Report Builder 3.0. I defined a Analysis Services Data Source on the server where I provide windows credentials to access the server.
When I want to add a dataset in Report Builder based on this data source I have to enter credentials. Why? They are defined in the shared data source on the server....
My understanding was, that the data source defined on the report server will use the credentials defined in the data source and not the credentials of the calling client application.