OS_III
asked on
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.WinFor ms.ReportS erverExcep tion: An error has occurred during report processing. (rsProcessingAborted) ---> Microsoft.Reporting.WinFor ms.ReportS erverExcep tion: Cannot create a connection to data source 'MyDb'. (rsErrorOpeningConnection) ---> Microsoft.Reporting.WinFor ms.ReportS erverExcep tion: 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.Fo rAnalysis( DataRow row)
at MyRepScheduler.Service1.ob jTimer_Ela psed(Objec t sender, ElapsedEventArgs e)An error has occurred during report processing. (rsProcessingAborted)MyRep SchedulerS ystem.Coll ections.Li stDictiona ryInternal
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.
Thanks,
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.WinFor
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at MyRepScheduler.Service1.Fo
at MyRepScheduler.Service1.ob
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.
Thanks,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.