When a Solomon SL user tries to run a report, we see the below errors in the SQL Server Error Log. This behavior has been explained to me as expected, but the reason for it has not. The users have local DSN's configured with SQL authentication, none of which work or seem to be used. I have a few questions I was hoping the community could help with.
1. The pattern of an empty string, AD account, empty string, and AD account is consistent (below). Again, it's also not how any of the client's DSN's are configured, they are all configured to use SQL authentication with accounts entered into the Login ID field. What is the reason for this behavior being reported in the SQL Error Log?
2. It was explained to me that Crystal reports in Dynamics SL will create the DSN's if it doesn't detect them on the client. This explanation doesn't make sense to me as they're not being used. Can someone explain this behavior?
3. The local DSN's configured on each users work station do not work (32 & 64). The SQL account configured in the DSN and the AD account displayed in the Error Log do not exist on the target database server. So each time a report is ran, broken DSN's are created and invalid users are attempted to authenticate to the database server. What is the reason for this behavior?
4. Ultimately the primary issue I'm trying to resolve are the error log entries in the database server error log. Is there a solution to preventing the error log entries other than turning off login auditing on the entire database server?
2016-03-29 11:49:20.300 Logon Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: XX.XX.XX.XXX]
2016-03-29 11:49:20.300 Logon Error: 18456, Severity: 14, State: 58.
2016-03-29 11:49:20.290 Logon Login failed for user 'DOMAIN\USER'. Reason: Failed to open the explicitly specified database 'DATABASENAME'. [CLIENT: XX.XX.XX.XXX]
2016-03-29 11:49:20.290 Logon Error: 18456, Severity: 14, State: 38.
2016-03-29 11:49:20.280 Logon Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: XX.XX.XX.XXX]
2016-03-29 11:49:20.280 Logon Error: 18456, Severity: 14, State: 58.
2016-03-29 11:49:20.270 Logon Login failed for user 'DOMAIN\USER'. Reason: Failed to open the explicitly specified database 'DATABASENAME'. [CLIENT: XX.XX.XX.XXX]
2016-03-29 11:49:20.270 Logon Error: 18456, Severity: 14, State: 38.