We are doing some analysis for one of our clients who would like to use Siteminder sso with SSRS 2016, we are not finding the ReportManager folder in SQL Reporting service installed location,
Also if there is any way to implement the custom security extension, to authenticate and authorized for reports using site minder sso..
Appreciate any help...
Thanks...
Related
SQL Server/SSRS 2016 Developer, installed on my local laptop, Windows 10 Pro.
My login is an admin to SQL Server, I'm able to do everything. For SSRS, when I try to connect to my web portal url I'm told "You are not allowed to view this folder. Contact your administrator to obtain the necessary permissions." Connecting to the web service url I get this message, "The permissions granted to user are insufficient for performing this operation. (rsAccessDenied)". When I connect to Reporting Services with my login in SSMS it connects but I'm not able to do anything - when I right-click on anything the Properties options are not available.
I have run IE as administrator and added the web portal url to trusted sites. I've run SSMS as administrator and connected to Reporting Services, same problems. I can run Reporting Services Configuration Manager as administrator and have no problems there. It seems like somehow when I setup SSRS my account didn't get added to the list of administrators for Reporting Services.
I did select * from ReportServer.dbo.Users and see these three:
Everyone
NT AUTHORITY\SYSTEM
BUILTIN\Administrators
I have tried Chrome, IE, Edge, all as regular user and administrator.
Any suggestions? Thanks!
I am migrating an application from SSRS-2012 to SSRS-2016. We are having an application to deploy rdl files to the report server. Inside that application we are using Report Server Web Service Endpoints. For SSRS-2012 we used following service url
http://localhost/ReportServer/ReportService2010.asmx
When I am migrating to SSRS-2016, what shall be the Report service endpoint?. I didn't find a specific endpoint for SSRS-2016. I confirmed that the same endpoint(above mentioned url-ReportService2010.asmx) is working with SSRS-2016 also.
Anyone please suggest which endpoint should be used with SSRS-2016.
Thanks in Advance
The endpoint name is the same for SSRS 2012 and SSRS 2016 (ReportService2010).
As described here : https://learn.microsoft.com/en-us/sql/reporting-services/report-server-web-service/methods/report-server-web-service-endpoints
It only can change if you switch to SSRS 2017 and use the REST API (https://learn.microsoft.com/en-us/sql/reporting-services/developer/rest-api)
I have deployed a couple of reports in SSRS2012, the report uses the user's windows token to do some verification. When testing the report in VS I successfully read the windows token but when I deploy to SSRS token is empty.
I did configure all data sources to use windows authentication and to impersonate the user.
any ideas?
Thanks
I'm a little unclear on the specifics here, but I'm thinking the problem is with the authentication method you're using in IIS.
Check out this other question:
Why does Windows/Integrated Authentication in IIS not pass user credentials to SSRS and SQL?
The versions are a bit different (SSRS 2005) but I think the issues here are the same. I won't get into it too much, because the answer in that link explains it better than I could, but essentially, it works from Visual Studio because your Windows Token is the one making all the requests. When you deploy to IIS, however, without explicitly configuring Windows Authentication and Identity Impersonation, the requests are being executed as the App Pool User, not the user using your web app. I hope this helps!
We're having an issue with Dynamics CRM 4.0.
Environment:
Dynamics CRM Enterprise 4.0 Update Rollup 20
Windows 2008 R2, SQL 2008 R2
Platform and Database servers on separate virtual machines
On-Premise deployment
We are using an imported organisation, the web site, outlook connectors and reports are all working without issue.
The issue we're having is that all workflows and system jobs are stuck in the Waiting status. Looking into the organisation database, we see a message like so:
Select Message from AsyncOperationBase where AsyncOperationId = 'SOMETHING';
We see a message that indicates the CrmService returned a 401 Unauthorized.
Using a browser, we can browse to:
http://crmserver/orgname/mscrmservices/2007/CrmService.asmx
and the service is correctly returned, however, when we browse to
http://crmserver/mscrmservices/2007/CrmService.asmx
we receive a 401.2 error.
Additionally, we can access the other services, such as the discovery service, via their normal path (without the org name). It's only the CrmService.asmx that displays the problem.
The CrmAsync and AppPool are all running under Network Service, and this issue is only affecting workflows.
We've tried Unpublishing/Republishing all workflows to no avail. We've run the IFD tool to ensure the server names are correctly set. We have uninstalled/re-installed.
Now we're stuck. Any ideas?
Turns out that the problem was related to hosting WSUS on the same web application as the Dynamics CRM service.
Fixed the problem by reinstalling Dynamics CRM to its own web application.
I'm trying to access the Reporting Services via Web Services in my Visual Studio 2008 Application. How/where can I find my WSDL?
The following example shows the format of the URL to the Reporting Services management WSDL file:
http://server/reportserver/ReportService2005.asmx?wsdl
See http://msdn.microsoft.com/en-us/library/ms169816.aspx
I should point out that although Gulzar has indeed posted the correct answer, it only works if you have your Web Service URL set to the default - if not then it won't work.
Make sure you check which URL is correct - in Reporting Services Configuration Manager go to the Web Service URL section and see what's in the "Report Server Web Service URLs" box.
This may also include the Port number, though if it's Port 80 you can leave this out.
Also, for some reason even though this is Sql Server 2008 & Reporting Services 2008, the asmx is still ReportService2005.asmx. For some reason this hasn't been updated.
So the URL should be:
http://MyReportServer:PortNumber/WhateverUrlTheWebServiceIsSetAs/ReportService2005.asmx?wsdl
Hope this helps!