This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
The K2 Blackpearl Server Service terminated unexpectedly.
The following error appears in the K2 Server Console Mode:
"Error Invoking 'StartHostserver' : SourceCode.HostServerLib : Method 'SuspendSession is type 'Sourcecode.Hosting.Server.Runtime.HostSessionManager' from assembly 'Sourcecode.HostserverLib , Version=220.127.116.11,Culture=neutral,PublicKeyToken=16a2c5aaaa1b130d' does not have an implementation."
If you perform a K2 Product Repair, the Windows server will restart at the "K2 Server" point on the repair process.
The K2 Server
will not start up in Console mode
or Service mode
which causes system applications to be inaccessible.
Please complete the following steps:
Validate that the version of the SourceCode.HostClientAPI.dll in the Global Assembly cache is correct as per a K2 4.7 default installation.
You will note that the version of the dll in the K2 blackpearl\Hostserver\bin is related to a 4.6.11 installation and a bit outdated. (A good indication is the Date Modified).
The image below shows an incorrect DLL that will be presented in the K2 blackpearl\Hostserver\bin:
Please see below a correct DLL that needs to be copied over to the K2 blackpearl\Hostserver\bin:
Replace the SourceCode.HostClientAPI.dll from the Global assembly cache with the one in the K2 blackpearl\Hostserver\bin directory.
You will be able to Start the K2 Server in Console Mode, but will be presented with an invalid archive type error which is caused by invalid versions of the K2 dlls on the environment.
To get past this, perform a K2 Repair on both K2 Blackpearl and SmartForms from the K2 installation media.
Please note that if a K2 repair is completed any Fix Packs or Cumulative Updates that was applied will need to be reapplied as the repair will remove these.
If you still experience this issue, please raise a K2 Support Ticket so further steps can be taken.