“is not an existing data source name” errors with odbc

On some new machines that I’ve been building I’ve had major issues with SYSTEM dsn’s not working properly and getting the “DSNNAMEis not an existing data source name” when trying to configure a dsn…. Eventually I found an answer…..

The problem seems to be that when the dsn is configured as a user, the permissions on hklm\software\odbc\odbc.ini\DSNNAME is set so that only system and the user have access to that key. Anyone else does not have access. A short term solution is to add everyone with FullControl to these dsn’s within the registry and things work when logged on as a different user. I thought the whole point of system dsn’s was so that one user could create one and then everyone else on the system could use it.