Dynamics Community Forum Thread Details

SL 2018 Logon Fail

We are in the middle of an SL 2018 test upgrade for a new client. The upgrade procedures ran well, but when trying to logon we are unable to connect to the SQL server. The SQL Server resides on another box, is a default instance and is operational. In troubleshooting we've done the following;

1) Restarted SQL Services

2) Verified Port 1433 and 1434 were open on windows server firewall

3) Tested with the firewall off

4) Checked the CLICONFG utility, made sure TCP/IP and named pipes were enabled

5) Tested the order of TCP/IP and named Pipes

7) Verified server could be pinged from TS Box

8) Tried setting up an alias

9) Tried connecting with the iP address instead of the server name.

10) Verified I could make an ODBC connection using SQLNative Client 11

In each case was unable to complete a successful logon to SQL Server. The process errors out with a System Message 5003 and the following message detail: "Unable to open the specified server database CVMDSQL ( 66)

I am running out of things to check. Is there something I may be missing. Please advise. Look forward to a response.

This might be a security problem at database level. It often happens that the SQL users and logons are messed up after a backup/restore or migration operation. The database maintenance utility should address most of it. Try running the 9829000.exe and select the "Synchronize all ownership and security" and "update views" task. The logon credentials for the utility can be any sysadmin SQL credentials (SQL or integrated), not necessarily SL application users.

Other things to check:

1. Is CVMDSQL the host name you expect to see? If not, check for stale solomon.ini files in your system.

2. SL operates either with integrated security (Windows credentials) or SQL authentication. Check which scheme is actually activated and whether it match the one you expect.

3. If you have access to SQL management console, check the Security/Logins and (SYS and APP databases) Database/Security/Users. Do any of them seem underpopulated? The DB maintenance utility should address this.

4. If the utility doesn't correctly link your database, check the contents of the SYS database Domain table. Look for stale entries under the ServerName and Database fields. The ServerName should match CVMDSQL and must be a name the TS client can resolve.

5. If still got problems, check for the annoying SQL orphaned users effect. Try googling for it, there are several ways to solve it.

Quick Links