Errors in log after installing 12.20

Hi over a while!
Windows 7 Pro SP1, F-Secure Client Security 12.20 (installed over 12.00). On some devices app-events log is showing ...
---
Faulting application name: FNRB32.EXE, version: 10.10.133.0, time stamp: 0x57f62cea
Faulting module name: FNRB32.EXE, version: 10.10.133.0, time stamp: 0x57f62cea
Exception code: 0xc0000005
Fault offset: 0x00064de6
Faulting process id: 0x1264
Faulting application start time: 0x01d257599c30b388
Faulting application path: C:\Program Files (x86)\F-Secure\Common\FNRB32.EXE
Faulting module path: C:\Program Files (x86)\F-Secure\Common\FNRB32.EXE
Report Id: d9e0826d-c34c-11e6-be1a-fcaa14659d2d
---
... and in sys-events ...
"F-Secure Network Request Broker service terminated unexpectedly" and afterwards "The F-Secure Network Request Broker service entered the running state.". This seems to happen when device is (re)started.
Also, not sure connected with above, could be totally different story (exact times not connected to above problem and devices vary), but F-Secure management console started after upgrade (12.00 to 12.20) distribute occasionally (but still very often to annoy local admin) warnings a'la "Message: F-Secure Management Agent has detected new communication settings that have failed to work immediately and switched back to the last known good settings. This may be caused by a temporary loss of connection to the F-Secure Policy Manager Server or by a set of invalid communication settings.".
Any ideas?
More thanks, Alar.

Comments

  • VadVad Posts: 1,050 F-Secure Employee

    Hello Alfa,

     

    This is a known issue in CS 12.20. It is fixed in upcoming CS 12.30 release.

    Please, contact support for a hotfix for CS 12.20 version.

     

    Best regards,

    Vad

    etomcat
  • AlfaAlfa Posts: 16

    Hi and thanks!
    If I correctly understand – after applying this HF to management server we must deploy msi's once again to update ws's?
    Have You any ideas when is 12.30 due?
    More thanks, Alar.

  • VadVad Posts: 1,050 F-Secure Employee

    To install a hotfix from Policy Manager Console "Installation" tab, import it to PMC, select affected sub-domain or host, then use "Hotfix" action or "Install" button, and distribute polisies.

     

    CS 12.30 RC is planned for this week. RTM will be in January.

     

    Best regards,

    Vad

  • AlfaAlfa Posts: 16

    Hi again and thanks again!
    Ok, well, as we install F-S for new devices (added to domain) using msi, can/should we update msi as well? Or this HF is applicable to ws's only via PMC?
    More thanks, Alar.

  • AlfaAlfa Posts: 16

    Hi again!
    Well, I got this HF. It seems to be just about replacement one file on workstation (ws). Well, it can be done in many ways, supposedly, but is there a way to apply this HF unattended  using fshotfix.exe on ws? Would be nice, I must say.
    More thanks, Alar.

  • AlfaAlfa Posts: 16

    Hi!
    Anyway. This HF fixed fnrb errors, but in F-S log and PMC still appear errors a'la ...
    2016-12-23 09:37:46+02:00 <computer> SYSTEM F-Secure Management Agent 1.3.6.1.4.1.2213.11.1.14
     F-Secure Management Agent has detected new communication settings that have failed to work immediately and switched back to the last known good settings. This may be caused by a temporary loss of connection to the F-Secure Policy Manager Server or by a set of invalid communication settings.
    Any ideas about those?
    More thanks, Alar.

  • VadVad Posts: 1,050 F-Secure Employee

    Hello Alfa,

     

    The hotfix can be installed locally on the client by double-clicking on fsfix hotfix file.

     

    Regarding errors in log. It could be a real loss of connection or some bug. We need more details for analysis. Please, contact support.

     

    Best regards,

    Vad

  • AlfaAlfa Posts: 16

    Hi and thanks!
    I thought using for HF deployment not double clicking but rather some more automatic way for mass-deployment (wo using  PMC). =)
    I contacted support, they suggested to give a try for 12.30 release candidate, not sure this is good idea, though.
    More thanks, Alar.

This discussion has been closed.