SL Datamart Errors

(0) Share

Report

Posted on by SL_GP_BC_123

1,114

I am in the process of configuring MR (CU16) for a Dynamics SL 2018 implementation. The installation runs fine and the datamart creates without error, however we are having a problem when trying to enable and populate it.

The process appears to go through the motions, but then stalls towards the end. The following message is in the error log:

Cannot open database "SLSYTEM" requested by the login. The login failed.
Login failed for user 'E8F575915A2E4897A517779C0DD7CE'.

The implementation uses windows authentication and In troubleshooting we've done the following

1) Under Solomon Database Maintenance, Set the authentication type to "Windows Authentication" (without error)

2) Also under Database Maintenance, Ran "Synchronize all database ownership and security" (without error)

3) Recreated the datamart numerous times still with the error.

4) Rebooted the server

5) Compared and verified the 'E8F575915A2E4897A517779C0DD7CE' SQL settings against another working MR implementation

6) Ran the Solomon data verification scripts and corrected any issues

Regardless still have not been able to remedy the login issue. Before I open a formal case, is there something obvious I may not have considered. Please advise. Look forward to a reply.

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Laura 460 on at

Like (0)

Report
Copy link

Link copied!

You may want to try changing the database authentication to SQL Authentication and then back to Windows Authentication.

I recall issues with SL 2015 for another company that causes issues with Management Reporter and with the PV's in SL .

Laura

Was this reply helpful? Yes No
KyleBWillman 67 on at

Like (0)

Report
Copy link

Link copied!

I assume this is a test or sandbox environment, and not a production environment. If so:

How were the Dynamics databases created in the environment?

Is it the same DB server as production, or different?

Did you move production DB's from prod server and restore them into a test/dev SQL server?

Was it a backup of a production environment?

Sorry for all the questions, but might help!

Was this reply helpful? Yes No
SL_GP_BC_123 1,114 on at

Like (0)

Report
Copy link

Link copied!

Kyle,

No need to be sorry.

This is a test environment upgraded from SL2011 to SL2018CU3. It is separate from the production environment. Databases were restored to the new environment and upgraded without issue. Solomon screens and reports appear to be functional.

MR is a new install/implementation and CU16.

Any thoughts? Let me know. Thanks!

JG

Was this reply helpful? Yes No
SL_GP_BC_123 1,114 on at

Like (0)

Report
Copy link

Link copied!

Thanks Laura,

I tried that, but no luck.

Any other thoughts?

JG

Was this reply helpful? Yes No
KyleBWillman 67 on at

Like (0)

Report
Copy link

Link copied!

From what it looks to me:

Due to the fact that you have restored DB's from another DB server, sometimes the 07.... and E8..... users get disjointed due to SQL server SID vales stored in the DB's. I would drop the E8... user and potentially the 07.... user from all application and the system DB. Then, drop the login from SQL as well. Run the synchronize ownership through DB maintenance and let it recreate itself throughout. I think then you might get past this. It appears that restoring the DB's retained the old SID and it does not match the login. I hope this helps!

KW

Was this reply helpful? Yes No
SL_GP_BC_123 1,114 on at

Like (0)

Report
Copy link

Link copied!

Kyle,

That's makes sense. Was starting to think along those lines too. Will give it a try.

JG

Was this reply helpful? Yes No
SL_GP_BC_123 1,114 on at

Like (0)

Report
Copy link

Link copied!

I never closed out this case. Thanks to all who responded.

Turned out the client had an old invalid system DB reference in their domain table. Once removed then the datamart rebuild worked.

Was this reply helpful? Yes No