Skip to content
Viscosity 1.4.5 crashes while editing connection
Got a problem with Viscosity or need help? Ask here!
Hi,
we have Viscosity client installed with version 1.4.5(1203) on Win 7 Desktop 64 bit. If we put the client certificates in:
C:\Program Files\Viscosity
and setup the config file:
%APPDATA%\Roaming\Viscosity\OpenVPN\1
to use them:
...
ca "C:\\Program Files\\Viscosity\\ca.pem"
cert "C:\\Program Files\\Viscosity\\client.crt"
key "C:\\Program Files\\Viscosity\\client.key"
...
and distribute automatically all these files to the clients, the client machines are able to connect to the VPN server but if some client tries to edit the connection the program fails with the following error:
we have Viscosity client installed with version 1.4.5(1203) on Win 7 Desktop 64 bit. If we put the client certificates in:
C:\Program Files\Viscosity
and setup the config file:
%APPDATA%\Roaming\Viscosity\OpenVPN\1
to use them:
...
ca "C:\\Program Files\\Viscosity\\ca.pem"
cert "C:\\Program Files\\Viscosity\\client.crt"
key "C:\\Program Files\\Viscosity\\client.key"
...
and distribute automatically all these files to the clients, the client machines are able to connect to the VPN server but if some client tries to edit the connection the program fails with the following error:
Code: Select all
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: Illegal characters in path.
at System.IO.Path.CheckInvalidPathChars(String path)
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
at System.IO.FileInfo..ctor(String fileName)
at .(String , Int32 , )
at . (Object , EventArgs )
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1008 (RTMGDR.030319-1000)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
Viscosity
Assembly Version: 1.0.0.0
Win32 Version: 1.4.5.1203
CodeBase: file:///C:/Program%20Files/Viscosity/Viscosity.exe
----------------------------------------
System.ServiceProcess
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1001 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1002 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1001 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1015 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1015 (RTMGDR.030319-1000)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Security
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1004 (RTMGDR.030319-1000)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Security/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Security.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Hi vpeshov,
Viscosity is designed for the certificates to be stored with the connection profile, I'm afraid I'm unaware of anyone using Viscosity like this. Saying that though, there could be another option that is causing the crash that Viscosity is not handling correctly that could be causing the issue.
To get to the bottom of this, we would highly appreciate it if you could send us a copy of your config (certificates aren't required), so we can have a look what is going on. If you wish to keep your configuration off the public internert, please feel free to email it to us at https://www.sparklabs.com/support/#contact.
Viscosity also allows connections to be pre-bundled with connections, you may wish to have a look at this too as it may simplify your deployment:
http://www.sparklabs.com/support/viswin_bundle_viscosity/
If you are simply looking to keep the certificates out of a users appdata, you can set Viscosity to store connections in a different location, please email us if you would like more information about this.
Regards,
Eric
Viscosity is designed for the certificates to be stored with the connection profile, I'm afraid I'm unaware of anyone using Viscosity like this. Saying that though, there could be another option that is causing the crash that Viscosity is not handling correctly that could be causing the issue.
To get to the bottom of this, we would highly appreciate it if you could send us a copy of your config (certificates aren't required), so we can have a look what is going on. If you wish to keep your configuration off the public internert, please feel free to email it to us at https://www.sparklabs.com/support/#contact.
Viscosity also allows connections to be pre-bundled with connections, you may wish to have a look at this too as it may simplify your deployment:
http://www.sparklabs.com/support/viswin_bundle_viscosity/
If you are simply looking to keep the certificates out of a users appdata, you can set Viscosity to store connections in a different location, please email us if you would like more information about this.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
2 posts
Page 1 of 1