Getting Invalid Archive type while fetching the SmartObject from SmartObjectClientServer. For the GetWorkListItem facing an issue with method not resolved

Question

SourceCode.SocketService.Legacy.LegacySession.<HandlePacketAsync>d__25.MoveNext()","","","FWA-Dev-K2Five:C:\Program Files\K2\Host Server\Bin","2180715","ff2faeaf8267456a856a26f0054dac12",""
"2180771","2026-06-23 21:50:57","Error","System","2025","InternalMarshalError","SourceCode.Hosting.Server.Runtime.HostServerBroker.InternalMarshal","2025 Error Marshalling SourceCode.Workflow.Runtime.Management.WorkflowManagementHostServer.GetWorklistItems, Method could not be resolved!
at SourceCode.Hosting.Server.Runtime.HostServerBroker.InternalMarshal(String TypeName, String MethodName, Object[] ParamArray, Boolean[] NullList, Boolean UseSession, String sessionCookie, String RemoteConnectionString)","","","FWA-Dev-K2Five:C:\Program Files\K2\Host Server\Bin","2180771","6ccfa9be765345008a98b3605e7dfcef",""

Facing two issues:
1. Getting the Invalid Archive Type while executing the following code in the local development
2. Getting Method not resolved for the GetWorklistItems.

As a workaround i updated the dlls from the K2 Five into my application references as a 64 bit and running the solution in debug mode as 64 bit still facing the issue.

Please help me in resolving this issue as i got stuck not able to debug locally.

TinTex · Answer

These two errors usually indicate missmatching assembly (.dll) reference between the application and the K2 server that it is communicating with.

1. Getting the Invalid Archive Type while executing the following code in the local development
2. Getting Method not resolved for the GetWorklistItems.

Things to look out for:

if using DNS, is the DNS pointed to the correct server?
- application with 5.9 assemblies reference talking to 5.9 server?
- perhaps application with 4.7 assembly trying to communicate with 5.9 server
- or application with 5.9 assembly trying to communicate with 4.7 server
depending on the application configuration, it may look in the Global Assembly Cache (GAC) first on the server that your application is hosted; make sure the GAC doesn’t have a different version of the assembly than perhaps the bin folder

If you are still stuck, perhaps logging a support case.

Sign up

Log in with SSO

Login to the community

Log in with SSO