I have seen a few messages about difficulties with SRS 2005 + CRM 3.0
Due to some problems we encountered here, I had to re-install CRM on our
server. It had existing CRM Database, IIS configuration corrupted and
reporting services component removed from SQL 2005.
Since the reporting services had been playing up (IIS issue?) and there were
no custom reports in our system, I also dettached and moved the reportserv
and reportservertmp databases from our system.
Eventually re-installed by this process.
1. removed and re-added Applications server role from server (w2K3)
2. Added Reporting services back to SQL 2005
3. Used "Reporting Services Configuration" tool to configure SRS with defaults
4. At this point attempted install of CRM threw error at IIS config
verification because CRM and SRS expect two different versions of .Net
framework but are using same pool.
5. Used SRS config tool again to create new app pool (called it ReportAppPool)
6. Now CRM install failed at SRS config verification. Hitting the details
button provided the raw html describing the problem. The SQL service account
that I had configured did not have write access to:
"C:\Windows\Microsoft.net\framework\2.0.50727\Temporary ASP.NET Files"
7. Added and ACL to this directory that matched the entry for ASP.NET
machine account
8. Install succeeded (use existing databases)
Note: solutions determined by examining contents of evnet log on CRM server,
response to browsing to report server default web page and the output from
the "details" button when CRM config checks failed.
If you follow this sequence, please note whether it works or not with a
reply. It may not be a generic solution and others will want to know.
...Greg
|