Symptoms

Upgrading test server from 4.6.7 to 4.6.11. After going through the installation process we see the following errors on the K2 for Sharepoint Setup manager:

Failed to copy k2configadmin.resx from 'C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14CONFIGAdminResources' to 'App_GlobalResources' for site http://Servername::Port_]/. Exception: Could not find a part of the path 'App_GlobalResourcesk2configadmin.resx'.

Exception Could not find a part of the path 'App_GlobalResourcesk2configadmin.resx'.

Also when we attempt to navigate to the K2 for SharePoint link in central administration we get the following error:

"Could not load file or assembly 'SourceCode.SharePoint.ApplicationPages.Administration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d' or one of its dependencies. The system cannot find the file specified. "
 

Diagnoses

Customer faced similar errors after running through this same install on the Dev Servers. For that instance of the install they found a workaround for these errors by uninstalling and then reinstalling K2 for SharePoint components on the SharePoint server. Due to time constraints we attempted this same workaround on test but this did not solve the error. We checked that the DLL files that it was complaining about were in the correct areas:

SourceCode.SharePoint.ApplicationPages.Administration.dll
- C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14ISAPI (Found)
- And in the GAC. C:WindowsAssembly (NOT FOUND)

Sourcecode.SharePoint.Administration.dll
- GAC, C:WindowsAssembly (NOT FOUND)
- C:Program Files (x86)K2 blackpearlSetupConfigurationSPSolutions (Found)
- C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14ISAPI (Found)

Customer added these dll files to the GAC on the SharePoint server. Error when navigating to the link in CA changed to where it could not find the Administration.aspx page. We also saw that all of the K2 for SharePoint admin links did not work properly. It was discovered that the configuration wizard was not run after the upgrade because we could not access it via the sharepoint CA page.
 

Resolution

We ran the install of all K2 components on the various SharePoint WFE and CA. After that we went back to Central Administration server and ran the K2 for SharePoint Configuration wizard via the start menu shortcut instead of trying it from the CA page. After running through the Configuration wizard we saw no more issues with missing DLL files and all sharepoint admin links working again. During the upgrade process many of the DLL files for K2 for Sharepoint are updated, what happened here was that since the configuration wizard was not run, those links were still attempting to point to old files from 4.6.7 that no longer existed or had been updated. Running through configuration wizard configured all of the K2 Features to utilize the new 4.6.11 files/dlls.