XRM: Failed Report Error, Failed - #lineins t_inv 56 ^

XRM: Failed Report Error, Failed - #lineins t_inv 56 ^

This problem is caused by a blank space being in the report template file. This can be resolved in the XYGATERM GUI. The steps to do so are below.

1. Open XYGATERM GUI

2. Open the afflicted report

3. Switch to the Layout Tab

4. Under Selected Columns Click the blank line

5. Click the remove button to the left of that box

6. Save the report.


If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.


    • Related Articles

    • XRM: GUI error when attempting schedule and save a report

      Check the permissions for the folder c:\Users\<user name>\AppData\Local\XYPRO\XYGATERM and its subordinate folders by executing the following command as follows from Windows shell: (Where <user name> is the Windows user that will schedule the reports ...

    • XRM failed report because there were too many audit trails

      Lower the amount of audit files that XRM tries to read. Rename or purge the audit files. It is a good idea to keep the first audit file and the last audit file for a specific date because the first and the last will have valid information. If this ...

    • XUA: Install script execution failed with error

      Without the ?run? in-front of any macro/object execution then, TACL macro execution goes through the #pmsearchlist path for looking for the object/macro. If the #pmsearchlist does not have #defaults in it, the object/macro won?t be found. We have the ...

    • XRM: System.OutOfMemoryException Error

      Possible work-arounds: Running the report for a shorter period Reducing the size of the report by splitting it into two or more separate reports. Retrieve the report and then sent it to a file, which can be put into a spreadsheet and saved. If you ...

    • XRM GUI Error: Runtime.Remoting.RemotingException: Port is Busy: All pipe instances are busy.

      Rebooting User's Computer resolved the XRM GUI "System.Runtime.Remoting.RemotingException: Port is Busy: All pipe instances are busy" Error.