Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
S3 Interfaces/Conversion
LP570 PTO Balance upload conversion
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
26
Members:
0
Total:
26
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Integration / Customization
S3 Interfaces/Conversion
LP570 PTO Balance upload conversion
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
13 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
bgodwin
New Member
Posts: 0
2/24/2007 1:12 AM
I'm trying to run the LP570 to upload our PTO balances for our implementation. I get this vague error:
Unable To Open File With Mode "r"
KB articles state this could be a variety of things. I have the file name in uppercase, I have RW access, etc. I've pointed jobdef to where I stored this file (same place I put the other conversion files which worked fine).
I'm baffled and in a desperate situation as the LIS/Help Desk is taking their time guessing what this could possible be.
Any help would be tremendously appreciated.
Deleted User
New Member
Posts: 0
2/25/2007 5:36 AM
Split
Might be a permissions problem on the write directory, or the directory might not exist at all. If you're sure the directory exists and you've used it for other conversions make sure the permissions on the file itself are set right. Are you on Unix? you may try changing the permissions to somthing like 777 rerunning the job and see if it goes then change it back when your done. Also, double check your job run params you may have a typo in your path.
Please
login
to post a reply.