-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to validate data - Error logging into the SSRS Portal #121
Comments
having the same error when i do the scale out deployment |
Thanks @manceelee for suggestion. It actually worked by adding the following into rsportal.exe.config
I guess it should have imported the machine key from the reporting service instead of getting from own configuration file. |
I'm facing the same error exactly however I can't get it to work by adding the |
The same is happening here. If I add the machine Key in rsportal.exe.config it is removed on startup. |
Hi @n1LWeb, have you added your machineKey to rsReportServer.config under Also make sure it's in the correct format otherwise it get's wiped for me.
After this restart the Report Server and it should sync the machineKey to rsportal.exe.config. |
Hi guys,
I'm getting an error running the SSRS Portal after configuring CustomAuthentication (as per example provided in the repository) from
Reporting Services Custom Security Sample for Power BI Report Server and SQL Reporting Services 2017
The issue is regarding MachineKey as seen from the error logs. I'm following all the instructions given in the above sample but still no luck yet.
I'm running the SSRS 2017 on my Dev PC (Win 10 Pro).
The custom login works well (Register and Login) for the report server at: http://localhost/ReportServer_SSRS, but the portal (http://localhost/Reports) doesn't work after Login. It returns the 500 Internal Error message. Stack trace is given below:
RsReportServer.config file is attached here for reference
rsreportserver.config.txt
Please suggest if there's anything wrong in the configuration, or I'm missing out on something. Or probably a bug in the operating environment?
Thanks in advance!
The text was updated successfully, but these errors were encountered: