Reporting Web Viewer - Failed to establish the following data connection

[Kim_Hammers]

We are trying to install Reporting Web Viewer, so we can generate URL links to our Dashboards. We are successfully generating the dashboard URLs, and the user is prompted to enter Parameters (as necessary), but then the final connection fails with this error message. The connection listed is the Data Provider for the dashboard. We've reviewed the MRG, but can't figure out what step we are missing...

[aboucher]

Hi @Kim Hammers,

I changed the tag for this community question from Community (Site) to Reporting Dashboards. For the best customer experience, please always tag your question with a specific product / module so that community members following that group will be notified when you post your question. 

For more information, see How do you ensure the right people see your questions? 

Cheers! 
~Alan 

[aboucher]

Hi @Kim Hammers,

I've seen your same data connection issue and error message in a few support cases.  These were resolved by setting the "Identity Impersonate" option appropriately.

If your "Identity Impersonate" setting in the AppNet web.config is set to "TRUE" but you do not have an identity account configured.

Do one of the following:

• Set the "Identity Impersonate" value to FALSE in the AppNet Web.config. See Disabling Impersonation.
• Specify an impersonation account Username and Password in the AppNet Web.config. See Enabling Impersonation.

I hope this helps!

~Alan

[Kim_Hammers]

Thank you for this information! We verified that Identity Impersonation is set to false and it is disabled. We are opening a case with our first line of support. I will post again when I hear back from them.

[Kim_Hammers · Accepted solution]

Working with our first line of support, we were able to determine that this was a user authentication issue. The solution was to make sure our Reporting Viewer user matched our AppNet user. Once we did that, we were able to generate/access Dashboard URLs.

One last hurdle that we came across had to do with the generated URL being too long to render. This was because our Dashboard has several Parameters, which makes the generated URL very long. To fix that, our FLOS / Hyland suggested the following changes to override the defaults used in IIS.

1. In your ReportingViewerWeb.config (C:\inetpub\wwwroot\Reporting Viewer\) file add MaxQueryString="32768" to the request Filtering/requestLimits node

2. Add maxQueryStringLength="30000" to httpruntime node

3. In your AppServer (C:\inetpub\wwwroot\AppServer) web.config file Add MaxQueryString="32768" to the Security/Request Filtering/RequestLimits node