Symptoms
After upgrade to 4.6.9 on new server, I am having issues with the development environment. Initially, I could not publish service object changes and the smart objects referenced the old server. Now, after taking down the old server, I cannot get anything to work regarding K2 Connect on the dev environment and Visual Studio continually becomes non responsive. K2 remote services performed the install of the new server and version of K2, 4.6.9. The K2 client tools have been reinstalled on the development client. The development environment has not worked correctly since the install.
Diagnoses
The issue was caused by mismatch version of K2 Connect (4.6.5) installed on the client machine. After customer uninstalled K2 Connect 4.6.5 and installed 4.6.9, they received the following error when building any K2 Connect project:
Error 23 Could not load file or assembly 'SourceCode.ServiceObjectModel.Composer, Version=4.0.4.5, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkand stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName)
at System.RuntimeType.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkand stackMark)
at System.Type.GetType(String typeName, Boolean throwOnError)
at SourceCode.ProjectSystem.ProjectFile.get_ContentType()
at SourceCode.DeploymentTasks.Compiler.WorkflowCompiler.Execute()
C:Program Files (x86)MSBuildSourceCodev3.5ProjectSystem.targets 17 6 SAP_PlantMaintenance_Notification
Resolution
Using Procmon, we were able to see that Visual Studio was retrieving the value from following registry:
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeSourceCodeContentTypes.svd. The data value was set to the wrong version of the
Vsip.ServiceObjectModelComposer.Editor.EditorFactory, SourceCode.ServiceObjectModel.Composer, Version=4.0.4.5, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d
After updating the key to have the correct version, customer was able to build project successfully.
Vsip.ServiceObjectModelComposer.Editor.EditorFactory, SourceCode.ServiceObjectModel.Composer, Version=4.0.4.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d
