Thursday, July 31, 2008

Reporting Services 2008 Configuration Mistake

To start working with the management side of SQL Server Reporting Services 2008, I decided to set up a report server and report manager. Unfortunately, I made a mistake while setting up my configuration that left me a little perplexed. Here are the steps I took to cause, track down, and solve the issue.

I began by opening the Reporting Services Configuration Manager from the Start Menu. I clicked through each of the menu options and accepted the defaults for any question with a warning symbol, since warning symbol typically designate an action item. After two minutes, all of the warning symbols had disappeared, and I was ready to begin managing my report server. Unfortunately, opening up a browser and trying to open up the report manager resulted in the dreaded "The report server has encountered a configuration error. (rsServerConfigurationError)" message.

Sherlock-ing it:
I put on my sleuthing hat and went to the log file directory: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles. Under the latest ReportServerService*.log, there was the following error: "Message: No DSN present in configuration file". Looking at the file: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config proved the error message true, as right at the top of my log file was the empty Dsn tag.

Looking in Books Online under the RSReportServer Configuration article, I discovered that the Dsn property contains a connection to the report server database. That's odd, I don't remember creating that connection...

I returned to the scene of the crime, the Configuration Manager. Sure enough, the third warning-less menu option allows you to set up the connection to either an existing report server database or create a new one for this instance. I filled in the appropriate information, and took a look back at the configuration file. This time, the Dsn tag contains a beautifully encrypted blob of information. The report manager works, and I am ready to manage my reports! The moral of this story is to read the directions before clicking through configuration managers, don't trust warning icons or lack thereof, and don't forget that Reporting Services needs to know what database to use. :)

Version: SQL Server 2008 RC0


Michael said...

Thanks saved me a lot of hassle :)

Kaisa said...

Thanks a lot! I noticed that the Database section looked rather empty in my RS Config Manager, but didn't investigate too much. Thank you for Sherlock'ing it! (Brilliant phrase!)

Jerry said...

Thanks so much for posting this. After working almost all day on this I found your post after I did some sleuthing on my own. My thing is it should either do a default installation to the SS you just installed or require you to do create a DB before proceeding. This was not a problem in SS 2005.

Thanks again.

mahnaz said...

Haha, that is the EXACT issue I came across. Thanks for the post!

Dorfy said...

I am having the same problem. However, I don't see the 3rd screen you referenced on the Configuration Manager. How do you launch this screen.

I went to the SQL Server Configuration Manager on the Server and found the Reporting Services and on the 'Log On' tab the accounts has a grayed out button stating 'Not Installed'. I stopped the services for Reporting Services in hopes this would un-gray the button, but no luck. Help! :)

chuck said...

this fixed me up too. Thanks and see you @ devlink.

Jessica M. Moss said...

Hi Dorfy,

I think we may be talking about different programs, as the configuration manager doesn't have a Log On tab. You can find the Configuration Manager by going to your Start Menu > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager.

Hope that helps,

Dorfy said...

It seems we were launching the same program. I was not using Reporting Services, (it was not installed), but the 'SQL Reporting Services' was running. I ended up stopping the service and changing it to Manual. I don't get the error any more.

Chetnav said...

Thank you sooo much...what a relief to find a solution!!! phew:)

Tejas Shah said...


This is really helpful. I found it at last on this blog.


Tejas Shah

Anonymous said...


I am working on sqlserver reporting services 2008. I m getting a reporting services Login screen Problem when i m deploying a report. and after inserting username and password then it appear again and again.
if anyone know the solution please reply

Thanks a lot

Dale said...


I just did an reinstall of SQL Server Reporting Services 2008 and am getting the same error as Anon above when trying to hit the report server page from the report server "The report server has encountered a configuration error. (rsServerConfigurationError)"

Trying to hit this page from any other server repeatedly prompts me for a username and password.

Looking in the ReportServer Logfile though I see the following error:

runningjobs!ReportServer_0-5!1984!11/19/2009-08:41:09:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
runningjobs!ReportServer_0-5!1984!11/19/2009-08:41:09:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
library!ReportServer_0-5!1984!11/19/2009-08:41:10:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. , SharePoint content service is null. Report Server may not have joined the SharePoint farm, or Report Server service account may not have been granted access to farm.;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
library!ReportServer_0-5!4b4!11/19/2009-08:41:10:: Unhandled exception was caught: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeClientDisconnectionException: A client has disconnected from the Report Server Web service application domain ReportServer_MSSQLSERVER_0-5-129031152285275000. No corrective action is required. An error code has been submitted to ASP.NET to release the connection. The error code is 800708CA. ---> System.Runtime.InteropServices.COMException (0x800708CA): This network connection does not exist. (Exception from HRESULT: 0x800708CA)
at Microsoft.ReportingServices.HostingInterfaces.IRsHttpPipeline.GetAuthType()
at ReportingServicesHttpRuntime.RsWorkerRequest.GetUserToken()
--- End of inner exception stack trace ---
at ReportingServicesHttpRuntime.BaseWorkerRequest.FilterAndThrowException(Exception e, String message)
at ReportingServicesHttpRuntime.RsWorkerRequest.GetUserToken()
at System.Web.HttpContext.get_ClientIdentityToken()
at System.Web.HttpContext.get_ImpersonationToken()
at System.Web.ClientImpersonationContext.Start(HttpContext context, Boolean throwOnError)
at System.Web.HttpApplication.ThreadContext.SetImpersonationContext()
at System.Web.HttpApplication.ThreadContext.Enter(Boolean setImpersonationContext)
at System.Web.HttpApplication.OnThreadEnterPrivate(Boolean setImpersonationContext)
at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)
Currently there are no Application event logs popping up.

This server used to be part of a farm. It was originally working until I started playing with uninstalling/reinstalling some msp files to fix another problem. Since then I've uninstalled reporting services and MOSS, and done the reinstall according to this page:

I'm currently stumped at step 3.6 - Step 6: Installation of SQL Server Reporting Services 2008 Add in.

I installed the Add-in to see if that would make a diff but no go.

Currently I am running WSS and MOSS SP2 and Reporting Services 10.0.2734.0 Enterprise. (According to the Reporting Services Configuration Mgr Startup screen)

I think I'm looking for ideas on how else to diagnose this problem or if I'm lucky a solution. I've been banging my head against this for a couple days now. Any help is appreciated.


Dale said...

Funny - after posting this I found the solution here:

On the computer that hosts the report server, continue to run the Report Server service as NetworkService and add the built-in account, such as NT_AUTHORITY\NetworkService to the WSS_WPG Windows group.

Once we added the NT_AUTHORITY\NetworkService account to wss_wpg, the report website started working on the report server. There are still some other things we need to cleanup but at least we're on the right path.

Caroline said...

I just stumbled across your blog and this post solved my issue immediately.

I linked to it from my small blog where a coworker and I post issues we've run into. I hope that's okay, if not, please let me know.

My Link to your post

Jessica M. Moss said...


I'm so glad I could help, and linking to the post is perfectly fine by me!


Anonymous said...

Saved me a lot of work. Thanks.


Anonymous said...

Thank you for this information! We have been attempting to install Microsoft CRM server and were stuck at reporting services not validating for days!

Andrew said...

Thank you so much! I had been trying to figure this out for hours.

Anonymous said...

Great post, very useful ! Thanks a lot for sharing this !

Dave G said...

What a great tip! Thanks for posting it. That saved me a TON of time.

Anonymous said...

Apparently I must be missing something cause I can't figure this out. Currently I can not start reporting services because of the DSN error. If I go into Reporting Services Configuration Manager only the first 2 options are available; localhost\MSSQLSERVER and Service Account. I have the service account set to built-in Network Service. But since the service wont' start I can't access any of the other configs.

If I go under SQL Server Configuration Manager I just get a list of the services and protocols etc. Not sure where this 3rd screen is you speak of.

Any help would be appreciated. Thanks!

Jessica M. Moss said...

Hi Anonymous,

Be sure that you have full admin access when running the Reporting Services Configuration Manager. I've seen odd behavior when you only have read access.


Anonymous said...

Thanks for this - It was a great help! I made sure I was logged on as the administrator of the server too (SharePoint) so I'm half way tehre.

Rajesh Krishnan said...

thanks, keep going

Anonymous said...

Thanks! Saved me a lot of time and effort!!!

Anonymous said...

Thanks a lot! Love it!!!

Zed Power said...

Creating the Reporting Services database worked for me

Richard said...

Thank you, thank you.

Richard said...

Thank you, thank you!

Thomas Palakan said...

Had the same error..Had tocreate a new database for report server from the confihuration manager and then updated the datasource for the application. Started working subscription in 2008 server.

KarthikShanth said...

Thanks Jessy. Good one. Saved my time.


Ray said...

Had the same error and just found your blog entry. Apparently I skipped right over the create database part in the configuration manager. Thank you.

Anonymous said...

Great find, you saved my time.

Anonymous said...


Save me lots time, You are Sherlock re-incarnate.

I cant beleive this is the only article of its kind. I struggled to find any other. Also that M$ failed to point out this seemingly obvious place to look too.


Anonymous said...

I am new to all this. Can someone please tell me what you needs to be typed in the DSN section as this article just states what is in Books online. I am not sure what that is. Please I need some help here

Dinesh Dattatray Vishe said...

There is no showing content tag.Unable to make new folder.

Thanh said...


Anonymous said...

I'm at the point where I'm attempting to Change Database and use an existing SQL Database, however the manager just sits there and hangs whenever it tries to connect. I have to force close it to continue. Do you know what may be causing this? Could me using the Express edition of SQL Server be an issue?

Anonymous said...

Just as everyone else has stated, this led me right to it. Thank you for sharing your experience online!


Koms said...

Thanks a lot!..helped me to find the cause of error.

Anonymous said...

Thanks a bunch. Ran into the issue in the process of installing a development instance of Microsoft Dynamics CRM 2013. The reporting piece being a side-requirement I did not have the depth to configure it correctly the first time. Thanks again !

Anonymous said...

Thanks for the fix, helped me immediately!

Anonymous said...

Seven years and counting and this post is still helpful. Thanks!