Error when accessing K2 sites after upgrading the server's OS to Windows Server 2016 Standard

  • 24 February 2022
  • 0 replies
  • 176 views

Userlevel 5
Badge +20
 

Error when accessing K2 sites after upgrading the server's OS to Windows Server 2016 Standard

kbt168243

PRODUCT
K2 blackpearl 4.7
BASED ON
K2 blackpearl 4.7
TAGS
K2 Server
Upgrading
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.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Issue

After an upgrade of the K2 sever's Operating System from Windows Server 2012 R2 Standard to Windows Server 2016 Standard, all K2 sites are inaccessible. 

 

 

 

Symptoms

The error below is displayed when accessing any of the K2 sites (i.e. Designer, Management, Runtime):

Could not load file or assembly 'Microsoft.EnterpriseManagement.OperationsManager.Apm.DataCollecting.Producers.Mvc.4.0...' or one of its dependencies. The system cannot find the file specified.

Image

 

 

 

Troubleshooting Steps

This was resolved by uninstalling Microsoft Monitoring Agent which contains the assembly which causes the MVC application to return the error.

0 replies

Be the first to reply!

Reply