Monday, March 19, 2012

Installation to Sharepoint server

Hi,
We have a question regarding the installation of RS to a WSS server. We have
used STSADM to exlcude the site, checked the web configs for session state
info present, placed the Report server web site in a separate application
pool from WSS, applied Hotfix 859, and attempted manually activate using
rsactivate.
RS fails to activate and the sites cannot be browsed.
What can we check beyond this?
Thanks
SethWe have had similar difficulties - RS seems to compete with SharePoint
in the default web site. In our situation running an IISRESET had the
effect that whichever application was accessed first (either Report
Manager or SharePoints default web site application) would work, and
the other would throw an error.
In our case, RS had been installed first, so activation was not a
problem. Interestingly, even when Report Manager was 'broken', the
underlying Reporting Services continued to work for reports that had
already been deployed.
Researching provided some updated configuration files from the MSDN web
site (sorry I don't have the link) which got Report Manager to work
(after extracting and reapplying the symmetric key), but left the
sharepoint default web site down.
Luckily we didn't need it at that point, so we never drove to a
resolution. (so I will be tracking this thread!).
I would recommend uninstalling RS, finding the new config files I
mentioned, and starting again.
A copy of 'Hitchhiker's Guide to SQL Server Reporting Services' may be
a good investment - (www.bookpool.com has good pricing, service, and
delivery) I am just starting to work through the book, and feel I got
my money's worth at about page 2...
Putting the two RS applications in the same pool is good - you should
also confirm they are both configured to work with .NET Framework 1.1.
If you have Framework 2.0 on the box, they may have been configured to
work with it instead (and they won't - they also won't work if they are
in an application pool with anything using 2.0 - the other thing will
also break...).
If you can install RS to a place other than the default web site, that
might help (though we have never gone down that road).
Also, if you can get a more recent hotfix, you will overcome some
problems that 859 introduces in the Enterprise Manager (some DDL-type
changes won't work through the GUI, although the equivalent commands
will run in Query Analyzer.)|||Seth,
Did you ever get an answer for this?
Alan
"Seth" <Seth@.discussions.microsoft.com> wrote in message
news:41B01080-6179-4BBE-A343-11F3013836ED@.microsoft.com...
> Hi,
> We have a question regarding the installation of RS to a WSS server. We
> have
> used STSADM to exlcude the site, checked the web configs for session state
> info present, placed the Report server web site in a separate application
> pool from WSS, applied Hotfix 859, and attempted manually activate using
> rsactivate.
> RS fails to activate and the sites cannot be browsed.
> What can we check beyond this?
> Thanks
> Seth

No comments:

Post a Comment