ASG RD 2018 connection fail

[chengjian.ye]

Hello, I upgraded ASG RD to 2018 with SQL server 2016 in my company.
After upgrade, there are some users cannot connect to database environment.
The authorization is by AD group,  set in "Security Groups".
I have checked that user's AD account in "User account"
Could you give me a hand, how to trouble shooting this problem?
Thank you.

[DevOma]

Which error message the users get?

[chengjian.ye]

       

Please see 2 screenshot, one is error when test connection, another is user list.
Thanks.

[DevOma]

It's the permission in SQL server - see help file for necessary permissions on SQL Server

Working with environments=>Working in database mode=>Necessary permissions on SQL server instance

[chengjian.ye]

Hello, Oliver,

these 2 screenshot are correct?

       

[DevOma]

Yes - now you have to check if the user is assigned to this group and have access to the server

[chengjian.ye]

Hello, Oliver,
After Database permission setting, now user can login ASG RD 2018.

But it's strange that there is no "Connections" for normal users, although I have enabled any permission for user group.
Could you see what's wrong?
   

[DevOma]

Check the permissions on "Connections" - goto Properties => Security

[chengjian.ye]

This screenshot?
   

By the way, there is one user still not able to pass "Test connection"
even "Security Group" disabled, and "select" "execute" & "select" enabled for public in SQL server

[DevOma]

Yes - you need to add security groups or add your users to Administrator group

If "Test connection" fails the user can't access the sql server / database - it's network / security related!

[chengjian.ye]

Sorry, Oliver.
You mean if i enable "Security Groups" by "active user permissions", then only users in "Administrators" can work normally?

[DevOma]

In your screenshot there is only the Administrators group assigned - so only assigned users to this group are allowed on this item (and sub items) - you can Add security groups and set permissions on each object (or inherit to child objects by default) - you need to login as Admin to set these permissions on object level...