Custom Report Error & Web Report Server Problems

This may or may not be helpful, but I think you may need to sit down with your network people and figure out exactly who is responsible for what, when it comes to application configuration and support. I'm the sole DBA for my organization, and my network guys' jobs are done when the servers are running and backed up, and the IPs and domain names are pointing to the right place. Everything beyond that, from installing the server applications to getting the client to run on a staff machine, is essentially on me, and so I have a level of access to those servers that allows me to do my job.

Someone may be able to chime in with a "to solve your problem do x" answer, but ultimately if there's an organizational issue here causing "not my job" syndrome, your efforts spent solving that problem will yield results far more valuable.

Hi Lee-Ann,

I have seen the authentication token issue several times before.  I initially saw this when generating the Plan Summary standard Tessitura report, and at that point it was a problem with timeout.  I opened a ticket with TASK at the time and they helped me change the timeout settings.

However if you're seeing it on multiple reports, it is likely not a timeout problem.  I have seen the same error in our Test environment, and TASK again assisted me in resolving it with a number of troubleshooting steps.  Ultimately, I had to change the bindings settings on the site running the WebReports service in IIS on the SSRS server.  

So I guess I'd say TASK is your best bet!  If yuo're an IIS newbie (like myself) they can guide you through the troubleshooting process.

And I agree with Nick on sorting out whose business is whose with network admin! Good luck!

Thanks Nick.

I've already had that discussion with them.  Unfortunately this is all their job, they're not open to me having that type of access - it's an external company we use.  It's under discussion, internally.

Thanks Frances, I will raise on TASK :)