MS Dynamics CRM 4.0 Setup check fails - ReportServer issues

Hi,

My initial thoughts would be that your reporting server is configured to use SSL, but that an SSL certificate is either not installed or not correctly installed. If you are not exposing the reporting server externally then you do not need the SSL encryption. You can de-activate this setting by running the  Reporti Server Configuration wizard and under the Report Server Virtual Directory option deselecting the Require Secure Socket Layer tick box and then clicking apply.

i think port is in use on which reporting server is installed.
if you are using remote desktop and vnc close it first and then try again.

Cheers
Arpit

Thanks for the ideas,

Report Server is set to not use SSL and the port should not ne in use.

The problems occurs during the CRM 4.0 setup prequisite check routine. Setup tries to contact https://MyServerame and can't validate certificate. Error messages at this point:

- A server certificate could not be validated for URL: https://MYSERVER.

-Setup failed to validate specified Reporting Services Report Server http://MYSERVER/ReportServer. Error: The underlying connection was closed: The connection was closed unexpectedly.

I uninstalled SQL Server deployment, re-isntalled it succesfully. From IIS manager I can find the reporting server web page.

Any ideas to look for?

Heya,

If the report server is not set to use SSL then why are the URL references in your post https instead of just plain http ?

There is definately something somewhere, that is refering to SSL, either the URL you are typing in for the report server during the CRM setup process or the IIS settings on the base website / virtual directory for Reporting Services are set to Require SSL/

Thanks for the help,

I made some changes and yes, it seems to be an issue with ASP.net. I'm running 64bit Windows Server 2003 and Exchange 2007 is requesting 64but ASP.net. Could this be causing this behaviour? Here's the error message I'm now getting from the IIS Default Web Site Report Server:

----------------------------------
Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'ReportingServicesWebServer' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Source Error:

Line 27:       <assemblies>
Line 28:         <clear />
Line 29:         <add assembly="ReportingServicesWebServer" />
Line 30:       </assemblies>
Line 31:     </compilation>
 
Source File: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\web.config    Line: 29

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

Ah, Yes that could very well be the problem.

Have you looked at the following article ? (Installing 32-bit ReportServer on 64-bit)
http://msdn2.microsoft.com/en-us/library/ms143293.aspx

Yes,

I have looked on that article. I fllowed the article before installing SQL Server 2005, and all went ok. The problem is, that after the change from 64 to 32 bit ASP.net, all IIS web pages halted to show up.

In 32 bit mode there's no web pages to display, and in the 64 bit mode I get the error message when accessing Report Server. Everything else is working nice and smooth with 64 bit (OWA etc.)

Seems quite complicated issue...

bmosoftware,

I moved both virtual directories to their own Application Pool and ensured that the .Net framework is set to 2.0 on each one of them. I still get the same error message on the browser.

Could there be something in the 64bit environment, .Net is now running in 64bit mode (32bit mode didn't help either)?