Dear Community, Dear Experts,
I’m a newbee here in the Forum and this is my first post so I hope I will stick to most of the rules I learned in the beginners guide but please be patient in case I missed some in my post 
We started today the upgrade of our on prem Orchestrator which is currently running on version 2019.10.4. I’m doing such an upgrade for the first time and therefore it went pretty well but after all our packages got migrated successfully on the DB some additonal installation steps started and after a while we received the following error message:
*System.Exception: Error:-1, Message:An error occurred while migrating orchestrator data. Violation of PRIMARY KEY constraint 'PK_AspNetUserLogins'. Cannot insert duplicate key in object 'identity.AspNetUserLogins'. The duplicate key value is (Windows.Scheme, S-1-5-21-632532318-2666670698-1580278117-660243, e4d1c12b-983a-41db-9320-c2d2cd98b7c1).*
*The statement has been terminated.*
*at UiPath.OrchestratorCAs.IdentityDatabaseManager.RunDbMigrationToolObfuscatedLogging(String arguments, String[] tokensToObfuscate)*
*at UiPath.OrchestratorCAs.IdentityDatabaseManager.MigrateUsersFromOrchestratorDb(String webConfigPath, String identityPublicUrl)*
*at UiPath.OrchestratorCAs.IdentityDatabaseManager.ApplyDbConfigMigrationsOnInstalling(String webConfigPath, String identityAppSettingsJsonPath)*
*at UiPath.OrchestratorCAs.CustomActions.Deferred.UpdateConfigurationAndDatabasesAction.ApplyIdentityDbConfigMigrations()*
*at UiPath.OrchestratorCAs.CustomActions.Deferred.UpdateConfigurationAndDatabasesAction.Execute()*
*at UiPath.OrchestratorCAs.CustomActions.Base.BaseCustomAction.InternalExecute()*
I tried to check the entries in the database but when I checked the whole table identity.AspNetUserLogins was empty. Additionally I think this is a new table which was not there in the 2019.10.4 version so I’m wondering why and how it can happen that there are duplicates in this table…
All steps were rolled back afterwards and now I can’t see these identidy tables any longer in our database.
Could you please help me to understand if there is something we did wrong or what can be done to identify the root cause of the issue? The whole upgrade process stopped now and currently the orchestrator is down.
Thank you very much in advance for your help.
Best regards,
Andreas
5 posts - 3 participants