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.

Issue

After upgrading the environment from 4.6.11 to 4.7 using the upgrade manager or using the installation package, it fails and the folllowing errors appears:

"Object reference not set to an instance of an object. 1 Object reference not set to an instance of an object"

Symptoms

Upgarde fails with "Object reference not set to an instance of an object" error appearing.

Resolution

Check the host server logs after the update has been completed. This can be seen from the following directory:

Program Files x86 > K2 Blackpearl > Hostserver > Bin

You may see the following within the logs itself:

GeneralErrorMessage","SourceCode.Endpoint.Server.EndpointServer.LoadSharedEndpoints","1 Object reference not set to an instance of an object.","","","dlx:C:\Program Files (x86)\K2 blackpearl\Host Server\Bin","23790055","94f56dba23a44d2c98005bcee11334bd",""
"23790056","2017-10-05 13:53:31","Error","System","2001","ServerStartError","SourceCode.Hosting.Server.Runtime.HostServerEngine.StartHostServer",
"2001 Error Starting Host Server: Object reference not set to an instance of an object.","system","2002:6470:6a1b::6470:6a1b","dlx:C:\Program Files (x86)\K2 blackpearl\Host Server\Bin","23790056","68205dfc136243bab6bc9e7855017831",""

If this is the case, it may be caused by the SMO endpoints. Please disable this within the Hostsever.exe.config file under the following area:

<smoServices enableEndpoints="false"...

After this has been completed, the update should complete correctly and the service should run as normal without any further errors.