Sometimes I get the error "Can't Open Enterprise Logging File" what causes this and how do I fix it?

Sometimes I get the error “Can’t Open Enterprise Logging File” what causes this and how do I fix it?

Files in the logging directory are created as needed and are of the form logging_0.txt - logging_19.txt. If the logging files are “physically” on UNIX but there are “Windows” clients these files can be made with user-dependant permissions depending on the NFS package being used. As noted in the ClearTrigger documentation (section entitled “Region Logging Personality”) it is helpful to pre-create these empty files and set their permissions so they are consistently set to 666 (rw-rw-rw).

Once this is done all users will be able to write to these files.

EX. #1

An example of a logging directory that will occasionally cause this error is below:

drwxrwxrwx   2 clearadm develop      512 Dec 13 16:30 . 
drwxrwxr-x   8 clearadm cm          1024 Dec 16 11:06 .. 
-rw-rw-rw-   1 joel     develop     3881 Dec 17 14:02 logging_0.txt 
-rw-rw-rw-   1 darreng  develop     3849 Dec 17 14:02 logging_1.txt 
-rw-rw-rw-   1 clearadm develop     4066 Dec 17 14:05 logging_10.txt 
-rwxrwxr-x   1 rrojas   develop     3410 Dec 17 13:47 logging_11.txt 
-rw-rw-rw-   1 joel     develop     3803 Dec 17 14:01 logging_12.txt 
-rw-rw-rw-   1 joel     develop     3452 Dec 17 14:05 logging_13.txt 
-rw-rw-rw-   1 slewand  develop     4338 Dec 17 13:56 logging_14.txt 
-rw-rw-rw-   1 clearadm develop     3414 Dec 17 14:05 logging_15.txt 
-rw-rw-rw-   1 slewand  develop     4068 Dec 17 13:57 logging_16.txt 
-rw-rw-rw-   1 joel     develop     4088 Dec 17 14:02 logging_17.txt 
-rw-rw-rw-   1 afinnell develop     3484 Dec 17 14:01 logging_18.txt 
-rw-rw-rw-   1 joel     develop     3762 Dec 17 14:02 logging_19.txt 
-rw-rw-rw-   1 joel     develop     3647 Dec 17 13:47 logging_2.txt 
-rw-rw-rw-   1 joel     develop     3856 Dec 17 14:04 logging_3.txt 
-rw-rw-rw-   1 clearadm develop     3659 Dec 17 14:02 logging_4.txt 
-rw-rw-rw-   1 slewand  develop     4058 Dec 17 13:47 logging_5.txt 
-rw-rw-rw-   1 slewand  develop     3357 Dec 17 13:52 logging_6.txt 
-rwxrwxr-x   1 hdivoux  develop     4498 Dec 17 14:01 logging_7.txt 
-rw-rw-rw-   1 clearadm develop     3881 Dec 17 13:58 logging_8.txt 
-rw-rw-rw-   1 afinnell develop     3707 Dec 17 13:44 logging_9.txt

EX. #2

An example of a logging directory that will NOT cause this error is below:

drwxrwxrwx   2 clearadm develop      512 Dec 13 16:30 . 
drwxrwxr-x   8 clearadm cm          1024 Dec 16 11:06 .. 
-rw-rw-rw-   1 joel     develop     3881 Dec 17 14:02 logging_0.txt 
-rw-rw-rw-   1 darreng  develop     3849 Dec 17 14:02 logging_1.txt 
-rw-rw-rw-   1 clearadm develop     4066 Dec 17 14:05 logging_10.txt 
-rw-rw-rw-   1 rrojas   develop     3410 Dec 17 13:47 logging_11.txt 
-rw-rw-rw-   1 joel     develop     3803 Dec 17 14:01 logging_12.txt 
-rw-rw-rw-   1 joel     develop     3452 Dec 17 14:05 logging_13.txt 
-rw-rw-rw-   1 slewand  develop     4338 Dec 17 13:56 logging_14.txt 
-rw-rw-rw-   1 clearadm develop     3414 Dec 17 14:05 logging_15.txt 
-rw-rw-rw-   1 slewand  develop     4068 Dec 17 13:57 logging_16.txt 
-rw-rw-rw-   1 joel     develop     4088 Dec 17 14:02 logging_17.txt 
-rw-rw-rw-   1 afinnell develop     3484 Dec 17 14:01 logging_18.txt 
-rw-rw-rw-   1 joel     develop     3762 Dec 17 14:02 logging_19.txt 
-rw-rw-rw-   1 joel     develop     3647 Dec 17 13:47 logging_2.txt 
-rw-rw-rw-   1 joel     develop     3856 Dec 17 14:04 logging_3.txt 
-rw-rw-rw-   1 clearadm develop     3659 Dec 17 14:02 logging_4.txt 
-rw-rw-rw-   1 slewand  develop     4058 Dec 17 13:47 logging_5.txt 
-rw-rw-rw-   1 slewand  develop     3357 Dec 17 13:52 logging_6.txt 
-rw-rw-rw-   1 hdivoux  develop     4498 Dec 17 14:01 logging_7.txt 
-rw-rw-rw-   1 clearadm develop     3881 Dec 17 13:58 logging_8.txt 
-rw-rw-rw-   1 afinnell develop     3707 Dec 17 13:44 logging_9.txt