Question Status

Verified
Dieter Tontsch asked a question on 18 Jul 2013 6:28 AM

on sql reporting services with error "a server certificate could not be validated for url http://server/reportserver". I have no idea how to continue from here. I have little IIS+MSSQL knowledge and almost no CRM knowledge. I have added a SSL (https) binding to the default ISS web site incl. a self-signed certificate. Have also double-checked if SQL Server Reporting Services  is running.

SQL 2008 R2 is installed on the same server (w2k8 R2) where I intend to install CRM 2011 for testing and evaluation purpose.

I don't know if this is a hint, but http://servername/reportserver can not be browsed, is it supposed to be available? When I try to browse this url i first get a certificate warning and then a http:404.

Any ideas what the rason might be?

kind regards,

Dieter

Reply
Michael Dodd responded on 18 Jul 2013 6:45 AM

I would remove the SSL bindings in IIS. If you want to have CRM use SSL, you should do so after the install using the Internet Facing Deployment white paper as your guide. just a heads up, you will need to use ADFS to do so, which, if you're planning to install on the same machine, will need to use the default port 80, so make sure you install CRM and SSRS on different ports (like 8080 or 5555).

Reply
Dieter Tontsch responded on 18 Jul 2013 6:50 AM

I got the error before any ssl binding was set up in IIS. During the install process I have choosen CRM to run on 5555. I have no idea on what port SSRS is running.

I forogt to mention that on the same machine there is an old but yet stopped sharepoint 2010 installation also.

Reply
Mohammad Atif responded on 18 Jul 2013 1:03 PM

I believe this is due to the issue with the report server URL which can not be browsed. Can you please open report server configuration manager and click on the hyper link there to brose Report server URL and see if you can or not. Also, please make sure that reporting services configured properly in Reporting services configuration Manager

Thanks,

Mohammad

Reply
Verified Answer
Dieter Tontsch responded on 24 Jul 2013 5:29 AM

Mohammed was right in a way. Actually I had a lot of missconfigurations with the report server:

1. At the time SQL (incl. Reporting Services) was installed the machine had a different name. Therefor the SQL instance had a different name than the actual computer name. I had to fix this with:

sp_dropserver @@SERVERNAME

GO

sp_addserver 'newServerName', local

GO

2. on the same there was already installed a ISS which was listeing on port 80 and 443 already. So I had to change the URL for the Reportserver from 80 and 443 to something else in Reporting Service Configuration Manager (8080 + 8443)

3. last but not least also the fact that credentials vor Report Server did not macht anymore after the computer was renamed. I had also to re-set the login credentials for Reporting Servers

Reply
Verified Answer
Dieter Tontsch responded on 24 Jul 2013 5:29 AM

Mohammed was right in a way. Actually I had a lot of missconfigurations with the report server:

1. At the time SQL (incl. Reporting Services) was installed the machine had a different name. Therefor the SQL instance had a different name than the actual computer name. I had to fix this with:

sp_dropserver @@SERVERNAME

GO

sp_addserver 'newServerName', local

GO

2. on the same there was already installed a ISS which was listeing on port 80 and 443 already. So I had to change the URL for the Reportserver from 80 and 443 to something else in Reporting Service Configuration Manager (8080 + 8443)

3. last but not least also the fact that credentials vor Report Server did not macht anymore after the computer was renamed. I had also to re-set the login credentials for Reporting Servers

Reply