Came in this morning and we seem unable to create new records in our production Epicor server! Affected record types we’ve discovered so far:
Vendor (Supplier)
Part
Customer
Employee
For all, the error message is the same:
Exception caught in: Epicor.ServiceModel
Error Detail
============
Message: File name was not specified. One cause of this is not having permissions to write to output location. Contact your system administrator to verify.
Parameter name: fileName
Program: Epicor.ServiceModel.dll
Method: ShouldRethrowNonRetryableException
Client Stack Trace
==================
at Epicor.ServiceModel.Channels.ImplBase`1.ShouldRethrowNonRetryableException(Exception ex, DataSet[] dataSets)
at Erp.Proxy.BO.EmpBasicImpl.Update(EmpBasicDataSet ds)
at Erp.Adapters.EmpBasicAdapter.OnUpdate()
at Ice.Lib.Framework.EpiBaseAdapter.Update()
at Erp.UI.App.EmpBasicEntry.Transaction.Update()
I have a support ticket CS0002177267 opened with Epicor, but not hearing back from them yet and if I call they just say “it’s already assigned to someone.”
One potential cause we just thought of - we recently purchased EDI/Demand Mgmt and DocStar/APM from Epicor and installed a new license file - then the app server was rebooted during a monthly maintenance window this weekend. Maybe this has something to do with the issue cropping up suddenly? Some configuration setting for one of those modules is needed?
I’ve seen the generic error when something just can’t write out… Even if we have let’s say Multi-Company running and we take our shared server down, it would start throwing those errors since it cant write to the log file – It couldn’t write… It may be setup, but perhaps it can’t write to a path. Perhaps its looking for Employee Images?
It could be anything. I see it mentions Employee Adapter. EDI shouldn’t be a problem unless you have the Process scheduled to run every x minutes.
It could be even as simple as your EpicorData folder lost permissions check the “Agent” configuration there is a Server and a Client Path, make sure both are accessible.
You were so close Haso, and Epicor Support finally gave me the last piece of the puzzle. It was the Advanced Quality Module integration (with IQS Trubox). Somehow my IQS VM was shutdown, and thus the file share it writes CSV files to for certain record updates was not there. Interesting shortcoming of putting that file share on the IQS server itself (which is how Epicor Pro Services did it) - maybe it would be better to have that share on the Epicor app server and have IQS remotely watch for the file drops, since keeping Epicor humming along is much more important to the company.