Upgrading to SQL 2005 - Missing user

Open discussion about our Alloy Navigator 5 application

Upgrading to SQL 2005 - Missing user

Postby slandis@amospress.com on Mon Apr 30, 2007 4:35 pm

When trying to move our Alloy db from SQL 2000 to SQL 2005, we are having user problems. The main technician that generally makes all the changes seems to be missing from the db users list. Below are the steps used to recreate the problem.

Detach db from SQL 2000.
Copy files to new server.
Attach db to SQL 2005.
User missing. Cannot log in to Alloy with this user.

I have tried the command 'sp_change_users_login report', but it does not report the user in question. It reports every other user and I am able to log in with them.
slandis@amospress.com
Junior
 
Posts: 5
Joined: Mon Jan 24, 2005 10:34 am

Postby pille on Tue May 01, 2007 4:15 pm

Most likely SQL accounts were not moved from the original server to the new server. You can find the full article in our Support Portal on moving databases between servers - http://support.alloy-software.com/?mode ... d=KB000470

The part that I believe is specific to your situation, you can find in Microsoft's Knowledgebase - http://support.microsoft.com/kb/246133/
Contact Technical Services directly:
support@alloy-software.com
http://support.alloy-software.com

Paul Ille
Alloy Software
Maximize your IT Universe
Follow us on Twitter: http://twitter.com/alloysoftware
Image
User avatar
pille
Alloy Software
 
Posts: 473
Joined: Thu Aug 11, 2005 3:11 pm
Location: New Jersey, USA

Postby slandis@amospress.com on Thu May 03, 2007 10:19 am

I got the logins populated correctly now and all users are able to log in to the database on the new server now. However, when I try to edit any user information in the Administrative Settings, I receive the message "User does not have permission to perform this action". I am a member of the "Administrator Role". We have tried this with multiple logins with the same effects.
slandis@amospress.com
Junior
 
Posts: 5
Joined: Mon Jan 24, 2005 10:34 am

Postby pille on Thu May 03, 2007 2:11 pm

My first guess is that it's a permissions issue on the SQL Server side.

If you go into SQL using Enterprise Manager of Studio Express, go under Security, find your login and right-click, go to properties and then look at the roles you have...are you in the sysadmin group?

If not, add yourself to it and then edit account info in A5. If you're able to do it then it may be a SQL rights issue.
Contact Technical Services directly:
support@alloy-software.com
http://support.alloy-software.com

Paul Ille
Alloy Software
Maximize your IT Universe
Follow us on Twitter: http://twitter.com/alloysoftware
Image
User avatar
pille
Alloy Software
 
Posts: 473
Joined: Thu Aug 11, 2005 3:11 pm
Location: New Jersey, USA

Postby slandis@amospress.com on Thu May 03, 2007 3:07 pm

That took care of the problem. We are up and running on the new server. Thank you for your help.
slandis@amospress.com
Junior
 
Posts: 5
Joined: Mon Jan 24, 2005 10:34 am


Return to Alloy Navigator 5 Discussion

Who is online

Users browsing this forum: No registered users and 1 guest

cron