K2 workspace error after upgrade to K2 blackpearl 4.6.1 (4.12060.1500.0)

  • 13 July 2012
  • 7 replies
  • 2 views

Badge +2

Hi,


We upgraded from K2 blackpearl 4.5 (4.10060.1.0) with Update KB001420 to K2 blackpearl 4.6.1 (4.12060.1500.0). After upgradation, we created a Process instance.When we tried to access the K2 Workspace, we got an error .The error is shown below.We are not able to access the K2 Workspace. We were not getting any errors in the previous version of K2. Can you please suggest a solution to solve this error.


Thanks,
Rajesh


 


Server Error in '/Workspace' Application.
--------------------------------------------------------------------------------


Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.


Parser Error Message: Could not load file or assembly 'SourceCode.LicenseManagementAPI, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d' or one of its dependencies. The system cannot find the file specified.


Source Error:



Line 86:         <add assembly="SourceCode.Workflow.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16A2C5AAAA1B130D" />
Line 87:         <add assembly="SourceCode.Workspace.OOBReports, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16A2C5AAAA1B130D" />
Line 88:         <add assembly="SourceCode.LicenseManagementAPI, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16A2C5AAAA1B130D" />
Line 89:         <add assembly="Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
Line 90:         <add assembly="SourceCode.Workflow.Common, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16A2C5AAAA1B130D" />
 


Source File: C:Program Files (x86)K2 blackpearlWorkspaceSiteweb.config    Line: 88


Assembly Load Trace: The following information can be helpful to determine why the assembly 'SourceCode.LicenseManagementAPI, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d' could not be loaded.



WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLMSoftwareMicrosoftFusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLMSoftwareMicrosoftFusion!EnableLog].



--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.5456; ASP.NET Version:2.0.50727.5456


7 replies

Badge +10

Is 32bit support enabled or disabled on the Workspace application pool being used to support the k2workspace site?  

Badge +2

Hi Chris,


32 bit support is enabled in the application pool which is used by the K2Workspace site.


Thanks,


Rajesh


 

Badge +10

disable it, and see if that helps.

Badge +2

Hi Chris,


I will do that.But before disabling it, i commented line88 from the Web.config file.


Now iam able to access the K2 Workspace.


Thanks,


Rajesh

Badge +10

Glad you were able to get it working. Thanks for replying back with what fixed it!

Badge +5

Hi


Same problem here after update from K2 4.5 to K2 4.6.6.


Comment out the line in web.config was not a solution for us because the error apear later when you try to use licensing in the k2 workspace.


disable 32 bit in the application pool gets a lot of other errors


my solution was to extract the correct 32bit SourceCode.LicenseManagementAPI dll from the k2 blackpearl server msi.

Badge +13

What error did you get when you turned off Enable 32-bit applications option?

I just ran into the problem with 4.6.7 and found out turning off that option (somehow it's on) fixed the issue, haven't noticed any other problems yet.

Reply