Skip to main content

Just started on upgrading our Dev environment from v4.7 to K2 5.2

 

Upgrade itself has completed, however K2 Core - Installation Health Failed.

Log below, any ideas?

 

Installation Health
-------------------
Analysis Result: Failed.

The following errors were logged as part of the install:
Failed: System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at SourceCode.Sync.Storage.Sql.SyncEngineContext.GetADUMProviderInstances(XElement roleInit)
at SourceCode.Sync.Storage.Sql.SyncEngineContext.GetRoleInitProviderInstances(String roleInitValue, Boolean& adumInstancesExist)
at SourceCode.Sync.Storage.Sql.SyncEngineContext.GetRoleInitProvider(IProviderType legacyProviderType, IProviderType adProviderType, String providerName, String roleInitValue)
at SourceCode.Sync.Storage.Sql.SyncEngineContext.SeedExistingProviders()
at SourceCode.Sync.Storage.Sql.SyncEngineContext.DatabaseMigrate()
at SourceCode.Install.Package.Actions.Database.Migrations.MigrateDatabase.<>c.<ExecuteMigrateSyncEngine>b__3_0(String connectionString)
at SourceCode.Install.Package.Actions.IsolatedExecution.AppDomainDelegate.ExecutetT,TResult](T parameter, Func`2 func)
at SourceCode.Install.Package.Actions.IsolatedExecution.ExecutetT,TResult](T parameter, Func`2 func, String privateBinPath, Boolean enableLogging)
at SourceCode.Install.Package.Actions.Database.Migrations.MigrateDatabase.ExecuteMigrateSyncEngine(String dbConnectionString)
at SourceCode.Install.Package.Actions.Database.Migrations.MigrateDatabase.Execute(Target target)

Target failed to execute: SyncEngine

Duration: 0 seconds

 

Hi,


 


'An item with the same key has already been added' error indicated that something held off during the upgrade and the installer couldn't update it. It's possible that an end-user might have tried to close or navigate to K2 Designer, an inactive session of Package Deployment tool was still opened at the time. Perhaps, you can find this error in the K2 installertrace (i.e %temp%). If you go back a few lines, it might give some clues/details about it. 


 


 

It is none of those, its a dev box, only i was using it, all forms and workflows were checked in prior to upgrade.

 

I opened a support ticket was told to ignore the error

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings