ViscosityService.exe service faulting

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

DonDrohman01

Posts: 2
Joined: Tue Sep 07, 2021 10:23 am

Post by DonDrohman01 » Tue Sep 07, 2021 10:56 am
This install has been trouble free for some time, and then the ViscosityService.exe started faulting under version 1.9.3.1723, so I applied the recent update to v 1.9.4.1732 to see if this changed anything. Issue still occurring.

I have excluded the entire Viscosity install directory from AV scanning.

The service is running as the Local SYSTEM account (Default setting)

Here is the most recent Application Event log entry:

Faulting application name: ViscosityService.exe, version: 1.9.4.1732, time stamp: 0x6126f7d3
Faulting module name: clr.dll, version: 4.8.4069.0, time stamp: 0x5dc6126c
Exception code: 0xc00000fd
Fault offset: 0x00000000000a3b84
Faulting process id: 0x2730
Faulting application start time: 0x01d7a2aa95229901
Faulting application path: C:\Program Files\Viscosity\ViscosityService.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: f3f45330-0eb9-11ec-b80b-00acc7375d92

After the fault, 2 Windows Error Reporting Informational events occur both identical in nature, about 9 seconds apart:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ViscosityService.exe
P2: 1.9.4.1732
P3: 6126f7d3
P4: clr.dll
P5: 4.8.4069.0
P6: 5dc6126c
P7: c00000fd
P8: 00000000000b63a9
P9:
P10:

Attached files:
C:\Windows\Temp\WERFC32.tmp.appcompat.txt
C:\Windows\Temp\WERFEC3.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WERFEC4.tmp.hdmp
C:\Windows\Temp\WERFD5.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_ViscosityService_2cd077ee567e6d391ebff07d505ec95bf58defb2_cab_0f5d2b0f

Analysis symbol:
Rechecking for solution: 0
Report Id: 42948d0f-0f69-11ec-b80b-00acc7375d92
Report Status: 4

I have the service to restart on 1st, 2nd, and subsequent failures, which it seems to do, however the following Application Warning events are logged as the service restarts. (probably just a clean up issse)

DNS Interface IPv4 Loopback Setup failed. This may cause issued with Viscosity DNS.
The object already exists.

DNS Interface IPv6 Loopback Setup failed. This may cause issued with Viscosity DNS.
The object already exists.

Environment
OS: Win7 SP1 fully patched.
.NET Framework: 4.8.03761 installed in 3/2021.
Using OpenVPN

No other relevant System Events logged in the vicinity of the faulting service (other than the expected unable to resolve names using DNS)

The Viscosity logging simply reports the state change as follows:
Sep 06 4:22:36 PM: State changed to Disconnected
Sep 06 4:22:36 PM: State changed to Disconnected
Sep 06 4:47:41 PM: State changed to Connecting**

** This event was started when i noted the VPN was disconnected, and restarted the connection. So restarting the service will not also restart the VPN session.

What else will you need to help troubleshoot?

Eric

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

Post by Eric » Tue Sep 07, 2021 12:19 pm
Hi Don,

Usually if ViscosityService is causing the crash, you should see a stacktrace in a second event in the event log under or above what you have posted. If you do see this, could you please post a copy?

If you don't see this, it means the crash isn't actually happening in Viscosity, but as the crash infers, it's happening in CLR. We have seen something like this before where another application will try to modify system files directly. My recommendation would be to uninstall .NET, reboot, and then install it again downloaded from Microsoft, download the Runtime option here - https://dotnet.microsoft.com/download/d ... work/net48
I have the service to restart on 1st, 2nd, and subsequent failures, which it seems to do, however the following Application Warning events are logged as the service restarts. (probably just a clean up issse)

DNS Interface IPv4 Loopback Setup failed. This may cause issued with Viscosity DNS.
The object already exists.

DNS Interface IPv6 Loopback Setup failed. This may cause issued with Viscosity DNS.
The object already exists.
Yes you're correct, these are just a cleanup issue if they're happening post-crash and can be ignored.

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

DonDrohman01

Posts: 2
Joined: Tue Sep 07, 2021 10:23 am

Post by DonDrohman01 » Wed Sep 08, 2021 8:57 am
If you are looking for a .NET stack trace, no, there is not one logged in the Windows event logs. I will try the .NET 4.8 reinstall

Thank you
3 posts Page 1 of 1