Microsoft KB Archive/916570

= Error message when you try to access Reports in Microsoft Dynamics CRM 3.0: &quot;The underlying connection was closed: Could not establish trust relationship with remote server&quot; =

Article ID: 916570

Article Last Modified on 12/2/2006

-

APPLIES TO


 * Microsoft Dynamics CRM 3.0

-





Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you try to access Reports in Microsoft Dynamics CRM 3.0, you may receive the following error message:

The underlying connection was closed: Could not establish trust relationship with remote server.



CAUSE
This problem occurs because Microsoft CRM uses the certificate that you created for the server after you installed or upgraded the program. Microsoft CRM is installed on this server. By default, the installer program uses the Web address that is specified in this certificate. Microsoft CRM reports do not work if you try to access Reports by using this Web address.



RESOLUTION
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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, remove the Web address from the report configuration files and from the registry. To do this, follow these steps.

Note This procedure uses the default file locations for Microsoft SQL Server 2000. If you are using Microsoft SQL Server 2005, the files may be in different locations.  On the server on which SQL Server Reporting Services (SSRS) is installed, modify the Rswebapplication.config file. To do this, follow these steps.

Note You can verify the installation location of Reporting Services by using Microsoft Internet Information Services (IIS) Manager. The Reports folder and the ReportServer folder are listed under the default Web site.  Open the Rswebapplication.config file. By default, this file is in the following location:

C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\

 In the file, locate the following section:

https://. /ReportServer

Note In this step and in step c,  represents the actual server name, and   represents an actual domain name. In the path that is mentioned in step b, change https://. to https:// . Save and close the file.</li></ol> </li> Modify the Rsreportserver.config file. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Open the Rsreportserver.config file.

Note By default, this file is in the following location:

C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\

</li> In the file, locate the following section:

<UrlRoot>https://. /ReportServer</UrlRoot>

Note In this step and in step c,  represents the actual server name, and   represents an actual domain name.</li> In the path that is mentioned in step b, change https://. to https:// .</li> Save and close the file.</li></ol> </li> Modify the registry for Reporting Services. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type Regedit, and then click OK.</li> In Registry Editor, click the following subkey:

</li> Click Reporting Services.</li> Right-click RSVirtualDir. Then click Modify.</li> Change the value that is in the Value data field from https://. /ReportServer to https:// /ReportServer, and then click OK.

Note In this step,  represents the actual server name, and   represents an actual domain name.</li> Right-click WAVirtualDir. Then click Modify.</li> Change the value that is in the Value data field from https://. /Reports to https:// /Reports, and then click OK.

Note In this step,  represents the actual server name, and   represents an actual domain name.</li> In Registry Editor, click the following subkey:

</li> Click MSCRM.</li> <li>Right-click SQLRSServerURL. Then click Modify.</li> <li>Change the value that is in the Value data field from https://. /ReportServer to https:// /ReportServer, and then click OK.

Note In this step,  represents the actual server name, and   represents an actual domain name.</li> <li>On the File menu, click Exit.</li></ol> </li> <li>Verify that you can access the SSRS Manager by using the following Web address:

https:// /Reports

Notes <ul> <li>In this step,  represents the actual server name.</li> <li>You may receive an error message if you access the SSRS Manager by using the Web address and if you are using Microsoft SQL Server 2005. To resolve this problem, follow the instructions in the following Microsoft Knowledge Base article:

916163 You receive an error message when you access Calendar or Reports in Microsoft CRM

</li></ul> </li> <li>Verify that you can view Microsoft CRM reports.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kbmbsreports kberrmsg kbmbsmigrate kbprb kbtshoot KB916570

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.