PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 01/30/2018 6:28 PM by  Kwane McNeal
Huge error-rpt files created when report errors
 8 Replies
Sort:
You are not authorized to post a reply.
Page 1 of 212 > >>
Author Messages
Kert490
Programmer Analyst
Private
Basic Member
(28 points)
Basic Member
Posts:12


Send Message:

--
01/15/2018 12:40 PM
    We have had several instances where our Lawson drive space was suddenly eaten up with no warnings, going from under 50% to over 95% and causing failures. We have found that the space is being taken up by error files in the users print directory. There are 2 files created: error-rpt (around 40 GB) and error_rpt.dtl (around 5 GB). These are much larger than the normal files that are created when a report errors.

    We can go through and delete the files and restore the space, but we would like to prevent the files from being created to avoid issues with having the drive fill up while people are using the system.

    Does anyone know why these huge error files are being created?

    Is there any way to prevent their creation, since they have no particular use and are harmful to the system?

    Tags: Reports
    Kwane McNeal
    Private
    Private
    Veteran Member
    (1299 points)
    Veteran Member
    Posts:433


    Send Message:

    --
    01/15/2018 12:45 PM
    Make sure none of the batch jobs and invoked programs are compiled in trace or debug mode.

    Look in LAWDIR/product-line/obj for .idy and .int files, as those are usually the programs that have been compiled in trace or debug mode.

    Other than that, we would need to know more about the specific job and perhaps a snippet of the error-rpt file to know what’s happening
    (REMEMBER to not post a snippet containing sensitive data)
    Kert490
    Programmer Analyst
    Private
    Basic Member
    (28 points)
    Basic Member
    Posts:12


    Send Message:

    --
    01/16/2018 2:01 PM
    We don't have any examples of the giant error-rpt files, since we delete them when it happens, but I will post it if it happens again before it is resolved.

    I checked in our directory E:\INFOR10X\law\GHSE\obj for the .idy and .int files, but didn't find any. It is mostly just .gnt files which look to be compiled reports.

    Is there another place we can see if the reports were compiled in debug/trace mode?
    Kwane McNeal
    Private
    Private
    Veteran Member
    (1299 points)
    Veteran Member
    Posts:433


    Send Message:

    --
    01/16/2018 2:29 PM
    If you have no .idy or .int, then nothing is compiled in debug mode. Without knowing which programs are causing the issue or any snippets of the reports themselves, there’s nothing more I really could tell you.
    John Henley
    Private
    Private
    Senior Member
    (9692 points)
    Senior Member
    Posts:3248


    Send Message:

    --
    01/16/2018 5:51 PM
    This sounds like it's an error report generated by a particular batch job/report, not a job log file.
    Do you only see it on particular jobs/tokens, and if so, which one(s)?
    Thanks for using the LawsonGuru.com forums!
    John
    You are not authorized to post a reply.
    Page 1 of 212 > >>