search

alanjuden / MvcReportViewer

Custom Report Viewer control to replace MS Report Viewer on MVC projects (also works on .NET Core as a Report Viewer).
MIT License
173 stars 109 forks source link

Export Works Local but Issues when hosted in IIS #51

Closed cgountanis closed 6 years ago

cgountanis commented 7 years ago

Strangest thing it is like the credentials are not being passed when I host the Core 2 application under IIS. It has been working perfectly under Visual Studio, even talking to a remote ReportServer via VPN on HTTP line. I wanted to test the publish and the application works perfectly until I try and use the reporting features. Right now we only use EXPORT, we are not even using the viewer. Might be an issue with the creds being sent via SOAP, IIS setting not sure. I made sure IIS has Anonymous and Windows Auth enabled for the web site. App_Pool tried none, tried 4.5 tried appIdentity/NetworkService. This is just strange. I am sure the user name and password is being sent into the report model as well.

Does it need any features under IIS like 3.5 HTTP Activation, etc...

Any have a simple solution for this?

Error: One or more errors occurred. (The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was ''.)

cgountanis commented 7 years ago

I found out this has something to do with IIS AppPool permissions, and nothing else in IIS settings, don't waste your time.

Help me? https://stackoverflow.com/questions/47416234/core-2-mvc-wcf-to-ssrs-execution-project-needs-administrator-iis-apppool-to-wo