I have a really wierd one here. I have generated several reports that work wonderfully for me but will not work for others under certain conditions. The difference appears to be the fact that I am an author, publisher, etc; and others are just browsers. Now this wouldn't be too bad to resolve BUT, everything works fine as long as I have run at least one report before anyone else runs it. If I do not run a report then anyone in the browser role will get a reporting services internal error message with no further information. As soon as I run one report, all and sundry can run whatever report they wish with no problems.
I have checked and re-checked security settings and am at a loss.
I am running SQL Server 2000 on a dual processor box. The server is restarted each day at 4am and I suspect that this is something to do with the issue here. Any help would be most appreciated as this problem appears to defy logic!
Reporting Services funny
Hot Topic
- cannot login
- SQL Express connection limit
- Parsing Text String Field - comma delimited
- Import from adaptive server anywhere 9
- Reporting services passing parameters
- Still a problem with Report Refresh Icon
- RAISEERROR from CLR stored procedures
- Can Visual Studio 2005 BI co-exist with Visual Studio 2003?
- What is a Transfer Task?
- Internet explorer script error
SQL Server
- Problems with connecting to SQL Server 2005 Express
- now its invalid object name instead query timeout expired
- Using Transactions causes database connection to fail
- User defined functions in MSAS
- Pause between pages when printing RS report
- Variables Not Seen In Custom DataFlow Destination
- Sql server Express 2005 Advanced
- Data Flow Task- Error Output
- URGENT: SQL 2005 : All schedulers appear deadlocked
- Internal Query Processor Error
Reporting Services funny
Steve Tyson
How exactly is it not working if the non-admin users navigate to the reports first. Can you post the exact error message, as well as the error from the RS log files Reporting Services\LogFiles\ReportServer(datetime).log