Answered

Changing a connection reference owner or creating a new connection reference

(0) Share

Report

Posted on by westerdaled

676

I did a reinstall of managed solution in an environment under a service account, in one of our test environments. Unfortunately , there was previously configured connection reference in place under a user account. Now this presents a problem as this user does not have the desired db roles on SQL Server, Yep my users are getting those annoying "you are not authorised to access this DB Server / Database prompts.

Is there a way to change the owner or recreate the same connection reference under the service account, either manually or via CLI command? We are using a CD/CI pipeline but not Azure DevOps.

Categories:

Governance & administering

All responses (2)

Answers (1)

Sort by

Verified answer

eleung83 232 on at

Like
a
(0)

Report
Copy link

Link copied!

If memory serves me well, it shouldn't matter who owns the connection reference itself, as this is a solution component, but I think you may be getting the error due to the connection that's being used by that connection reference..

I'm guessing that the connection that is being used, is owned by a specific user using that user's specific credentials to access the SQL db, but that SQL DB doesn't allow that specific user to login. You can try to change the connection used by that connection reference to another connection that you can create with a different set of credentials using, for example, the following Dataverse connection reference:

But I'm not sure if you can share the SQL Connection itself with other users (the example above is for the Dataverse connection reference and the Dataverse connection cannot be shared with others)
westerdaled 676 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @eleung83

Thanks for your reply. The SQL Connections are all implicit which is great as I don't need to add each user's login to each SQL Server instance. This is how I have set up the other environments. However, I think you are right. I recently changed a connection owner by editing the connections under Dataverse tab, in the Power App details pane. Thanks for reminding me . Anyway, I won't be accessing this client's environments until Monday but I will let you know how I get on .

Update: you are 100% correct. Looks like the Connection reference owner is the person who created this connection reference in the environment for the database. In my most recent greenfield environments, the connection ref owner and connection credentials are the same. Anyway whilst I have been away, it looks like one of the devs have gone in under Dataverse->Connections and configured the connection correctly.