Fing desktop is failing multiple times a day

RobinRobin Administrator Posts: 3,079
2500 Comments 100 Answers 250 Likes 100 Awesomes
admin
Original post by @jmcging

In event viewer, the fing agent is listed as faulting multiple times daily.  My new PC is shutting down randomly, so I'm looking at logs and seeing misbehaving fing   I thought I would report what I found, share the logs and such but cannot find any such mechanism.  So I thought I'd ask here.

ERROR 2020/03/07 15:03:28.210 === fing agent 1.0.1 - www.fing.io ===
ERROR 2020/03/07 21:03:33.834 HttpSession | 127.0.0.1:60087 | Error reading data: An existing connection was forcibly closed by the remote host
ERROR 2020/03/07 21:03:43.608 === fing agent shutdown requested
ERROR 2020/03/07 21:03:43.608 TcpServer service shutdowning..
ERROR 2020/03/07 21:03:43.608 TcpServer service terminated
ERROR 2020/03/07 21:03:44.425 === fing agent graceful exit.

ERROR 2020/03/07 21:04:22.438 === fing agent 1.0.1 - www.fing.io ===
ERROR 2020/03/08 01:57:44.981 TcpServer service shutdowning..
ERROR 2020/03/08 01:57:44.981 TcpServer service terminated
ERROR 2020/03/08 03:26:25.101 === fing agent 1.0.1 - www.fing.io ===
ERROR 2020/03/08 05:26:34.682 TcpServer service shutdowning..
ERROR 2020/03/08 05:26:34.682 TcpServer service terminated

3/8/2020 7:26 AM Application Error Faulting application name: fingagent.exe, version: 1.0.1.0, time stamp: 0x5e5e4459
Faulting module name: fingagent.exe, version: 1.0.1.0, time stamp: 0x5e5e4459
Exception code: 0x40000015
Fault offset: 0x000ba7fe
Faulting process id: 0x1718
Faulting application start time: 0x01d5f4ede26c169f
Faulting application path: C:\Program Files\Fing\resources\extraResources\fingagent.exe
Faulting module path: C:\Program Files\Fing\resources\extraResources\fingagent.exe
Report Id: 79edc040-b1a8-4efe-acef-4d3894551e32
Faulting package full name: 
Faulting package-relative application ID:

3/9/2020 6:15 AM Application Error Faulting application name: fingagent.exe, version: 1.0.1.0, time stamp: 0x5e5e4459
Faulting module name: fingagent.exe, version: 1.0.1.0, time stamp: 0x5e5e4459
Exception code: 0x40000015
Fault offset: 0x000ba7fe
Faulting process id: 0x164c
Faulting application start time: 0x01d5f55cb2b2d577
Faulting application path: C:\Program Files\Fing\resources\extraResources\fingagent.exe
Faulting module path: C:\Program Files\Fing\resources\extraResources\fingagent.exe
Report Id: 5a4378a4-55b1-4d09-b220-6e3d5e0f21d0
Faulting package full name: 
Faulting package-relative application ID:
Robin (Admin at Fing)
Getting Started? Please refer to Community guidelines & Community User Guides("Helping Hand"). HAPPY POSTING!!!

Comments

  • RobinRobin Administrator Posts: 3,079
    2500 Comments 100 Answers 250 Likes 100 Awesomes
    admin
    Hi @jmcging
    Thanks for your post. Can you try to uninstall the Fing App completely and then reboot the device and then install the Fing Desktop and then check if you are still facing the issue?
    Robin (Admin at Fing)
    Getting Started? Please refer to Community guidelines & Community User Guides("Helping Hand"). HAPPY POSTING!!!
  • jmcgingjmcging Member, Beta Tester Posts: 5
    First Anniversary First Comment Photogenic
    I've had it uninstalled now since I wrote the above and no more weird reboots.  If I can find the latest version to download, I'll give it a try.
  • jmcgingjmcging Member, Beta Tester Posts: 5
    First Anniversary First Comment Photogenic
    It appears that the errors I get today are the same as before I uninstalled it.  They look the same.

    from event viewer this morning
    Faulting application name: fingagent.exe, version: 1.0.1.0, time stamp: 0x5e5e4459
    Faulting module name: fingagent.exe, version: 1.0.1.0, time stamp: 0x5e5e4459
    Exception code: 0x40000015
    Fault offset: 0x000ba7fe
    Faulting process id: 0x15a4
    Faulting application start time: 0x01d5f9bddd5c74f1
    Faulting application path: C:\Program Files\Fing\resources\extraResources\fingagent.exe
    Faulting module path: C:\Program Files\Fing\resources\extraResources\fingagent.exe
    Report Id: 764176e2-e5d6-4d43-a753-9c95e3a3c225
    Faulting package full name: 
    Faulting package-relative application ID: 

    ====Today=====
    Fault bucket 1511935250578404862, type 1
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: fingagent.exe
    P2: 1.0.1.0
    P3: 5e5e4459
    P4: fingagent.exe
    P5: 1.0.1.0
    P6: 5e5e4459
    P7: 40000015
    P8: 000ba7fe
    P9: 
    P10: 

    Attached files:
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0E8.tmp.mdmp
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB389.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB4D2.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB51E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB3A.tmp.txt

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fingagent.exe_c7da3d38ad376fc1abcdb4d8b32d222c45c33ebe_78e20804_fd6f000e-f806-4f10-b3aa-334ac7515dc0

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 764176e2-e5d6-4d43-a753-9c95e3a3c225
    Report Status: 268435456
    Hashed bucket: 1a4615b7c0d914a9f4fb79198e1df5fe
    Cab Guid: 0

    =====March 9 2020===
    Fault bucket 1511935250578404862, type 1
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: fingagent.exe
    P2: 1.0.1.0
    P3: 5e5e4459
    P4: fingagent.exe
    P5: 1.0.1.0
    P6: 5e5e4459
    P7: 40000015
    P8: 000ba7fe
    P9: 
    P10: 

    Attached files:
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D8C.tmp.mdmp
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E96.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3ED6.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3EE3.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER407B.tmp.txt

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fingagent.exe_c7da3d38ad376fc1abcdb4d8b32d222c45c33ebe_78e20804_e9814082-29d2-4437-9331-259795ed5c24

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a341ef3e-e2ca-47b2-ae7a-f182200e392e
    Report Status: 268435456
    Hashed bucket: 1a4615b7c0d914a9f4fb79198e1df5fe
    Cab Guid: 0
  • Giux_from_FingGiux_from_Fing Rome, ItalyAdministrator, Fing Team Posts: 14
    10 Comments First Anniversary Name Dropper Photogenic
    edited March 17

    Hello @jmcging thank you for all. That's super helpful. I need more info If you can reproduce it.

    Here's how to change the log level:

    STEP 1: Open a prompt window and write

    echo overlook.fingagent.logging.level=INFO > %userprofile%\AppData\Roaming\FingAgent\conf\fingagent.properties

    That will create the configuration file required to override the logging level.

    STEP 2: Reboot the system (or kill the service manually, it will be started automatically my WindowsOS)  and repeat the issue

    STEP 3: Send us via DM the log files for the fingagent (in %userprofile%\AppData\Roaming\FingAgent\log\), and let's see if we can recreate it

    Thank you!

    Giux

  • jmcgingjmcging Member, Beta Tester Posts: 5
    First Anniversary First Comment Photogenic
    I've uninstalled the product and have since done a clean windows 10 pro reinstall.  Prior to the wipe, I was seeing fing agent service reporting multiple stops, faults like above and shortly thereafter I'd get an unexpected reboot with no dump or minidump logs.  That led me to the above.  (And there has to be an easier way to report bugs and such in the product itself, you require way too much work to do reporting.) Anyway, I uninstalled the product but the fing service was still listed in the list of services, where I disabled  it.  Doing that and I had no unexpected reboots.  Then a couple of days later I reinstalled the latest version and in 24 hours had like 3 reboots.  Circumstantial, yes. But that and one other issue I had led me to the wipe and clean install.  I'm still in the process of putting the PC back to normal, and I did not install fing desktop and I'm not having any issues.  The hardware is a Ryzen 7 3700 on an Asus x570 motherboard with C: being an intel NVME SSD Gen 3 and 32 G RAM.  I'm not at all ready to play fix until I can put this back to normal and have a solid image in hand to restore it back to what I consider baseline.   So it'll be a bit before I do any of the above.
  • Giux_from_FingGiux_from_Fing Rome, ItalyAdministrator, Fing Team Posts: 14
    10 Comments First Anniversary Name Dropper Photogenic
    @jmcging Sounds good. Thank you for your update, we always try to make improvements. we will also take your suggestions into account. Let us know if the same problem occurs again once you are ready to install FingDesktop on your PC again.
    Thanks in advance.

Sign In or Register to comment.