Viscosity on Win 7 crashes on start up.

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

Znook

Posts: 8
Joined: Sat Apr 06, 2013 1:58 am

Post by Znook » Tue Oct 22, 2013 6:54 am
Hi Guys,

Viscosity has been on my Windows 7 machine for quite a while now without any issue, always connected to my VPN service the infrequent times when I wanted it to. Great stuff.

However I noticed recently that the icon was missing from the notification area, thought I must have closed it at some point, no worries I'll just start the program again. Only when I tried to it crashes on start up. I've uninstalled it, re-installed it but the problem still exists.

These are the details from the crash window:
Code: Select all
Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	viscosity.exe
  Problem Signature 02:	1.4.6.1212
  Problem Signature 03:	524a8ccb
  Problem Signature 04:	mscorlib
  Problem Signature 05:	4.0.0.0
  Problem Signature 06:	517a19ee
  Problem Signature 07:	3771
  Problem Signature 08:	97
  Problem Signature 09:	System.Security.Security
  OS Version:	6.1.7601.2.1.0.256.4
  Locale ID:	2057
  Additional Information 1:	66a3
  Additional Information 2:	66a300f143f83c638bfa31c51631ba8a
  Additional Information 3:	bafe
  Additional Information 4:	bafe54ef8ce93737fe4b3d94b58cb2bc
Does anyone have an idea as to why it's doing this and what I can do to get Viscosity working again?

Thanks for any input.

Eric

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

Post by Eric » Tue Oct 22, 2013 3:41 pm
Hi Znook,

It looks like something is blocking Viscosity from running. The Event Viewer generally provides much more information for us to track down what is causing this. Are you able to try and run Viscosity again, then see if you can retrieve the logs from the Event Viewer (their are generally two entries for a Viscosity Crash).

http://www.sparklabs.com/support/viswin_event_viewer/

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

Znook

Posts: 8
Joined: Sat Apr 06, 2013 1:58 am

Post by Znook » Wed Oct 23, 2013 5:05 am
Hi Eric, only just got around to checking this. Thanks for the reply.

The Event Viewer shows this:
Code: Select all
Log Name:      Application
Source:        Application Error
Date:          22/10/2013 18:54:38
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SR1-VM1-W7E
Description:
Faulting application name: Viscosity.exe, version: 1.4.6.1212, time stamp: 0x524a8ccb
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
Exception code: 0xe0434352
Fault offset: 0x000000000000940d
Faulting process id: 0xcb4
Faulting application start time: 0x01cecf4fc5ee3499
Faulting application path: C:\Program Files\Viscosity\Viscosity.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 04532555-3b43-11e3-9c0e-005056b14402
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-10-22T17:54:38.000000000Z" />
    <EventRecordID>298546</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SR1-VM1-W7E</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Viscosity.exe</Data>
    <Data>1.4.6.1212</Data>
    <Data>524a8ccb</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.18229</Data>
    <Data>51fb1677</Data>
    <Data>e0434352</Data>
    <Data>000000000000940d</Data>
    <Data>cb4</Data>
    <Data>01cecf4fc5ee3499</Data>
    <Data>C:\Program Files\Viscosity\Viscosity.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>04532555-3b43-11e3-9c0e-005056b14402</Data>
  </EventData>
</Event>
And this:
Code: Select all
Log Name:      Application
Source:        .NET Runtime
Date:          22/10/2013 18:54:37
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SR1-VM1-W7E
Description:
Application: Viscosity.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Security.SecurityException
Stack:
   at Microsoft.Win32.RegistryKey.OpenSubKey(System.String, Boolean)
   at  .(Boolean, Boolean)
   at  .()
   at  . ()
   at  ..ctor()
   at  .()

Event Xml:
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='.NET Runtime'/><EventID Qualifiers='0'>1026</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2013-10-22T17:54:37.000000000Z'/><EventRecordID>298545</EventRecordID><Channel>Application</Channel><Computer>SR1-VM1-W7E</Computer><Security/></System><EventData><Data>Application: Viscosity.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Security.SecurityException
Stack:
   at Microsoft.Win32.RegistryKey.OpenSubKey(System.String, Boolean)
   at  .(Boolean, Boolean)
   at  .()
   at  . ()
   at  ..ctor()
   at  .()
</Data></EventData></Event>
I guess with the latter having an earlier timestamp that that is the reason for the crash. Maybe .NET has got corrupted and I need to reinstall it?

Robbie.

Eric

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

Post by Eric » Wed Oct 23, 2013 5:42 am
Hi Robbie,

Thanks for posting that information up. By the looks of it, something has modified your start up items in the Windows Registry (i.e. what applications start when you login to Windows) and is now preventing Viscosity from reading/writing this list. Viscosity checks to see if it is in the startup list to adjust the preference within Viscosity in case an administrator sets Viscosity to start at login while Viscosity is closed. We have just put up a new beta and included a fix to prevent this crash from occurring if you would like to give it a go, but I would highly recommend running a virus scan if you can to make sure nothing malicious is at play.

You can grab the latest beta here - http://www.sparklabs.com/forum/viewtopic.php?f=7&t=482

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

Znook

Posts: 8
Joined: Sat Apr 06, 2013 1:58 am

Post by Znook » Wed Oct 23, 2013 6:10 am
Hi Eric, thanks for the quick reply.

It's only recently I did a full virus scan using the latest Windows Defender update and also with the third-party anti-virus software I use and the results were negative. However I'll give both another run through because, as it's a virtual machine, it's not being used at the moment.

Once they complete I'll uninstall the current version of Viscosity and try the beta you've mentioned.

As an aside, strangely the non-VM Win XP machine also recently suffered from Viscosity failing to start and that also used to be rock solid up until that point. I've managed to reinstall it and this time it runs okay, but the config file of my VPN connections disappeared. It's probably me though, may have hit the delete all option when I did the uninstall/reinstall. Annoyingly I now cannot find my original back up config file so it's going to have to be a manual set-up. Oh well, things happen.

Thanks once again for your help, I'll report back with the results.

Robbie

Eric

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

Post by Eric » Wed Oct 23, 2013 6:29 am
Hi Robbie,

Just a side note, you can install the beta straight over the top of your existing installation without the need to uninstall anything.

Look forward to hearing back from you.

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

Znook

Posts: 8
Joined: Sat Apr 06, 2013 1:58 am

Post by Znook » Wed Oct 23, 2013 11:46 pm
Okay, completed scans and again nothing found.

Tried to start Viscosity - again no dice.

Installed the beta version over the top of the old version and - woot! It works! It originally balked on trying the first connect resulting in the unconnected icon showing, yet the right-click menu showed it was connected. Despite this I tried again to connect and this time the icon changed to connected and up popped the IP 'speech' bubble.

Thanks for all the help Eric in getting this sorted out.

The only thing lacking with Viscosity and it's been like this for a while now is that the connected IP shows as an internal address and not the actual IP the internet sees. Other than that little thing I'm glad to have purchased both the Mac and Win versions. It's a great little app!

Robbie
7 posts Page 1 of 1