Martin Poirier

Updating clients to 8.0.16.3799 (which appears to have just been released in the past hours) seem to have fixed the issue. Thanks a lot!

2019-12-03 11:27:39,451 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name DEBUG PlasticProto.ConnectionFromClient - conn 5. mInitialCmCallContext.UserCredentials.Mode UPWorkingMode 2019-12-03 11:27:39,451 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name DEBUG PlasticProto.ConnectionFromClient - conn 5. mInitialCmCallContext.UserCredentials.User.Data user.name 2019-12-03 11:27:39,451 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name DEBUG PlasticProto.ConnectionFromClient - conn 5. mInitialCmCallContext.Organization 2019-12-03 11:27:39,451 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name DEBUG PlasticProto.ConnectionFromClient - conn 5. mInitialCmCallContext.MachineName machine_name 2019-12-03 11:27:39,451 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name DEBUG PlasticProto.ConnectionFromClient - conn 5. mInitialCmCallContext.SecurityCtx ctxNormal 2019-12-03 11:27:39,452 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name DEBUG PlasticProto.ConnectionFromClient - conn 5. mInitialCmCallContext.CurrentTransaction 00000000-0000-0000-0000-000000000000 2019-12-03 11:27:39,452 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name DEBUG PlasticProto.ConnectionFromClient - conn 5. mInitialCmCallContext.Version 5.4.16.0 2019-12-03 11:27:39,452 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name ERROR PlasticProto.ConnectionFromClient - conn 5. Error in ProcessMethodCall for method GetWorkingMode. The method GetWorkingMode is not supported. 2019-12-03 11:27:39,453 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name DEBUG PlasticProto.ConnectionFromClient - at g2.a (PlasticPipe.PlasticProtocol.Messages.PlasticMethods A_0) [0x00025] in <558a8466dff54a8182e158d80822059f>:0 at g2.d () [0x0010f] in <558a8466dff54a8182e158d80822059f>:0 2019-12-03 11:27:39,454 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name INFO PlasticProto.ConnectionFromClient - Discarded input from unsupported method call. Bytes to discard 94 2019-12-03 11:27:39,454 NetworkThread-13 DEBUG PlasticProto.ConnectionFromClient - conn 5. ReceiveAsync 2019-12-03 11:27:39,454 W-12 5 00000000-0000-0000-0000-000000000000 user.name machine_name INFO ChannelCall - conn: 5 protocol:plasticproto sec:none recb: 119|rect: 0|sentb: 4|sendt: 1|queuedt: 0|prt: 4|th: 12|dest: 0|mt: 0|sert: 0|zip: 0|cpu: 0| 172.16.19.19|user:user.name|GetWorkingMode 2019-12-03 11:27:39,455 W-12 DEBUG WorkerThread - WorkerThread.Run: Going to GetWork. ThId: 12 This is what we see in the log after adding the debugging options.

No No, that's what generates that log on the server and a similar message on the client Client is 8.0.16.3542 Proxy is 8.0.16.3785-2.1 Server is 8.0.16.3282 I'll try the config change and report the log. That is not a version that is currently available I guess? Thanks

Hi We've recently started receiving this errors in some clients when connecting to a proxy. Strangely, other machines running the same Plastic client version can connect to the proxy without errors. In the proxy logs, it shows up as: 2019-12-02 10:18:57,241 00000000-0000-0000-0000-000000000000 <machine-name> ERROR PlasticProto.ConnectionFromClient - conn 1. Error in ProcessMethodCall for method GetWorkingMode. The method GetWorkingMode is not supported. We've been running that same proxy (no version updates) for months with the same clients. The error started showing up only this morning. Restarting the proxy process or rebooting the client machines didn't do anything. I couldn't find anything in the docs, so if anyone can help that would be great. Thanks