"File not created" on the email statements error report

(0) Share

Report

Posted on by Oscar Mayer

520

Email statements is setup in GP v18.2 under the original GP functionality (versus use of Word Templates). Issue is some customers work fine while others do not though the setup of under Cards - Customer - Options (Customer Maintenance Options window) is set up correctly with no difference between them. To expand, comparing the set up between the Internet Information window, Customer Maintenance Options window, and Customer E-mail Options, there is no setup differences other than the actual customer and email address for To with the Send E-Mail Statements box marked on the Customer Maintenance Options window.

The EmailStmtStatusPath= is set to a network share which all GP users have full control to.

Any ideas to check into why the "File not created" error is occurring for many customers?

Of a batch of 18 customers to receive statements via email, only 3 were successful.

I have the same question (0)

All responses (2)

Answers (1)

Suggested answer

JanelleM Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Randal,

Thank you for using Microsoft Communities.

When issues or errors come up during the e-mailing process, it can be caused by numerous things. Out on the communities is a really good article and link to a 'Dynamics GP Email Troubleshooting Guide' which lists out some of these many things and resolutions which can cause e-mailing issues. Below, I have copied in the link to this article for your convenience.

community.dynamics.com/.../dynamics-gp-email-troubleshooting-guide-1743830067

I hope this helps.

Janelle

Microsoft Support

Was this reply helpful? Yes No
Verified answer

Oscar Mayer 520 on at

Like (0)

Report
Copy link

Link copied!

Solution was found which involved updating the records within the SY04905 table for the company. Comparing the records between successful and unsuccessful customers, value of 1 (Enabled) was set in the table for unsuccessful customers even though the GP interface reflected Disabled. Updating the records to a value of 0 (Disabled) resolved the issue.

Was this reply helpful? Yes No