Custom Report Error & Web Report Server Problems

Hi all

I've just started working in a company who haven't had a database administrator in a very long time, therefore I am starting to use tools that haven't been used before.  It's an incredibly frustrating experience, especially given that our network support aren't being every helpful.  I would be grateful for any advice or recommendations so I can go back to our network support and tell them exactly what they need to be doing to resolve this.  We are on v11.

My first problem is the Web Report Server - it's intermittently working.  When running a SSRS report via Tessitura, the user is asked for their login details.  When you log in you get an error message - our network support say it's me but other users are experiencing the same problem:

Exception of type 'System.Web.HttpUnhandledException' was thrown.
There was an error processing this request. Please check the details below.
The authentication token is not valid. Please retry with a valid token.

My next problem is the below error message.  This appears when I try to run a new SSRS custom report.  I know there is something wrong with the dataset (I don't know exactly what because I can't access the error logs) but I get this error message when first opening the report - any ideas:

Thanking everyone in advance

Parents
  • 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!

Reply
  • 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!

Children