CLR20r3 viscosityservice.exe

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

datevat

Posts: 10
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Mon Jul 08, 2019 10:07 pm
Hello,
I did a little sweep of errors in my Event Viewer, and saw that Viscosity is frequently crashing (viscosityservice.exe).

Description
Faulting Application Path: C:\Program Files\Viscosity\ViscosityService.exe

Problem signature
Problem Event Name: CLR20r3
Problem Signature 01: ViscosityService.exe
Problem Signature 02: 1.7.16.1616
Problem Signature 03: 5cee4e8a
Problem Signature 04: System.Management
Problem Signature 05: 4.8.3752.0
Problem Signature 06: 5c7a241f
Problem Signature 07: 8a
Problem Signature 08: 51
Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
OS Version: 10.0.18362.2.0.0.256.48
Locale ID: 1033
Additional Information 1: c845
Additional Information 2: c8458de3129ac310566f5f5edb271f67
Additional Information 3: dfb9
Additional Information 4: dfb9e84192fc0b595ffdd113a23b8744

Extra information about the problem
Bucket ID: 587587e412f8fb159eefba9ee8dee772 (2229205532246206322)


Any ideas where to start troubleshooting?

datevat

Posts: 10
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Tue Jul 09, 2019 7:01 am
Update:
I seem to get the error each time I restart the computer. See screenshot.
Attachments
Anmerkung 2019-07-08 230120.jpg
Anmerkung 2019-07-08 230120.jpg (80.07 KiB) Viewed 747 times

Eric

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

Post by Eric » Tue Jul 09, 2019 8:49 am
Hi datevat,

These events usually come in a pair, is there a second event with more information being posted at roughly the same time to the Event Viewer? At a glance though it looks like the service is being forcibly terminated, for example by forcibly restarting when Windows prompts you after restarting that some applications are waiting to close.

If you're not doing this, please try repairing .NET - https://www.microsoft.com/en-au/download/details.aspx?id=30135

If the problem still occurs, you may need to reinstall .NET.

Regards,
Eric

datevat

Posts: 10
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Wed Jul 10, 2019 3:49 pm
I didn't find any other event. Source of the EventID is Windows Error Reporting.
Here is a bit more info from the Event Viewer:

Fault bucket 1374664618037830471, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: ViscosityService.exe
P2: 1.7.16.1616
P3: 5cee4e8a
P4: System.Management
P5: 4.8.3752.0
P6: 5c7a241f
P7: 8c
P8: 3f
P9: System.Management.Management
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCFD.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ViscosityService_79545da56316e6ff9ded903ab7b8bbbd73bcc744_563e58ea_d2e4658d-fdc6-4e58-8dbb-addb75796352

Analysis symbol:
Rechecking for solution: 0
Report Id: eeae1afb-ea0e-4742-88aa-5b176c468f42
Report Status: 268435552
Hashed bucket: 39b2e4c2fb21e9649313ca2fd3716347
Cab Guid: 0

I tried repairing .NET, nothing changed.

I'm not sure I'm keen to completely reinstalling .NET, since there are no other indications that there is a problem.

Eric

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

Post by Eric » Wed Jul 10, 2019 5:52 pm
Hi datevat,

System.Management is the .NET interface to querying the system about devices and hardware. Usually if the fault is within Viscosity you would see an application stacktrace in Event Viewer as well, the ones you have posted are from the System itself. I understand that you may not be seeing other problems, however, very few pieces of software would be interfacing with your system like Viscosity does.

We used to see System.Management errors a lot before we forced Viscosity to use .Net 4.5.2 as there was a bug in earlier versions of .NET that was generally fixed by a reinstall. This is the first time we've actually seen this error crop up since we updated Viscosity to the newer version of .NET several releases ago now.

I'm afraid all we can recommend is a reinstall of .NET. This should have no impact on your system other than taking a little while to complete - https://dotnet.microsoft.com/download/dotnet-framework/net48

A device driver not exiting gracefully when you shut down your PC could also be causing this, we have seen hardware wifi switches on laptop take out multiple .NET applications in the past when flicked for example. The hardware errors in your log may also be related.

We will monitor for further reports of this happening. The good news though is this is most likely not effecting Viscosity as it should be recovering itself on startup again from ungraceful shutdowns, even though the situation is not ideal.

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

datevat

Posts: 10
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Thu Jul 11, 2019 9:40 pm
OK, I get it. I'll try to completely remove and reinstall .NET and will report back in a week or so.

KStroSec

Posts: 2
Joined: Wed Jul 17, 2019 2:23 am

Post by KStroSec » Sat Jul 27, 2019 2:15 am
Hello,

We are having the same issue, on nearly every computer in our environment.

However, it does not seem to be causing any problems with the user actually staying connected to the VPN.

Eric

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

Post by Eric » Mon Jul 29, 2019 12:04 pm
Hi KStroSec,

Are you able to post a copy of the events in the Event Viewer you are seeing please so we can take a look? Are these events also appearing at the time of shutdown or at a different time?

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

KStroSec

Posts: 2
Joined: Wed Jul 17, 2019 2:23 am

Post by KStroSec » Thu Aug 01, 2019 4:55 am
It happens through out the day

here are two examples from event log

Fault bucket 1338226281304151579, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: ViscosityService.exe
P2: 1.7.16.1616
P3: 5cee4e8a
P4: System.Management
P5: 4.7.3056.0
P6: 5a8e5a11
P7: 8c
P8: 3f
P9: System.Management.Management
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER440D.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ViscosityService_1ba635db7c553aa596ebd61e55f283204e56764_563e58ea_3bd0edff

Analysis symbol:
Rechecking for solution: 0
Report Id: 5dbecff8-199f-409f-b37e-fa3ec441417e
Report Status: 268435556
Hashed bucket: 71f635e954eb5994129255b66e39d61b
Cab Guid: 0
-----------------------------------------------------------------------------
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: ViscosityService.exe
P2: 1.7.16.1616
P3: 5cee4e8a
P4: System.Management
P5: 4.7.3056.0
P6: 5a8e5a11
P7: 8c
P8: 3f
P9: System.Management.Management
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER440D.tmp.WERInternalMetadata.xml

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

Analysis symbol:
Rechecking for solution: 0
Report Id: 5dbecff8-199f-409f-b37e-fa3ec441417e
Report Status: 100
Hashed bucket:
Cab Guid: 0

Eric

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

Post by Eric » Thu Aug 01, 2019 12:18 pm
Hi KStroSec,

Could you please download the offline runtime .NET installer from here and run it, selecting to repair/reinstall if prompted - https://dotnet.microsoft.com/download/dotnet-framework/net48

It looks like you are using an older version of Windows or .NET, if you are not comfortable using the latest version of .NET, please scroll down to version 4.7.2 instead.

Once reinstalled, please reboot the machine and let us know if the problem reoccurs. As mentioned earlier in this thread, Viscosity is crashing outside it's own code which isn't giving us much to go on, this generally leads to the problem occurring within the system rather than the application. If you can find any correlation between the time of the crash and what you are doing on the machine, for example closing the lid, opening another program, that may help us to investigate.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
10 posts Page 1 of 1