Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Supply Chain Management
Lawson S3 Supply Chain
EDI error at random times
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
284
Members:
0
Total:
284
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson S3 Supply Chain
EDI error at random times
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
slavo
Basic Member
Posts: 8
5/13/2013 5:35 PM
We started getting errors in our EDI jobs, both inbound and outbound. About halaf of the times EDI jobs run (via recdef) they complete fine but 1/2 the time we get errors like the one below. This just started happening about 2 weeks ago, and NO nothing chganged in terms of Lawson or servers. ANy ideas or suggestions on how to fix this?
20130513113846,251, ERROR NEOFTPGHX Communications FAILED
20130513113846,252, ATTEMPTING CONNECTION TO 168.200.65.84 21
20130513113846,253, ERROR: UNABLE TO put [ghxftp.20130513113846.edi]
20130513113846,254, Opening ASCII mode data connection for ghxftp.20130513113846.edi.
Thanks much,
Slavo Milojevic
mark.cook
Veteran Member
Posts: 444
5/14/2013 5:59 PM
Out of curiosity, it looks like this is trying to send to GHX. If it is, could it be that server, I know they send those plug and play. Could the server be failing?
JonA
Veteran Member
Posts: 1162
5/15/2013 6:31 PM
We get a similar error but only very occasionally. It usually works the next scheduled time so I've never investigated it. For lack of any reason, I've attibuted it to server issues on the receiving end.
slavo
Basic Member
Posts: 8
5/16/2013 5:17 PM
Things are working fine now. Turns out we had adjusted the paging space and rebooted the GHX server. I think the issue was that we can log in and authenticate and that uses port 21 but the PUT and GET command use port 22 and there was something holding port 22. The restarted fixed things. Thanks everyone.
You are not authorized to post a reply.