Page 1 of 1

Cannot connect to VPN after 1.8.4 update

Posted: Tue Jan 14, 2020 3:54 am
by ToddlerTN
Running Viscosity 1.8.4 (1651) (32-bit) on Windows 10 1909 32-bit.

Was prompted to update this morning, installed the new version, now cannot connect to my VPN. You can see from the log that it runs a constant connect/disconnect loop every second or two.

Have rebooted to no avail. Still have version 1.8.3 installed on another W10 1909 system and that box can connect without issue.

Connection log:

Jan 13 10:42:46 AM: State changed to Connecting
Jan 13 10:42:46 AM: Viscosity Windows 1.8.4 (1651)
Jan 13 10:42:46 AM: Running on Microsoft Windows 10 Pro 32 bit
Jan 13 10:42:46 AM: Running on .NET Framework Version 4.8.03752.528040
Jan 13 10:42:46 AM: Bringing up interface...
Jan 13 10:42:46 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:42:46 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:42:46 AM: at ql0DWC5AFVg8sMkhnhkGwLbJWKr.wdoBD2KVIBogaISQLxb5mvkep0y()
Jan 13 10:42:46 AM: at hMkUWPyuLCMQCB1OBRAIijpFRpO.15wUQolaeoGEzCYUKLGfYQ6VKiA()
Jan 13 10:42:46 AM: at ViscosityService.ViscosityDaemon.startOpenVPN(String uniqueID, String openVPNVer, v2DcSXrBGN1TESgqYvdpeq4VLf1 config, StreamReader sr, StreamWriter sw, NamedPipeServerStream pipeServer)
Jan 13 10:42:46 AM: --- End of inner exception stack trace ---
Jan 13 10:42:46 AM: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
Jan 13 10:42:46 AM: at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
Jan 13 10:42:46 AM: at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
Jan 13 10:42:46 AM: at ShUeRFfnCy6rhRn1dsNFY6hq6xb.r809yvoR3Wcbxpgv09Jxh9EPmqD(Object )
Jan 13 10:42:47 AM: State changed to Disconnected
Jan 13 10:42:47 AM: Connection will be reconnected when reachable.
Jan 13 10:42:47 AM: Resolving address: "atl-a02.wlvpn.com"
Jan 13 10:42:48 AM: Reconnecting connection as it is now reachable
Jan 13 10:42:48 AM: State changed to Connecting
Jan 13 10:42:48 AM: Viscosity Windows 1.8.4 (1651)
Jan 13 10:42:50 AM: Running on Microsoft Windows 10 Pro 32 bit
Jan 13 10:42:50 AM: Running on .NET Framework Version 4.8.03752.528040
Jan 13 10:42:50 AM: Bringing up interface...
Jan 13 10:42:50 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:42:50 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:42:50 AM: at ql0DWC5AFVg8sMkhnhkGwLbJWKr.wdoBD2KVIBogaISQLxb5mvkep0y()
Jan 13 10:42:50 AM: at hMkUWPyuLCMQCB1OBRAIijpFRpO.15wUQolaeoGEzCYUKLGfYQ6VKiA()
Jan 13 10:42:50 AM: at ViscosityService.ViscosityDaemon.startOpenVPN(String uniqueID, String openVPNVer, v2DcSXrBGN1TESgqYvdpeq4VLf1 config, StreamReader sr, StreamWriter sw, NamedPipeServerStream pipeServer)
Jan 13 10:42:50 AM: --- End of inner exception stack trace ---
Jan 13 10:42:50 AM: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
Jan 13 10:42:50 AM: at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
Jan 13 10:42:50 AM: at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
Jan 13 10:42:50 AM: at ShUeRFfnCy6rhRn1dsNFY6hq6xb.r809yvoR3Wcbxpgv09Jxh9EPmqD(Object )
Jan 13 10:42:51 AM: State changed to Disconnected
Jan 13 10:42:51 AM: Connection will be reconnected when reachable.
Jan 13 10:42:52 AM: Resolving address: "atl-a02.wlvpn.com"
Jan 13 10:42:52 AM: Reconnecting connection as it is now reachable
Jan 13 10:42:52 AM: State changed to Connecting
Jan 13 10:42:52 AM: Viscosity Windows 1.8.4 (1651)
Jan 13 10:42:54 AM: Running on Microsoft Windows 10 Pro 32 bit
Jan 13 10:42:54 AM: Running on .NET Framework Version 4.8.03752.528040
Jan 13 10:42:54 AM: Bringing up interface...
Jan 13 10:42:54 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:42:54 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:42:54 AM: at ql0DWC5AFVg8sMkhnhkGwLbJWKr.wdoBD2KVIBogaISQLxb5mvkep0y()
Jan 13 10:42:54 AM: at hMkUWPyuLCMQCB1OBRAIijpFRpO.15wUQolaeoGEzCYUKLGfYQ6VKiA()
Jan 13 10:42:54 AM: at ViscosityService.ViscosityDaemon.startOpenVPN(String uniqueID, String openVPNVer, v2DcSXrBGN1TESgqYvdpeq4VLf1 config, StreamReader sr, StreamWriter sw, NamedPipeServerStream pipeServer)
Jan 13 10:42:54 AM: --- End of inner exception stack trace ---
Jan 13 10:42:54 AM: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
Jan 13 10:42:54 AM: at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
Jan 13 10:42:54 AM: at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
Jan 13 10:42:54 AM: at ShUeRFfnCy6rhRn1dsNFY6hq6xb.r809yvoR3Wcbxpgv09Jxh9EPmqD(Object )
Jan 13 10:42:55 AM: State changed to Disconnected
Jan 13 10:42:55 AM: Connection will be reconnected when reachable.
Jan 13 10:42:56 AM: Resolving address: "atl-a02.wlvpn.com"
Jan 13 10:42:56 AM: Reconnecting connection as it is now reachable
Jan 13 10:42:56 AM: State changed to Connecting
Jan 13 10:42:56 AM: Viscosity Windows 1.8.4 (1651)
Jan 13 10:42:58 AM: Running on Microsoft Windows 10 Pro 32 bit
Jan 13 10:42:58 AM: Running on .NET Framework Version 4.8.03752.528040
Jan 13 10:42:59 AM: Bringing up interface...
Jan 13 10:42:59 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:42:59 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:42:59 AM: at ql0DWC5AFVg8sMkhnhkGwLbJWKr.wdoBD2KVIBogaISQLxb5mvkep0y()
Jan 13 10:42:59 AM: at hMkUWPyuLCMQCB1OBRAIijpFRpO.15wUQolaeoGEzCYUKLGfYQ6VKiA()
Jan 13 10:42:59 AM: at ViscosityService.ViscosityDaemon.startOpenVPN(String uniqueID, String openVPNVer, v2DcSXrBGN1TESgqYvdpeq4VLf1 config, StreamReader sr, StreamWriter sw, NamedPipeServerStream pipeServer)
Jan 13 10:42:59 AM: --- End of inner exception stack trace ---
Jan 13 10:42:59 AM: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
Jan 13 10:42:59 AM: at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
Jan 13 10:42:59 AM: at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
Jan 13 10:42:59 AM: at ShUeRFfnCy6rhRn1dsNFY6hq6xb.r809yvoR3Wcbxpgv09Jxh9EPmqD(Object )
Jan 13 10:42:59 AM: State changed to Disconnected
Jan 13 10:42:59 AM: Connection will be reconnected when reachable.
Jan 13 10:43:00 AM: Resolving address: "atl-a02.wlvpn.com"
Jan 13 10:43:00 AM: Reconnecting connection as it is now reachable
Jan 13 10:43:00 AM: State changed to Connecting
Jan 13 10:43:00 AM: Viscosity Windows 1.8.4 (1651)
Jan 13 10:43:03 AM: Running on Microsoft Windows 10 Pro 32 bit
Jan 13 10:43:03 AM: Running on .NET Framework Version 4.8.03752.528040
Jan 13 10:43:03 AM: Bringing up interface...
Jan 13 10:43:03 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:43:03 AM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The parameter is incorrect
Jan 13 10:43:03 AM: at ql0DWC5AFVg8sMkhnhkGwLbJWKr.wdoBD2KVIBogaISQLxb5mvkep0y()
Jan 13 10:43:03 AM: at hMkUWPyuLCMQCB1OBRAIijpFRpO.15wUQolaeoGEzCYUKLGfYQ6VKiA()
Jan 13 10:43:03 AM: at ViscosityService.ViscosityDaemon.startOpenVPN(String uniqueID, String openVPNVer, v2DcSXrBGN1TESgqYvdpeq4VLf1 config, StreamReader sr, StreamWriter sw, NamedPipeServerStream pipeServer)
Jan 13 10:43:03 AM: --- End of inner exception stack trace ---
Jan 13 10:43:03 AM: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
Jan 13 10:43:03 AM: at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
Jan 13 10:43:03 AM: at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
Jan 13 10:43:03 AM: at ShUeRFfnCy6rhRn1dsNFY6hq6xb.r809yvoR3Wcbxpgv09Jxh9EPmqD(Object )
Jan 13 10:43:03 AM: State changed to Disconnected
Jan 13 10:43:03 AM: Connection will be reconnected when reachable.

Re: Cannot connect to VPN after 1.8.4 update

Posted: Tue Jan 14, 2020 4:30 am
by ToddlerTN
Replying to add that reinstalling 1.8.3 immediately got me working. Reinstalling 1.8.4 broke things again, so I've had to roll back once more to 1.8.3 for the time being.

Re: Cannot connect to VPN after 1.8.4 update

Posted: Tue Jan 14, 2020 10:11 am
by Eric
Hi ToddlerTN,

Thanks very much for the report, we will investigate.

Regards,
Eric

Re: Cannot connect to VPN after 1.8.4 update

Posted: Tue Jan 14, 2020 11:38 am
by Eric
Hi ToddlerTN,

We've identified a regression issue on 32-bit installations. Viscosity 1.8.4 Build 1652 is now available via auto-update that will resolve this issue.

Thank you very much for reporting this once again!

Regards,
Eric