locked
CRM 3.0 reports does not work with external address. RRS feed

  • Question

  •  

    Hi,

     

    I did a search but did not find any similar issues.

     

    We have a CRM 3.0 system where the SQL 2005 database used to be on the same machine but this was moved and are now on separate machines.  This was moved by restoring the original DB.

     

    Using the internal name, ie. http://server1int/loader.aspx we are able to use both CRM and also gain access to the Reports (having configured this to point to http://server2db/reportserver

     

    Now we have configured an external public name i.e. crm.domain.com which works well, but does not allow the reports to be seen.  We get a "Error has occurred" message with contact Administrator but no futher information.  We realised later this applies to IP address internal/external as well, so I assume we have a setting somewhere where we need to configure it to accept all forms of the server name?  In IIS it's set to all assigned.

     

    Thanks,

    Phu

    Tuesday, January 15, 2008 2:24 PM

Answers

  • The problem is that when you are outside of your network and accessing your CRM system via the internet using the http://crm.domain.com address, when you try to access reports, CRM is still pointing to an internal address (http://server2db/reportserver) that your browser has no way of resolving. Thus you get the error. Since CRM 3.0 only allows one address to be set in Deployment Manager for the SQL Report Server, your only alternative is to make your SQL Report Server accessible to the internet and use that full, externally resolvable, address in the Deployment Manager setting. For example, if you publish your SQL RS server to https://sqlrs.domain.com/reportserver, and this address works externally, then you can set this in Deployment Manager as the address of your SQL RS server for CRM. The drawback is that you will need to authenticate twice when opening CRM externally (you can work around this internally by adding the sqlrs.domain.com to your Trusted Sites, and set IE to automatically logon for you).

    Hope this helps,

    Matt Wittemann

    CRM MVP

    http://icu-mscrm.blogspot.com

     

    Wednesday, January 16, 2008 3:18 AM
    Moderator

All replies

  • The problem is that when you are outside of your network and accessing your CRM system via the internet using the http://crm.domain.com address, when you try to access reports, CRM is still pointing to an internal address (http://server2db/reportserver) that your browser has no way of resolving. Thus you get the error. Since CRM 3.0 only allows one address to be set in Deployment Manager for the SQL Report Server, your only alternative is to make your SQL Report Server accessible to the internet and use that full, externally resolvable, address in the Deployment Manager setting. For example, if you publish your SQL RS server to https://sqlrs.domain.com/reportserver, and this address works externally, then you can set this in Deployment Manager as the address of your SQL RS server for CRM. The drawback is that you will need to authenticate twice when opening CRM externally (you can work around this internally by adding the sqlrs.domain.com to your Trusted Sites, and set IE to automatically logon for you).

    Hope this helps,

    Matt Wittemann

    CRM MVP

    http://icu-mscrm.blogspot.com

     

    Wednesday, January 16, 2008 3:18 AM
    Moderator
  • Dear, can you check it plz

     

    First check your IE for windows authentication..

    installed CRM 3.0 rollup #2 

    connect to the http://servername/reportserver

    Try to re-config  the report services(Reporting Services Configuration).

    You can check following as well..

     

    1. Can you open your reports server? http://servername/reports
    2. create a new application pool and set the following virtual directories to run on that pool
    /Reports/
    /ReportServer/
    3. Then change /Reports/ and /ReportServer/ to run on .net 2.0
    Do this by going to IIS and expanding your CRM web site. You will have the reports virtual directories listed there and on their properties menu there will be a .net tab where you can choose what version to run.
    4. verify you can now access your reports server.

     

    Regards,

    Imran

     

    http://microsoftcrm3.blogspot.com

     

    Tuesday, January 22, 2008 7:19 AM
    Moderator