I am just getting started. Have completely setup and installed SSRS. I have created my first report and am trying to deploy it.

It let's me deploy it without error. Sometimes I can view it from the webpage where it's deployed and sometimes I get the following error "An internal error occurred on the report server. See the error log for more details."
Sometimes if I can view the first page of the report, I will get that error when moving to the second.

I have checked the SQL server logs and there are no error messages corresponding to this, there.

So I guess I have 2 questions:

1. What error log is it referring to?
2. Has anyone else seen this error and how can I fix it?

Thanks in advance for any help!
Sunny

This is the Reporting Services Service error log

Unlikely to be to do with the report itself

Rgds, Geoff

We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.

Please read FAQ222-2244: How to get the best answers before you ask a question

Thanks for the response.

I found an error log here: \microsoft SQL server\<SQL server instance>\reporting services\logfiles

Is that the log you are referring to?

Here is the message from the SQLDUMPER_errorlog in that folder:

02/14/08 10:19:34, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () failed (00000514)
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6008
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x1D125860
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
02/14/08 10:19:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
02/14/08 10:19:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
02/14/08 10:19:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\SQLDmpr0022.mdmp
02/14/08 10:19:35, ACTION,                  w3wp.exe, Watson Invoke: No

Can you give me any hints as to what this means? I have googled and searched this site for key words from this log to no avail.

Thanks very much!
Sunny

Ok for anyone following this thread- here is a link to what I found to be my problem.

http://blogs.msdn.com/mariae/archive/2007/12/10/reporting-services-internal-error.aspx

Here is a little blurb from it:
The issue was caused by a problem with the hardware AMD processor with PowerNow technology enabled in the BIOS (using technology Cool'n'Quiet). Please check if that is your case.

The following article describes the underlying cause of it, which seems to be casing secondary effects in other applications like Reporting Services.

SQL Server timing values may be incorrect when you use utilities or technologies that change CPU frequencies

http://support.microsoft.com/default.aspx?scid=kb;EN-US;931279

 

To get rid of this error, first of all, you should find out if your machine has an AMD multi processor by checking the Properties of the “My Computer”, under the general Tab.

If that is the case (If you can confirm that your machine is has an AMD processor) you have 3 options:  1) Update the BIOS on the computer (to disable the Cool'n'Quiet technology from the BIOS), 2) modify the Boot.ini file to use the /usepmtimer switch, or 3) Install Cumulative Update Package 5 for SQL Server 2005 Service Pack 2 (http://support.microsoft.com/default.aspx?scid=KB;LN;943656)