I have an SSRS report that connects to an cube using a shared SSAS data source with integrated security. In visual studio the report works fine and connects successfully. Once I deploy it to the report server (sharepoint 2013 integrated/sql 2012) then it won't work and gives an access denied error.
My user is an admin on the SSAS instance so security is not the issue. Can connect fine with ssrs in visual studio, excel, ssms. Only once the report is deployed and run in sharepoint it doesn't work. Similar error if I go to the data source in sharepoint and try to test the connection.
I believe the problem was that even though my user had permissions. Using integrated security causes a double hop problem (computer ->report server -> db server) in order to authenticate. By using stored credentials on the report server is solves the double hop problem (report server -> db server).
Related
I have downloaded, installed, & tried to configure evaluation copies of 2019 SQL Server & 2017 SSRS.
When I used Report Server Configuration Manager, I put my new instance of the SQL database engine (MSSQLSERVER05) into the database name.
This connected properly.
Through multiple tries, I have created multiple report servers & temp report servers.
However, when I try to access SSRS from the Object Explorer of SSMS 18.5, 2 old DB names & "SSRS" are the only instances I see.
I have tried using SSRS, but the error says the reporting service instance cannot be found.
If I type in the name of the new database engine (MSSQLSERVER05), I get the same error.
I have had earlier trials of SQL, but tried to uninstall all of them.
I notice that the file rsreportserver.config has "SSRS" in it as well as a coded database name.
This likely needs to change somehow. I would appreciate any help!
Thanks!
Ginger
First, use Developer Edition instead of Evaluation Edition for non-production scenarios, as it's not timebombed.
when I try to access SSRS from the Object Explorer of SSMS 18.5,
There's not really much use in using SSMS to connect to the Report Server. Just open the Report Manager Portal in your browser.
old DB names & "SSRS" are the only instances I see
Not sure, but SSRS 2017 is not installed as part of a SQL Server instance, and you can't have multiple instances installed on a computer. This change was part of the transition of SSRS be a scaled-down edition of Power BI Report Server.
I'm trying to connect SQL Server Report Builder 3.0 to SQL Server 2008 R2. When I click on connect (on builder 3.0) it returns the above connection error. SQL Server Reporting Services on ie is up and running but every time I click on Report Builder button on SQL Server Reporting Services (in internet explorer), it opens up report builder 1.0 instead of 3.0 .
I tried different changes on my link but none worked. There were posts suggesting adding / to the end of my link, it didn't work either.
I use Web Services URL from Report Services Configuration Manager. I tried many online suggestions, uninstalled, and reinstalled Builder 3.0 compatible with SQL Server 2008 R2. None worked so far. I'm using win 8.1 if that matters.
Any help is appreciated!
In a normal local network environment if your SSRS server was called myServer then you would view the reports with
http://myServer/Reports . This is the web portal (called Report Manager in earlier versions I think)
Report Builder needs to connect to the service url with, using our example this would be
http://myServer/Reportserver
If this does not help, then please show the connection you have tried and also show the connection that works that you use to get to the SSRS Home page (where you see your reports listed).
I installed VS2013, VS2010 Shell (for the BI-Tools) and SQL Server 2012 on Windows 8.1 Pro. I configured the SQL Server and attached the AdventureWork2012 database successfully.
I created datasource > dataview > cube from the db above.
However, I got an error saying
"The project could not be deployed to the 'XX\DBT2' server because of
the following connectivity problems: A connection cannot be made to
redirector. Ensure that 'SQL Browser' service is running. TO verify or
update the name of the target server..."
I've checked the SQL Server and SQL Server Browser and both are running. (checked from SQL Server Configuration Manger)
I also checked the db connection I set up on the VB project. It said Test connection succeeded.
I think I missing some user permission thing but not sure which one is it so here is a little more info about the user right. The user I am using is the account that setup with the windows installation. I also followed some other article online that they said added a few more admin right (user, group) will solve this issue which it didn't for this case.
I also go into the SQL Server Management Studio and check the database permission. And the user right as well but I can't seem to find any problem.
So I've been doing a project at my university with BIDS and a database on their servers. I've managed to back up the database and put it on my local machine.
Problem right now is I've installed SQL Server 2008 + BIDS through SQL Server 2008 Express Edition. Now I've heard it doesn't include SQL Server Analysis Service, meaning I can't deploy the cube.
I've tried deploying the project on my home computer but it gives me the error.
Error 23 The project could not be deployed to the 'my computer
name\SQLEXPRESS' server because of the following connectivity problems :
A connection cannot be made to redirector. Ensure that 'SQL Browser' service
is running. To verify or update the name of the target server, right-click on
the project in Solution Explorer, select Project Properties, click on the
Deployment tab, and then enter the name of the server.
I've checked and SQL browser service is definitely running so I'm not sure what else to try. Is there any way for me to successfully deploy the cube?
I think its authentication issue for your current user connecting to SQLEXPRESS. Try using "Runas /user:[domain]\[user] "Path to BIDS" to run BIDS as privileged user and try windows authentication.
I have installed WSS 3.0 on Windows Server 2008 R2. Over the weekend the system admin installed Double Take to backup the server. During the installation process SQL Server 2008 was installed. Now when I load WSS the page is blank and on the server I get the classic "Internal 500" error. I uninstalled all the 2008 SQL Server items and tried to get the WSS site back up and running. I have verified the database is still located on the server and has my existing data. I have successfully backed this up for safety. I ran the Sharepoint Products and Technologies Configuration Wizard but no luck getting the site back up and running. I looked around the forums and didn't see this exact problem. Help....
Have you checked that the database is still accessible by WSS and that WSS has permissions to read/write to the database.
Also have you checked your event log on the server. This can sometimes give information about errors/issues that WSS is having when trying to access its database and failing.
Hope this helps..