I had to downgrade to SSRS 2016. When opening the web url I can only see the data folders in text and not getting the normal SSRS screen.enter image description here
Tried to look in the config file but could not see anything out of order
That looks like report server address, not the web portal address.
If you URL looks like this
http://myservername/reportserver
Then you should be using this
http://myservername/reports
This is the default address of the web portal. If this does not work Open Reporting Services Configuration Manager and look at the Web Portal URL
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...
I am accessing SSRS reports (SQL Server 2016) through URL to embed them in my application in an iFrame. When I access SSRS reports remotely, i.e from different computer I can authenticate and display the reports.
In my iFrame source I put:
http://example.com:4000/path_to_ReportServer/report_name
And that works fine when I deploy my app to stage server. All the SSRS reports load with no problem at all.
However I develop on the same PC as my SSRS report server resides, and when I am on it I have to change all the links in iFrames to:
http://computername:4000/path_to_ReportServer/report_name
edit: originally I wrote here that I use localhost, but actual I meant computer name.
If I try to run my app from VS on my dev machine and I do not change the domain to computer name I wont be able to authenticate at all. It just keeps asking me for the same credentials over and over again.
I've checked the ReportServerService log, and I see this as a last line when I try to log in:
library!DefaultDomain!3bd0!11/21/2016-12:52:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Invalid PBI Configuration, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
I looked for this problem extensively, and I only find MS configuration tutorial but no one having similar issue to mine.
I have checked the usual culprits like firewall or port conflicts (but if I had any of those I would not be able to access the SSRS from any other PC, yet I can and the link doesn't work only on local machine.)
I am very new to SSRS in general so please kindly be patient with me. Thanks!
A few things you can try:
In SSRS Configuration and ensure that the Report Service and Report Management endpoints are valid (Copy the url in the hyperlink and make sure it opens on your local host.)
In SSRS Configuration and ensure that the Report Service Database has been properly deployed.
Remove any custom modules/assemblies you have applied to the default behavior from the ssrs web config (Custom Security).
I think you have applied changes to ssrs's web config in order to have it load assemblies for your custom security, custom datasourse/dataset, custom render format and fat fingered the config somehow.
You're probably running into a same-origin-policy error, which wikipedia states as under the policy, a web browser permits scripts contained in a first web page to access data in a second web page, but only if both web pages have the same origin.
The fix is to implement the X-Frame-Options metatag, like so:
X-Frame-Options: ALLOW-FROM https://example.com/
I am building custom reports in Microsoft CRM and am using the CRM_URL parameter to created drill downs.
However, the URL coming in is ***http://**myserver.com/org/CRMReports...* but it should be **https://**myserver.com/org/CRMReports...
My understanding is that this value is dynamically passed in by MS CRM. How/where can I update this URL to use https?
you need to use the SRSS config tool. =>
Configuring a Report Server for Secure Sockets Layer (SSL) Connections (2005)
Configuring a Report Server for Secure Sockets Layer (SSL) Connections (2008)
"Edit UrlRoot in the RSReportServer.config File
If you are using the report server e-mail delivery extension, you can create subscriptions that included a report URL in the e-mail message. To construct the report URL, the report server uses the UrlRoot configuration setting in the RSReportServer.config file. If the report runs on a report server that is accessed through an SSL connection, you must manually edit the UrlRoot to use the https:// prefix.
If you are using a server certificate, the format of the URL is as follows:
<UrlRoot>https://certificatename/reportservervirtualdirectoryname</UrlRoot>
The answer to my issue was #4 & #5 from this link:
http://rc.crm.dynamics.com/rc/regcont/en_us/op/articles/secure_comm.aspx#ID0EFD
For deployments that will not be used
by external clients, which connect
over the Internet, follow these steps:
Obtain a certificate from a CA. To use certificates you will have set
up a public key infrastructure (PKI),
which consists of one or more CAs that
are linked in a hierarchy. These CAs
and the PKI are required to manage
certificate issuance, validation,
renewal, and revocation in one or more
organizations. You can use a
third-party PKI with Microsoft Windows
Server 2003, or you can establish your
own PKI, based on Windows Server 2003
Certificate Services.
Make sure that there are no users accessing Internet Information
Services (IIS) where the Microsoft
Dynamics CRM Web application is
installed. To do this, stop the
Microsoft Dynamics CRM Web site:
right-click the Web site, and then
click Stop.
Configure the Microsoft Dynamics CRM Web site to use SSL. To do this,
perform the following steps on the
server running IIS where the Microsoft
Dynamics CRM Web application is
installed:
1. Start Internet Information Services (IIS) Manager
2. Right-click the Microsoft Dynamics CRM Web site, and then click
Properties.
3. Click the Directory Security tab, click Server
Certificate, and then follow the
instructions in the Web Server
Certificate Wizard.
4. If you want clients to only use SSL when they connect to the
Microsoft Dynamics CRM application, on
the Directory Security tab in the
Secure communications area, click
Edit.
5. On the Secure Communications dialog box, click the
Require secure channel (SSL) check
box.
6. Close Internet Information Services (IIS) Manager.
Important: You can apply only a single certificate to the Microsoft
Dynamics CRM Web site. Therefore, you
if you have configured Microsoft
Dynamics CRM Server for both internal
and Internet-facing (external) access,
you cannot configure SSL for both
internal and external connections to
the Microsoft Dynamics CRM Web site.
You must manually modify the following values in the configuration
database.
Warning: Incorrectly modifying the configuration database
(MSCRM_CONFIG) can cause unexpected
behavior in the Microsoft Dynamics CRM
system or cause the system to stop
working. We recommend that you back up
the Microsoft Dynamics CRM system
before you complete these steps. For
information about how to back up the
Microsoft Dynamics CRM system, see the
Operating and Maintaining Guide that
is part of the Microsoft Dynamics CRM
4.0 Implementation Guide document set.
1. On the computer running Microsoft SQL Server, start SQL Server
Management Studio.
2. Expand Databases, expand MSCRM_CONFIG, expand Tables,
right-click dbo.DeploymentProperties,
and then click Open Table.
3. In the dbo.DeploymentProperties table under
the ColumnName column, in the
ADRootDomainScheme row, change the
NVarCharColumn column value from http
to https. Note that this value must be
in lower-case letters.
4. In the dbo.DeploymentProperties table, under
the ColumnName column, in the
ADSdkRootDomain row, change the
NVarCharColumn column value by using
the name of the certificate configured
for the Microsoft Dynamics CRM Web
site. The name of the certificate can
be found, in Internet Information
Services (IIS) Manager, on the
Directory Security tab of the
Microsoft Dynamics CRM Web site
properties page.
5. Click View Certificate.
6. On the Certificate dialog box, click Details.
7. Click the Friendly Name field to locate the certificate name.
If the certificate name is the same as
the computer name, you can use the
format ServerName:SSLPortNumber. By
default, the TCP port for SSL
connections is 443.
8. In the dbo.DeploymentProperties table, under
the ColumnName column, in the
ADWebApplicationRootDomain row, change
the NVarCharColumn column value by
using the name of the certificate
configured for the Microsoft Dynamics
CRM Web site. If the certificate name
is the same as the computer name, you
can use the format
ServerName:SSLPortNumber. By default,
the TCP port for SSL connections is
443.
9. Make sure your modifications are saved and then close
SQL Server Management Studio.
Modify the LocalSDKPort Windows registry subkey value. To do this,
complete the following steps.
Warning: Serious problems might occur if you modify the registry
incorrectly by using Registry Editor
or by using another method. These
problems might require that you
reinstall the operating system and
Microsoft Dynamics CRM. We cannot
guarantee that these problems can be
solved. Modify the registry at your
own risk.
1. Start Registry Editor, and locate the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
subkey.
2. Right-click LocalSdkPort, click Modify, and then click OK.
3. In the Base area, click Decimal, and then type the TCP port.
4. Click OK.
5. Close Registry Editor.
Restart IIS. To do this, at the command line, run the iisreset
command.
Start the Microsoft Dynamics CRM Web site. To do this, right-click the
Microsoft Dynamics CRM Web site, and
then click Start.
Restart the Microsoft Dynamics CRM Asynchronous Processing Service.
To do this, click Start, point to
Administrative Tools, and then click
Services. In the list of services,
right-click Microsoft Dynamics CRM
Asynchronous Processing Service, and
then click Restart.
Verify that you can successfully connect to the Microsoft Dynamics CRM
Web site. To do this, you must use a
URL that begins with https. For
example, in Internet Explorer the URL
will appear similar to the following
address:
https://ServerName/OrganizationName/loader.aspx
If the Microsoft Dynamics CRM Web site is not configured to require
SSL connections, verify that you can
successfully connect to the site by
using an http connection, for example,
http://ServerName/OrganizationName/loader.aspx.
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!