What's new
Carbonite

South Africa's Top Online Tech Classifieds!
Register a free account today to become a member! (No Under 18's)
Home of C.U.D.

Need some help with Sage evolution (MS SQL) authentication.

Rickster

Legendary Member
Rating - 100%
13   0   0
Joined
Jul 3, 2013
Messages
1,539
Reaction score
677
Points
5,655
Hi all, been having a bit of an issue with a friends Sage Evolution, something went funny on the server and we had to relink the DB in MS SQL studio with the SQLExpress. Im not too clued up with this so if im missing any steps please let me know.

When he uses RDP into the admin account on the server he can login but when he tries with his user on RDP it gives him an error about user cant be found. Sage is using NT authentication and there is a username for him on the server.

Do i need to add logins in MS SQL studio somewhere?

Thanks.
 
Hey man

Check if his user is part of the RDP group on that machine. Since it's a local account and not AD, the allowed users should belong to the RDP group.

Or if the user belongs to the administrators group.

Sent from my LG-H870 using Tapatalk
 
Hey man

Check if his user is part of the RDP group on that machine. Since it's a local account and not AD, the allowed users should belong to the RDP group.

Or if the user belongs to the administrators group.

Sent from my LG-H870 using Tapatalk
Sorry, need to clarify, he can RDP with his user but when trying to login to the Sage evo program it throws an error.
 
how does Sage connect to SQL? does it use AD authentication or a SQL user.
When you say relinked the db, did you copy it to a new server?
If so, you may need to recreate the SAGE user on SQL
 
Do i need to add logins in MS SQL studio somewhere?

Thanks.
Likely,unlikely they added a Security group to the SQL access list on the server

Go to the Database security,users,add user there
 
Yup basically whay they said, except for an extra note.

Sometimes if this DB was relinked, then yes you have to re-assign permissions.

But often you will have to expand the DB in SSMS first and expand the Security and then remove the old sser as duplicate users are not allowed.

After removing the old user you can then go the the SQL Server Users not on the specfic DB and add the required user.

You could also just do something like

USE db_name;
DROP USER [ IF EXISTS ] username;

Sent from my LG-H870 using Tapatalk
 
Likely,unlikely they added a Security group to the SQL access list on the server

Go to the Database security,users,add user there

Cheers all, just an update this was the issue, I could see the administrator was already there hence why i was able to use Sage evo while logged in as Admin, so yeah, added user then ticked the sysadmin box and worked perfectly. Thank fuck.
 

Users who are viewing this thread

Back
Top Bottom