Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
If you find yourself in a situation where you are being prompted for a login when running reports, try the following:1 - Run the "synchronize all ownership and security" process in SL database maintenance - take note of any error message you may get 2 - If that doesn't work, try to delete the E8 user and recreate it. To do this: a - login to SQL. under Security -> logins, right click on the E8F575915A2E4897A517779C0DD7CE user and select properties. b - under the User Mapping page, uncheck the checkbox next to all the databases and click OK. c - The back under Security -> logins, right click on the E8F575915A2E4897A517779C0DD7CE user and select delete d - re-run the "synchronize all ownership and security" process in SL database maintenance which will recreate and re-map this user
We received a similar situation after creating test databases with copies of live data. We updated the test databases as per the instructions on creating a test database and ran all the necessary queries, synchs, etc. We ran through every scenario we could locate, but all users (other than sysadmin) would be prompted for the E8 password when running any report.
It was necessary to delete the test databases before we could get past this issue.
Is there a known issue with copies of live databases on SQL 2012?
Any thoughts would be greatly appreciated.