Viscosity stuck at creating connection, doesn't quit

Got a problem with Viscosity or need help? Ask here!

Microrobot

Posts: 13
Joined: Sun Nov 03, 2013 11:43 am

Post by Microrobot » Tue Nov 05, 2013 12:39 pm
Reconnect Disconnect issue
Nov 4 08:34:53: Notified TAP-Windows driver to set a DHCP IP/netmask of 11.122.11.121/255.255.255.252 on interface {16F8E265-430D-4373-9259-C117F0C023A5} [DHCP-serv: 11.122.11.121, lease-time: 31536000]
Nov 4 08:34:53: Successful ARP Flush on interface [51] {16F8E265-430D-4373-9259-C117F0C023A5}
Nov 4 08:34:58: Initialization Sequence Completed
Nov 04 08:34:58: State changed to Connected
Nov 4 08:35:37: [mqlbmq.com] Inactivity timeout (--ping-restart), restarting
Nov 4 08:35:37: SIGUSR1[soft,ping-restart] received, process restarting
Nov 04 08:35:37: State changed to Connecting
Last edited by Microrobot on Tue Nov 05, 2013 1:12 pm, edited 1 time in total.

Microrobot

Posts: 13
Joined: Sun Nov 03, 2013 11:43 am

Post by Microrobot » Tue Nov 05, 2013 12:46 pm
This issue seems to occur on UDP connections, TCP I haven't had any issues so far.

Microrobot

Posts: 13
Joined: Sun Nov 03, 2013 11:43 am

Post by Microrobot » Tue Nov 05, 2013 12:50 pm
I have also re-installed Viscocity about 5 times as of right now. Strangely during installation it never ever popped up about network driver install. It just went through installation and then it will have start viscocity checked marked. I hit finish and Viscocity starts it says my trial ended, I enter my license key and then I import my connection.

UDP errors:
Nov 4 08:46:34: Options error: unknown --redirect-gateway flag: def
This happens a lot.

Microrobot

Posts: 13
Joined: Sun Nov 03, 2013 11:43 am

Post by Microrobot » Tue Nov 05, 2013 1:03 pm
Update:

Sorry for constant replies. I so far am not having anymore issues, but when importing it does take quite a while it stays on creating... for a bit long, is this normal, or should it take about 10 seconds? It takes about a 1-2 minutes for just one import.

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Nov 05, 2013 2:37 pm
Hi Microrobot,

Good to gear everything is working. Adapters will take about 10 seconds to create on a moderately modern computer, plus about 10 seconds for each adapter that exists. If you are not going to use connections often, you may wish to untick the "Create VPN network adapter on import" checkbox in the Advanced tab of Preferences, and a network adapter won't be created then until you are ready to connect, this will speed up importing.

As for the rest of the issues you have faced, they all seem to be server side issues. If you haven't changed much in your configs, your VPN Provider may have been solving some issues while you were having issues. When you see issues like:

"No reply from server after sending 12 push requests"

or

"Inactivity timeout (--ping-restart), restarting"

In your log in the future, you are best contacting your VPN Provider. If you're not sure who your VPN Provider is, this will help - http://sparklabs.com/support/how_do_i_f ... _my_vpn_p/

If installation is not popping up asking to install the Viscosity driver, especially after a restart, it most likely means you have ticked the box during an earlier install to trust devices and drivers from SparkLabs.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

Microrobot

Posts: 13
Joined: Sun Nov 03, 2013 11:43 am

Post by Microrobot » Tue Nov 05, 2013 3:24 pm
Thanks so much! I did have an earlier install because I did do the trial, and I do remember hitting always trust Sparklabs. It was in fact a server issue, I tried another vpn and worked perfectly. Thank you so much!

Microrobot

Posts: 13
Joined: Sun Nov 03, 2013 11:43 am

Post by Microrobot » Tue Nov 05, 2013 3:30 pm
I also have some event reporting for you. These crashes are not too often, and I am still happy with this program, it's amazing! I just wanted to list them just in case someone else has issues.
------------------------------------------------------------------------------------------------------------
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: viscosity.exe
P2: 1.4.6.1212
P3: 524a8ccb
P4: Viscosity
P5: 1.4.6.1212
P6: 524a8ccb
P7: 2e1
P8: 5bb
P9: System.NullReferenceException
P10:

Attached files:

These files may be available here:
C:\Users\Administrator\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_viscosity.exe_50d4b0fc89cb71e7c53c50200ce7d631066a8c9_0f5e3957

Analysis symbol:
Rechecking for solution: 0
Report Id: db9e7520-45d1-11e3-aa45-d067e5534624
-----------------------------------------------------------------------------------------------------

Faulting application name: Viscosity.exe, version: 1.4.6.1212, time stamp: 0x524a8ccb
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fe958908ed
Faulting process id: 0xe90
Faulting application start time: 0x01ced9dd2a650618
Faulting application path: C:\Program Files\Viscosity\Viscosity.exe
Faulting module path: unknown
Report Id: db9e7520-45d1-11e3-aa45-d067e5534624
----------------------------------------------------------------------------------------------------------------------------------
Application: Viscosity.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
at  .()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Nov 05, 2013 3:34 pm
Hi Microrobot,

Thanks for the crash report. Are you able to let us know what you were doing at the time that this crash occurred and we will certainly look into it.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

Microrobot

Posts: 13
Joined: Sun Nov 03, 2013 11:43 am

Post by Microrobot » Tue Nov 05, 2013 3:38 pm
I would see creating... for about 2 minutes and then delete the connection, and when I hit connect for the new connection it said creating... so I deleted that one too and then Viscosity crashed.

Microrobot

Posts: 13
Joined: Sun Nov 03, 2013 11:43 am

Post by Microrobot » Tue Nov 05, 2013 3:43 pm
My computer should not be that slow to slow down the creating... process. It has an i5 2nd gen so it shouldn't be that bad. I put the all the Viscosity crashes in a folder for you.

https://www.dropbox.com/sh/4iss9xh9a1bkk9e/_ChQ2qA7tl
32 posts Page 3 of 4