We just started getting this error occasionally in the past week. We have
seen three instances, from different users with different reports, where
they get a pop-up that says:
Exception caught in: Epicor.Mfg.BO.ReportMonitor
Error Detail
============
Message: Invalid path "\\TUALATIN\EpicorData/Reports/tgleason/Packing Slip
Print02655.XML".
Type: Error
Program: bo/ReportMonitor/ReportMonitor.p
Method: loadData
Table:
Row:
Field:
When we look, the referenced file does not exist. Closing the dialog and
printing again works.
Has anyone seen anything like this?
--
*Tanya Denison* | IT Manager | NRS, Inc.
*2009 S. Main Street, Moscow, ID 83843*
*tdenison@...* <83843tdenison@...>* |
**www.nrsweb.com*<http://www.nrsweb.com>
*c: 208.301.0599 | p: 208.883.7834 Ext 277 | f: 208.882.1744*
[Non-text portions of this message have been removed]
seen three instances, from different users with different reports, where
they get a pop-up that says:
Exception caught in: Epicor.Mfg.BO.ReportMonitor
Error Detail
============
Message: Invalid path "\\TUALATIN\EpicorData/Reports/tgleason/Packing Slip
Print02655.XML".
Type: Error
Program: bo/ReportMonitor/ReportMonitor.p
Method: loadData
Table:
Row:
Field:
When we look, the referenced file does not exist. Closing the dialog and
printing again works.
Has anyone seen anything like this?
--
*Tanya Denison* | IT Manager | NRS, Inc.
*2009 S. Main Street, Moscow, ID 83843*
*tdenison@...* <83843tdenison@...>* |
**www.nrsweb.com*<http://www.nrsweb.com>
*c: 208.301.0599 | p: 208.883.7834 Ext 277 | f: 208.882.1744*
[Non-text portions of this message have been removed]