Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Random Bad File Status Erorrs (9/035 & 9/013)
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Wayne Willis
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5190
People Online:
Visitors:
342
Members:
0
Total:
342
Online Now:
New Topics
Lawson Landmark
Executing IPA from PR160
5/3/2024 2:46 PM
We're facing a situation where we need to upda
IPA/ProcessFlow
Executing IPA from PR160
5/3/2024 2:46 PM
We're facing a situation where we need to upda
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
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
1354
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Random Bad File Status Erorrs (9/035 & 9/013)
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Randall
Veteran Member
Posts: 44
7/26/2013 3:25 PM
Hi all,
Since upgrading to Lawson 9.0.1, we've randomly experienced "Bad File Status 9 035" errors in various Lawson delivered programs. Looking up the code, it leads to incorrect permissions on the file that was just generated by the program, usually a temporary file.
Additionally, we've been experiencing a "Bad File Status 9 013" on sort files that are generated by Lawson delivered programs, the most recent being PR197 that derailed our Payroll. Again, looking this up says that the file does not exist. I have trouble determining how a file created by a program is mysteriously gone when it goes into a reporting phase. We've also received the error randomly on other programs like PR141 and PR139.
Lawson recommended that we update our compiler, which was completed a few weeks ago. While we thought we were through it, the issue showed up once again.
We still have a case open with Lawson. However, has anyone else experienced similar symptoms?
I wasn't on board with the company for the upgrade, but from my understanding, it involved new hardware, a new type of disk storage, new environment and new apps. Definitely a lot of variables to take a look at.
Server architecture and the nitty gritty of system administration is not quite my forte, so I can only think of possibilities without knowing how to research them. I'd have to loop in some folks that know more of that than me. However, it almost seems, in the 9/013 error that there might be some garbage collection running on the disk storage since a lot of these files that are missing are temporary? Again, I'm not even sure if that's possible.
If anyone has any advice, please respond or shoot me a message. I'd love to hear what you've done or what you think we could look at.
Thanks,
Randall
Woozy
Veteran Member
Posts: 709
7/26/2013 4:53 PM
Hi Randall,
Are you by chance on Unix? We've had this problem when multiple users are running jobs that use the same files/folders. One user would run the job and it would create the folders/files with their Owner/Group info (i.e. meadek/meadek.upg 660) rather than using the Lawson group (meadek/lawson 660). Then, when a different user tried to run the job it would puke because they didn't have rights to the folder or file.
We ended up working with our infrastructure team to set up a script that runs regularly (every minute??) that updates rights in the {prodline}/work folder so it eliminates this issue.
Just something to consider.
Kelly
Randall
Veteran Member
Posts: 44
7/29/2013 4:05 PM
Hi Kelly,
Thanks for your response. Yes, we are on UNIX. That's a good suggestion. Have you run into any additional issues since the script was implemented, or still seen errors on occasion?
Thanks,
Randall
Woozy
Veteran Member
Posts: 709
7/29/2013 4:19 PM
We do occasionally run into errors, but it is usually due to one of two things. First, the user isn't set up correctly as a Batch User - usually meaning they aren't in the Lawson group. Second, two jobs were run against the same file within the one-minute window - but this rarely happens.
You are not authorized to post a reply.