Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Connection could not be established
#1
We currently have a production install of vRD2012 7.3.4144. We have 3 admins of the system and about 40 users that have various permissions all based on active directory groups. Over the weekend we have installed vRD2015 including Patch 4 to test prior to putting it into production. Once vRD2015 was installed we have created a new SQL database on the same SQL server as vRD2012 and successfully logged in. We then carried out the built in “upgrade of a 2012 environment” and again this went through with no issues. As an admin I can now login to vRD2015, get all connections and credentials etc. The issue comes when we try to login as another non-admin user. vRD2015 errors with “Connection could not be established. A connection to your current environment could not be established”
The test connection to SQL passes successfully for all users and this evening we have also added Patch 5 but this had made no difference.
Any ideas? And are there any connection logs or error logs we can look at?
Reply
#2
The message "Connection could not established" comes from your SQL server/instance. So there is must be anything with the security of the sql server. If your 2012 database configured with "Integrated auth login" or with "Username/pwd login" - did you set some permissions on your old database to ensure your users have the permission to log on to this database (and perhaps these settings are not made for the new database)?

You can check your application event log for more details...
Regards/Gruss
Oliver
Reply
#3
Thanks for the advice, it appears is was to do with the SQL permissions, we had matched the permissions we used on vRD2012 of db_datareader and db_datawriter. It appears for vRD2015 the group also needs db_owner, is this correct?
Also now that I am logged in as a standard user it appears the way permissions work have changed and the auto upgrade does not take account of this. Everyone using the system can see all connections apart from two specific folders. In vRD2012 we set the main “Connections” folder permissions so that all can see this then cascade down to the lower folders. We then just removed the inherit from the two specific so we could set the custom permissions. There does not appear to be a way in vRD2105 to remove the inherit?

Many thanks
Reply
#4
This is from the help :-)

In this chapter the minimum database security scheme is described for users who want to access the ASG-RD-database. To configure special permissions inside your data you have to use the Permissions functionality inside ASG-RD..

Choose "Logins" of your SQL server instance and add your user / user group. At least "public" must be checked to access the database.

Then select your ASG-RD database and goto Properties. In the category "Permissions" you have to grant your user(s) the right to "Connect" and "Execute.
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)