Skip to main content

This started happening last week for workflows that I try to build out of Visual Studio:

 

Done building project "CSWinWF-21def8cc231f4db6a2fcd2c99fca4832.csproj".
Build succeeded.
Done executing task "WorkflowCompiler" -- FAILED.
Done building target "ProjectCompilation" in project "TestVS.k2proj" -- FAILED.

 

and finish up with this:

 

Build succeeded.

Time Elapsed 00:00:01.55
========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ==========

 

and they are unable to be deployed.  Nothing in the Error List though.

 

Even creating a new workflow with just one DataEvent activity has the same result. Don't recall anything changing since the last successful build, apart from Microsoft patching.

 

Visual Studio Professional 2013, K2 4.7 with August 2017 CU FP4, SharePoint 2013

Please check the following registry key:


https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed


 


Does it indicate that perhaps .NET Framework 4.7.1 was recently installed along with the latest Windows Updates?  If so, .NET Framework 4.7.1 is known to cause issue with K2 version 4.7 and a patch is available.


 


The application of the November CU + FP5 or later:


https://help.k2.com/kb002132

Had a look at this yesterday.  Release is 394271, which equates to .NET Framework 4.6.1.

 

I've attached the complete diagnostic build output if it's of any help.

This was located in the logs, however not sure if it is related yet:


 


Could not resolve this reference. Could not locate the assembly "SourceCode.HostServerInterfaces, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.


 


Is this purely a client tools machine?  If so, perhaps we can just try a Repair of K2 blackpearl, a Repair of K2 Smartforms, and re-application of the CU/FP on this machine.


 


I assume the same issue is not experienced on another client tool machine connecting to the same server or from the server (if visual studio is somehow installed there).

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings