Microsoft SQL Server 2005 DSN

Is the login established at the server level?  If not, do so, and grant the login appropriate rights to the database it needs to access.  If you get a 'duplicate user', delete the user at the database level, then repeat these steps.  All of this is most easily done through Enterprise Manager (or whatever they call it in SQL Server 2005).

The link Nightman passed you I look on as something you want to use when you have very large numbers of users to transfer.  The steps I've outlined work well when all you want to do is fix a couple of users, and it is a procedure that has worked well since version 6.0, so I expect it to work in 2005 as well.

If that Username is in "Domain\User"-format the appliction tried to establish the connection using integrated security. If this is what you inteded, you should check if that user has been granted permission to connect to the SQL-Server-Database.

I am assuming that phone006 is a SQL account.

If the servers are both on the same domain, the SID (security identifier) of the login will not have changed. Since the permissions are stored in the database, this is unlikely to be the case. HOWEVER, it is possible that the user account has not been granted permission to log on to the server - this would need to be checked.

Please check with the same and let me know if not happening.

sketchy929 ,

Please run this statement to check if there are any orphan users in you database -> sp_change_users_login 'Report'  <-

Return the values to EE

Best Regards,

Paulo Condeça