> Hi,
>
> A bit of background.
>
> We have a deployment of CRM 3.0 installed and working fine on our
> Windows 2003 CRM server in a Windows 2003 AD. Still having problems
> with clients on Outlook (PC's are not a member of a domain), but
> playing with the web-based interface for now.
>
> Got a problem with the Reports part of CRM - this is based on the
> standard Reporting Services for SQL Server 2000 (SP4) - hence I've sent
> to public.sqlserver groups also.
>
> Clicking on Reports in CRM web takes you to the list of available
> reports fine, but when you try to 'Run report', it returns a 401.
>
> I know why this is happening, and a basic workaround proves it, but am
> looking for a decent server-side resolution.
>
> We have an AD (e.g. domain.com), with CRM/SQL installed on a box within
> a child domain (comp.domain.com). However, our web caching, proxy, DNS
> for the root of the our domain (domain.com) is not handled by the AD,
> its handled by our Unix/Sun guys.
>
> If we connect to the CRM reports via the web on an AD member PC, 'Run
> report' works fine for each report because it knows that our CRM/SQL
> Reporting server (sake of example called crm1), is in the domain, and
> that its Windows hosts name is http://crm1 ( =
> http://crm1.comp.domain.com). The problem is calling the reports from a
> non domain member fails with a 401 because it tries to call http://crm1
> (i.e. no FQDN), and thus goes to our Unix-based domain/DNS and tries to
> resolve to http://crm1.domain.com, not crm1.comp.domain.com. Hence it
> fails.
>
> I've proved that if I bung a hosts entry in
> C:\Windows\System32\Drivers\etc\hosts to resolve crm1 to the IP, it
> corrects the problem, but we don't want to have to maintain host files
> in our total IP-based network, and our CRM deployment might eventually
> have >1000 clients - some on domain, others not, some on trusted
> domains, some remote users.
>
> I might be able to get our Unix/Sun bods to some fiddle redirect their
> end, but would prefer to keep everything within our Windows set-up.
>
> Having looked at one of the reports in C:\Program Files\Microsoft
> CRM\Reports\MSCRM on our CRM/SQL server, e.g. "User Summary.rdl", we
> can see that the code for this report is calling the following
> variable:
>
> Parameters!CRM_serverURL.value
>
> Which is presumably pulling this from somewhere (SQL database? a config
> file in CRM? IIS?) and thats whats resolving it to http://crm1.
>
> The question is, does anyone know where this parameter is pulling its
> data from, because if so, can I change it to reflect
> http://crm1.comp.domain.com and thus ensure that the Reports section
> always uses the FQDN to work?
>
> Thanks in advance,
> Steve
>