FileNet Image Services: The TM_daemon process reports a 202,4,17 error - FNL_lock: Process record PID (0) does not match the real PID.
After applying FileNet Image Services 4.1.2 Fix Pack 6 and restarting the software, the following error might be reported in the error log on a server running the UNIX operating system.
2013/03/20 11:07:48.078 202,4,17 <fnsw> TM_daemon (2023642.1.0 0x1ee0da.1) ... [CRITICAL]
FNL_lock: Process record PID (0) does not match the real PID (2023642).
This error message can be ignored. The error is most likely due to a fork without exec. This error has no impact and does not cause a performance issue.
Resolving the problem
The problem was introduced in FileNet Image Services 4.1.2 Fix Pack 6 and is resolved in Fix Pack 7.
FileNet Image Services Fix Pack 7 is currently scheduled to be released in May 2013. Until the Fix Pack is released, the problem can be resolved by downloading and applying from IBM Fix Central, the Interim Fix for APAR PJ41113.
More support for:
FileNet Image Services
Software version: 4.2
Operating system(s): AIX
Software edition: All Editions
Reference #: 1632425
Modified date: 07 December 2016
Translate this page: