Friday, March 9, 2012

Help with problem from editing rsWebApplicationConfig

Our report server was being accessed by machine name, not alias, so I had an alias set up.

I was working to get the subscription emails to use the new alias, instead of machine name. I think I should have edited the rsreportserver.config file, but first I edited the rsWebApplication.config file, and added an URL into <ReportServerURL> tag.

At that point clicking on New Subscriptions stopped working - now I always get an Error page with this message "Object reference not set to an instance of an object". That's only for new subscriptions, not new Data driven subscriptions.

In the error logs, I got this message:

w3wp!library!c!2/5/2007-18:46:46:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information. > System.Exception: The configuration file contains an element that is not valid. The ReportServerUrl element is not a configuration file element.
at Microsoft.ReportingServices.Diagnostics.UIConfiguration.ParseXML(XmlNode node, RSConfiguration configObject)
at Microsoft.ReportingServices.Diagnostics.RSConfiguration.ParseDocument()
at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Load()
End of inner exception stack trace
w3wp!configmanager!c!2/5/2007-18:46:46:: Error occured with a config file change. New config file will not be used. Error: The report server has encountered a configuration error. See the report server log files for more information.

Now, no matter what I do to correct the rsWebApplication.config file, it doesn't seem to fix the problem (ie, I continue to get the above error, when trying to add a new subscription.)

What do I do to fix this?

Thanks in advance for any help!

Kristi

You can specify either the ReportServerVirtualDirectory element or the ReportServerUrl element, but not both. I'm not 100% sure this is yoiur problem, but that's what I'd check first.|||Thanks!

I think you are correct about not having both, and I think that caused my original problem - for awhile, I did have both specified.

However, once I read that information, I blanked out the ReportServerUrl, and now only have the ReportServerVirtualDirectory filled in. (and I tried reversing the two), but nothing seems to take effect now.

I've stopped and restarted both the IIS service and the SSR service, and while that was enough to make the original change to take effect, it does not seem to be resetting it to the original (working) state.

So, it's been a day, and your response prompted me to try the new subscription one more time, and indeed it has now started working again!

Fixed?!?!? The server has over 3000 hours uptime, so it wasn't a power cycle, but something seems to have reset itself, and is allowing new Subscriptions to be entered again.

I don't like when things "fix themselves", but our IT department might very well have changed something without notifying me, so ...

Thanks again for your reply. Kristi

No comments:

Post a Comment