Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

Error: aplication nlnhook.exe, version 11.0.6100.463, modules nnotes.dll, version 8.5.13.10143, adress 0x0018a23e.

  • 1.  Error: aplication nlnhook.exe, version 11.0.6100.463, modules nnotes.dll, version 8.5.13.10143, adress 0x0018a23e.

    Posted Jan 21, 2011 04:53 AM

    In OS WinXP SP3 Symantecs Endpoint Protection 11.0.6100.463 and Lotus Notes 8.5.1 are installed
    Each time at OS loading, under the user who does not have the rights of the Administrator, in system log appears the message: an application Error nlnhook.exe, version 11.0.6100.463, the unit nnotes.dll, version 8.5.13.10143, 0x0018a23e address.
    In the user
    Documents And Settings\Local Settings\Application Data\Lotus\Notes\Data\Notes.ini file there is a line
    NSF_HOOKS=NLNVP.DLL
    WinXp SP3 it is installed on VMWare View 4.5.0 build-293049



  • 2.  RE: Error: aplication nlnhook.exe, version 11.0.6100.463, modules nnotes.dll, version 8.5.13.10143, adress 0x0018a23e.

    Posted Jan 21, 2011 07:55 AM

    Firstly, I would suggest upgrading to the latest version of SEP, RU6 MP2 (11.0.6200.754)

    If that does not fix it or you can't upgrade at this time, try disabling tamper protection:

    To do this on the client:

    Change Settings >> To the right of Client Management click the Configure Settings button >> Tamper Protection tab >> uncheck the box for "Protect Symantec security software from being tampered with or shutdown"

    I wouldn't suggest disabling tamper protection permanently, but I had a similar issues with Notes 8.5.1 FP1 and this worked. Ultimately, we upgraded to Notes 8.5.1. FP3 and it went away even with tamper protection enabled.



  • 3.  RE: Error: aplication nlnhook.exe, version 11.0.6100.463, modules nnotes.dll, version 8.5.13.10143, adress 0x0018a23e.

    Posted Jan 25, 2011 06:43 AM

    Greetings!
    Unfortunately, update to the last version SEP 11.0.6200.754 hasn't helped. The version of client Lotus Notes 8.5.1. FP3.
    We have changed a setup package (have deleted the module of protection Lotus Notes) - the error has disappeared.