When we do a checkwrite, we sometimes have Outlook connectivity issues that prevent the emails from being sent to our vendors after we print remittances. This causes a variety of issues for us (along with, of course, vendors who wonder if there's EFT out there for them). It sometimes hangs the batch too. A few questions: has anyone else experienced this type of thing? What is the best way to mitigate the risk of having a flaky connection to Outlook? BTW - the "connection issue" is apparently network related (and sometimes prevents GP from accessing its data and has even caused APPCRASH events for us) and is being investigated. But in the meantime, we are running into this issue nearly every time we run checks. Batch Recovery sometimes is an option if it hasn't gone too far. It restarts right before the emails send then once it's restarted, the emails send out as the process fully completes.
Thoughts? Suggestions? Comments?
SOMA - not even an answer from you on this one? Anyone? Hoping to get some insights...
Still wondering if anyone has any insights on this.
I am not faced this issue earlier. I think this is related to Outlook.
Have you tried to manually sent any test emails to the vendor email id in outlook ?
If you facing the issue as well in outlook, contact your IT team to check the outlook security.
Hope this helps!!!
Note: Please mark it as verified, if this answer your question. Because this will helps to some others who experience the same.
Somakarpagamoorthy K | Microsoft Dynamics GP Consultant | Dynamics Thoughts
Let me give some additional background: we have some transient network issues that are periodically (and without warning) interfering with our checkruns (we are still on GP2010, btw). Here are more details: 1) the user selects the checks to do the payment batch, 2) he chooses the posting date, 3) he hits process and it processes 100%, 4) the window comes up to finish the remittance processing (send email "yes" etc.), 5) he instructs it to complete --- this is when our error happens --- it is either an APPCRASH or GP hangs without any explanation. In the event logs we see the following: "Connection to MS Exchange has been lost. Outlook will restore the connection when possible." These users are running on an Exchange server that is not co-located with where the terminal servers and the SQL servers are. We have been told that "network issues" are what's temporarily (and without warning) making Outlook unavailable to the application. Other than eliminating our issue by eliminating the network issues and/or moving the Exchange server, is there anything else we can do to mitigate this risk? Other than saying "no" to send emails, of course. ;-)