Happy 8th birthday to the Maveryx Community! Take a walk down memory lane in our birthday blog, and don't miss out on the awesome birthday present that all Maveryx Community members get to take advantage of!
A few quick questions - are you attaching a file you are generating in workflow? Is it on a network drive? Can you confirm that path you are generating to the file is accurate (ie the correct path)... Your attachment is blurred out - but I usually use that section to tag a field which has the specific path of the attachment. I find that's cleaner.
One more question - I notice this is SAP goodness - are you using DVW - if not - you should be.
Thanks for the quick response! The file is local but it is generated from the workflow (I put several "Block Until Done" to make sure that the files should be complete prior to sending). I selected the path/file directly from the "Attachments" box (see below). As for SAP, it does feed to our customer's system but they upload it manually (not sure what DVW is), I just create the data for them and they take it from there, I just wanted to not have to manually email it. :-) Thanks again.
I also tried sending a file that was not in the workflow to see if the data being written to the file was an issue and it gave me the same error (Failure when receiving data from the peer). I tried the throttle tool (mentioned in the link to other fixes) as well and that also did not fix the issue.
I figured it out! My issue was the name of the file itself. DO NOT USE SPACES IN THE FILENAME! I used underscores instead of spaces in the name and it corrected the issue. Oddly, the file path can have spaces but the filename itself triggers the error.
Late to reply here, but wanted to comment in case anyone else comes across this error. I found that not using spaces in the filename worked for me as well. AND not using commas in the filename as well. Just used regex replace and took commas out.