You’re offline. This is a read only version of the page.
2,165
I know that there are several solutions offered for when you are prompted for the E8 password when running reports.
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.
Does anyone know if this is a known issue with copies of live databases on SQL 2012?
Any thoughts would be greatly appreciated.
*This post is locked for comments
I have the same question (0)
I have not had this problem. But I also run a script on my application and system DBs to correct orphaned users and the E8 user is always orphaned. The first statement will give you a list of orphaned SQL users. The second will relink the orphaned user as long as it exists at the server level just replace E8User with the user from the first statement. Run this on all App and Sys DBs.
exec sp_change_users_login 'Report'
sp_change_users_login 'auto_fix', 'E8User'
Share
Report
All responses (
Answers (
