Universe.log is full of the following EEP Error: no filepath and filename specified.

Document ID : KB000087153
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
In the universe.log:
########################################
| 2015-10-08 09:29:19 |ERROR|X|EEP|pid=7180.7456| o_eep_check_file_resource | Error: no filepath and filename specified.
| 2015-10-08 09:29:19 |ERROR|X|EEP|pid=7180.7456| o_eep_check_file_resource | Error: no filepath and filename specified.
| 2015-10-08 09:29:19 |ERROR|X|EEP|pid=7180.7456| o_eep_check_file_resource | Error: no filepath and filename specified.
| 2015-10-08 09:29:19 |ERROR|X|EEP|pid=7180.7456| o_eep_check_file_resource | Error: no filepath and filename specified.
| 2015-10-08 09:29:19 |ERROR|X|EEP|pid=7180.7456| o_eep_check_file_resource | Error: no filepath and filename specified.
########################################

Patch level detected:Dollar Universe 6.3.00
Product Version: Dollar.Universe 6.3.01

Description :The universe.log file is getting full due to recurring error messages about a file resource but the file resource does not exist.
Environment:
OS: Windows
Cause:
Cause type:
Configuration
Root Cause: This is caused by a data corruption of the resources data file.
Resolution:
Need to reinitialize the following data files in all areas that are enabled:
u_frrv60 -> Resources being supervised (resource events)
u_fmer60 -> Expected Resource event
u_fmev60 -> Expected Events

############

PROCEDURE:

Important : You will lose all information about resources and resource management.
So it important to do it when no resources are being used.
Please backup all the files concerned before running the reinitialization.

- Load the environment
uxsetenv

-Stop the DUAS company

-Execute the following commands for each area that is enabled (X, A, I and/or S). X-area is used in the example:

%UXEXE%\uxrazfic u_frrv60 X
%UXEXE%\uxrazfic u_fmer60 X
%UXEXE%\uxrazfic u_fmev60 X

-Perform an offline reorg:
%UXEXE%\unireorg

-Start Dollar Universe.

Fix Status: No Fix

Additional Information:
Workaround :
N/A