Question : Reporting Services Error

This morning my Reporting services stopped working.  It worked yesterday when I left.  No changes were made to the server.  Below is the output of the SQLDUMPER_ERRORLOG.log.  The initial error was Arithmetic operation resulted in an overflow. (rsRPCError).  I could find very little on this except it might be a memory issue.  I decided to reboot the server and the error changed to internal error occurred on the report server.  Any thoughts?


04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 2624
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x1A1A2A04
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir =
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile =
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName =
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName =
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
04/01/09 09:50:17, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\SQLDmpr0025.mdmp
04/01/09 09:50:17, ACTION, ReportingServicesService.exe, Watson Invoke: No

Answer : Reporting Services Error

On to the next suggestion then...

As it cannot get more messed up than it is, try creating a new database in the Database Setup page of the config tool.  Hopefully that works and solves the issue.

BTW: could the reboot have caused a change to the account with which the SSRS Windows service starts?  Through some forced script pushed by another department or whatever? (just want to rule this out)