Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion


SQL User Logon Issue

By tundraroamer ·
We had to move both our SQL 2000 and application software to a new servers. Everything was reinstalled as original. All Databases were moved by backup/restore method. Users can logon to the primary application which access the SQL database without problem.
The issue is when they try to run Crystal Reports (also installed on the new application server same as original) they are getting a pop up box asking them to logon. No logon will work except for sa which is not the correct answer. The same type of problem exists when they use MSQuery in Excel.
This appears to be a permission issue but we can't find it. The server setups appear to be identical with one exception, the 2000 Advanced Server OS SP is version 4 not 3 as on the original. We are NT Terminal Server/Citrix based. No changes were made to that server or set up. The ODBC was pointed to the new server location, The Crystal Reports were all reset to the new server location and the database verified as up to date.
Only the admin logon does it all work correctly. What did we miss or misfire on?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to SQL User Logon Issue

Were the correct security groups granted permissions on the new server? The GUID will be different on the new server, which could cause an issue. This would explain why they are seeing a login box requesting authentication and why the SQL server database is attempting to authenticate them.

Collapse -

by Tony Hopkinson In reply to SQL User Logon Issue

Are you using integrted security ?. If so you may find that your users, logins and groups all exist, but they are incorrectly linked, Intenally it uses the SID and these probably won't be the same. Used to see this regular after a reload. Superuser login was in the readonly group and vice versa when you went into SQL Server's control centre

Related Discussions

Related Forums