Has anyone got a database login prompt when trying to run a print preview in SL 2011?
It forces me to check a Use Integrated Security box to continue the print preview.
How do we skip avoid this step?
I'm not sure if this is the same problem you are seeing but I found a previous case in which a user was being prompted for the E8 user password when trying to print reports.
Here are the steps they took to resolve that error:
1. Make sure all users are logged out of SL.
2. Log in to SQL Management Studio and expand the 'Logins' folder in the Object Explorer pane. Please find the E8F575915A2E4897A517779C0DD7CE login and right-click on it and delete it.
3. Open up SL's Database Maintenance screen, enter in the SQL server name, and connect using the SQL sa login/password.
4. In the Update Databases tab, select your SL app and system db's, then select the 'Synchronize All Ownership and Security' scenario.
5. Click on the Update Database button.
6. Once the process has completed, see if the issues still exist.
RachelTechnical Support Engineer**This posting is provided "AS IS" with no warranties and confers no rights.
I am having the same problem as Chuck and tried your solution but continue to get the error. Is there anything else that might cause the problem?
Thanks, I'm new to forum so please let me know if I'm posting properly.
Yes, you've posted properly. Welcome to the community :)
There are a few reasons why this would occur:
1) The servername in the domain table is something other than the machine name (such as an alias). Ensure that the servername field in the domain table is populated with the actual machine name.
2) The E8 user account is getting locked out. In SQL Server Management Studio, right click on the E8 user and open Properties. On the General tab, ensure that the "Enfor Password Policy" option is Unchecked. On the status tab, ensure that the login is not disabled.
3) Another option that is similar to the steps in the original reply is the following:
a) Make sure all users are logged out of SL
b) Log in to SQL Management Studio and expand the 'Logins' folder in the Object Explorer pane. Please find the E8F575915A2E4897A517779C0DD7CE login and right-click on it and delete it.
c) Expand on any databases that are experiencing the error and expand on the Security folder. Expand Users, and if any E8 user exists right click and delete it.
d) Ensure you have a good backup of your databases and run the following statement against the system database:
delete from Domain where Description = 'report user password'
e) Open up SL's Database Maintenance screen, enter in the SQL server name, and connect using the SQL sa login/password.
f) In the Update Databases tab, select your SL app and system db's, then select the 'Synchronize All Ownership and Security' scenario.
g) Click on the Update Database button.
h) Once the process has completed, see if the issues still exist.
Hopefully one of these suggestions will work for you!
Thank you for the fast reply. Unfortunately, I am still have the problem after performing your suggestions. Would it help if I did a SQL trace? Do you think that would tell me something new?
If you run the following statement against your system DB(s) does anything get returned?
Select * from RptExtra
If there are records in there, delete them and run Sync. Then try previewing a report.
I also found these steps that others have said resolved the issue - some of them you may have tried already but try them again along with the other steps;
1. Delete 32-bit ODBC connections:
a. If on a 32-bit OS, these are under Control panel > admin tools > ODBC
b. If on a 64-bit OS, these will be in C:\Windows\SysWOW64 (launch odbcad32.exe)
c. Delete all ODBC connections reflecting all SL database names.
2. Delete all occurrences of the E8 login in Management studio:
a. Under Security > Logins
b. Under each DB > security > Logins
3. Against system DB:
4. Re-run Synchronize all ownership and security.
5. Launch SL and print-preview a report (this will re-create ODBC connections)
Many times this is caused by a lack of permissions in SQL. It wouldn't hurt to run a trace to see if that tells you anything. I would suggest using the trace templates to do this as we've modified them to show more detail that could help you. I'm not sure what version of SQL you are running but I'll include the links below to the templates:
How to use SQL Profiler in SQL Server 2008 and SQL Server 2008 R2 to trace database events in Microsoft Dynamics SL
How to use SQL Profiler in SQL Server 2005 to trace database events in Microsoft Dynamics SL
If you don't see anything in the trace yourself and would like an engineer to take a look at the trace, you will need to open a case.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13