tacy.highland (8/28/2014)
Unfortunately neither one helped. Same behavior as before.Anything else?
Sorry, I'm basically tapped out. The only other things I can think of are:
1. A network trace using something like WireShark or Fiddler to see what's passing from the client to the report server
2. A SQL trace on the SQL Server hosting the ReportServer to see what's happening there.
3. A SQL trace on the SQL Server hosting the data to what's happening there.
These things might show you where the problem is happening.
One question:
How are permissions setup on the report?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question