XRM: Scheduled report fails with XRMMETAP being used by another process

XRM: Scheduled report fails with XRMMETAP being used by another process

Schedule reports to run at least 5 minutes apart, e.g.  times separated by 5 minutes between each report start to avoid the file clash.

If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.
 





    • Related Articles

    • XRM: Scheduled Reports Fails to Run

      1.Check XRM for the Task's Name, it can be found by Viewing the Task Log for the malfunctioning task and locating the 'Starting Scheduled Report' line. The task will be in the format XRM.<systemname>.<username>.<Fully.Qualified.Work.Directory> 2. ...

    • XRM: Scheduled Reports Fail - DPAPI unable to decrypt data

      Solution: 1. Confirm the error details from the progress.txt file in the XYGATERM folder (Windows 10). 2. After confirming error, schedule a new report. 3. Once scheduled, modify the task properties as listed below. a. Open Windows Task Scheduler b. ...

    • 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 ...

    • XS1: Monitor fails to run as scheduled - Collection failed XTR: open \node.$vol.subvolume.trconf error 12 \node

      When a monitor fails to run as scheduled, the activities tab should be checked for error details. If a monitor fails with an error after initially being scheduled, subsequent monitors may fail to run. The error should be addressed and then the ...

    • XOS: Why am I seeing \UNKNOWN in the XOS Audit Report?

      Below are two possible reasons "\unknown" is seen in a XOS Audit Report for node name: A. When the EXPLICIT_NODES is OFF and you try to execute a FUP program on \one node to purge a file on another you see \UNKNOWN on the SUBJECT-SYSTEM field as ...