How to resolve processing and db connection errors with SQL ReportServer

Hello All,
I'm extremely new to SQL Server,  so please bear with me if this questions has an obvious answer. I've been thrown into a problem just today when the our ASP.NET web application went down citing db connection problems and we saw the message below in the event viewer:

Microsoft.Reporting.WinForms.ReportServerException: An error has occurred during report processing. (rsProcessingAborted) ---> Microsoft.Reporting.WinForms.ReportServerException: Cannot create a connection to data source 'MyDb'. (rsErrorOpeningConnection) ---> Microsoft.Reporting.WinForms.ReportServerException: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   at MyRepScheduler.Service1.ForAnalysis(DataRow row)
   at MyRepScheduler.Service1.objTimer_Elapsed(Object sender, ElapsedEventArgs e)An error has occurred during report processing. (rsProcessingAborted)MyRepSchedulerSystem.Collections.ListDictionaryInternal

All reports were working fine intiially and then late last nite someone ran about 25 in a row, and then we lost our db connection through the Web application. Is there a simple way to reset the SQL connection to the web application. Maybe by restarting one of the Windows services or SQL Server itself? I'll be happy to provide any other informationor log files if requested.


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

OS_IIIAuthor Commented:
We've fixed the problem, although i'm not sure if our fix would be considered the "right" fix! Everything works now though so that's the point for most around here...!

While looking for more error messages, on the website itself we saw the message below:
"An Error has occured during reports processing. Cannot create a connection to Data Source "MyDb". For more information about this error, navigate to the report server on the local server machine, or enable remote errors."

 Taking this hint along with the event viewer's error message in my first post, we went to the URL for the Report server and examined the User ID, pwd and the IP itself from the data source's connection string. We tested the first two for db connectivity with a .udl file, and then found that the IP used for the data source was an external one.  Since we have our app and db on two different servers that are both behind the firewall, we changed the external IP to an internal one in the Report Server's connection string and voila, the connection was restored. As a newbie, i'm chalking this up to just a  whole lot of inexperience with the Report Server setup, but if there are no other words of advice, i'll consider this problem solved. Thanks for all who even looked!
 - os3

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.