SQL 2K8 R2 and Crystal Reports 8.5 - Login failed for user when bringing up DSN
We are running Crystal 8.5 (because customers don't want to upgrade or rewrite their reports) against a SQL 2008 R2 Server. They use a SQL account to connect to the DB and have to enter in the password when they run the first report in Crystal (click the lightning bolt). IT have noticed that the SQL Account becomes locked out after awhile. SQL Logs show quite a few 'login failed for user XXXXXX'. We tested and found that this message is generated when we click the lightning bolt and wait for the DSN login (they are using ODBC to connect) screen to appear. Enforce password security is check on the server. IF we remove this check, the login failed messages don't appear and the account doesn't get locked out. Anybody have thoughts on this? We didn't see this in earlier versions of SQL.
If you mean you have the 'Enforce password policy' box checked then you are telling SQL to use the same policy mechanisms as the underlying windows server. One of these is password expiration :
http://msdn.microsoft.com/en-us/library/ms161959(v=sql.105).aspx This setting is ON by default. In earlier versions you may have had someone configure the logins to not have this option.
Was there anything special you needed to do to make Crystal work with 2008? I am trying to accomplish the same thing, but Crystal APS is returning "Unable to open database. Verify data source name and availability, and database security." The ODBC connection works fine, and I believe the security is setup the same as when it was running under 2000. Any insight? Thanks!
We ended up unchecking the password security which prevented the errors. As far as setting up Crystal, we're running 8.5 and XI in our environments and there was nothing other than making sure to put the latest SP for Crystal on them to make them work.