Getting an error for a duplicate definition was found for user.... How do I fix this?
Craigbob
Posts: 3 New member
Hi all,
We just implemented SQL Source control in my company. It's hooked up to Azure Devops via Git. We're getting an error that states there's a duplicate definition for a user and to check case sensitivity options etc...
Our databases ae set to case insensitivity, and I confirmed that there's only one user with that name in the database. Now the same user exists in different databses on the same server/instance, but since they're in different dbs that shouldn't cause a problem.
Is it a problem if I delete the folders in the trainsients folder? would that solve the issue or would it reoccur?
We just implemented SQL Source control in my company. It's hooked up to Azure Devops via Git. We're getting an error that states there's a duplicate definition for a user and to check case sensitivity options etc...
Our databases ae set to case insensitivity, and I confirmed that there's only one user with that name in the database. Now the same user exists in different databses on the same server/instance, but since they're in different dbs that shouldn't cause a problem.
Is it a problem if I delete the folders in the trainsients folder? would that solve the issue or would it reoccur?
Tagged:
Answers
Please take a look at this article for troubleshooting the duplicate definition error in SQL Source Control:
https://productsupport.red-gate.com/hc/en-us/articles/4407476864401-Duplicate-definition-troubleshooting-in-SQL-Source-Control
Victoria Wiseman | Redgate Software
Have you visited our Help Center?
Hi,
Posting an update here with details from the work conducted with our support team directly on this request.
My understanding a solution has been found for this issue through the following
There was an issue with reconnecting one of the databases
</code></p><pre class="CodeBlock"><code><p><code>git exited with code: 1
warning: git-credential-manager-core was renamed to git-credential-manager
warning: see https://aka.ms/gcm/rename for more information
This was potentially solved by configuring the git buffer to avoid remote failing.
Details on solving that available here:
https://confluence.atlassian.com/stashkb/git-push-fails-fatal-the-remote-end-hung-up-unexpectedly-282988530.html