How to reset 'LAWSON' permissions on WINDOWS

My permissions are "messed up" (new technical term) for user LAWSON in production. I was attempting to apply a patch early this a.m. and received the error "/usr/bin/cp: cannot create regular file 'LAWDIR/PL/metadata/r1meta/R102.pgm': Permission denied" I checked permissions at LAWDIR/PL and have 'full control' that applies to tthis folder, subfolder and files. Well WINDOWS LIES. Checked permissions at LAWDIR/PL/metadata and found LAWSON has no permissions. Is there an easy way to fix this? So far EXTREME has told me I have a permissions problem and to fix it, after I opened a case early this morning stating I have a permissions problem and asked how do I fix this in WINDOWS. I know that once I get through UPDATE with patch, ACTIVATE will take me through a DBREORG of PAYMASTER, so I need to have permissions correct for user LAWSON for everything.

tia,

mike

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

richardd

Lawson doesn't have permissions to that folder. The Administrators group does of which Lawson is a member. Have you tried using permsmaint to reset your permissions? Have you compared your production permissions to those on your test system?

bhillz

Do you want to rest perms on just that folder or are others affected? If it's just LAWDIR/<PL>/<some_directory> it's should be fairly straight forward. if you're talking about the whole LAWDIR/... tree it can get really complicated fast.

Dan's right, what are the perms on your other systems?

Marilyn Sizemore

I second Dan's comment. Your first step is to run the permsmaint command to restore permissions settings. Depending on your system config, it can take a few minutes to run. In Windows, I would execute the cmd using the Lawson account.

unknown

Thank you everyone for your input. I have been comparing DEV with PRODUCTION and permissions are definitely different. I'm not saying that DEV is 100% correct, but I have been able to apply patches (preview, update, activate including DBREORG) for PR YE and ACA YE on DEV. I check the PERMS.cfg on both and the last updates were Nov 2015, so I should just run 'permsmaint -s' from signed on as lawson from LID? Does it matter whether security is on or off

Marilyn Sizemore

Hi MIke - apologies for the delay in response - holiday break. I typically do not disable security when running the cmd. There are a few ways you can run this, you can reset for the full environment, or just for the applications. The directive I usually use for the apps would be permsmaint -sap <prodline>. The -s directive will set apps permissions based upon settings found in the lawdir/system/ladirs.cfg file. The -a directive updates applications only. The -p will allow you to set permissions on a named product line. You can view the remaining directive options if you run the permsmaint -z command. (typically, the utilities don't have a z directive, so it will force the system to display available valid options). Also, if you find your permissions are different between environments, I would compare the perms.cfg (env)and ladirs.cfg (apps) files between the servers. These files are located in lawdir/system, and can be modified to meet your needs.

unknown

I was also off for a few days (2 holiday & 2 vac), and resisted the temptation to dial in and run permsmaint after extreme recommended 'permsmaint -R -b 1' , tried that today and still blow up when executing 'lawappinstall update PL' with the same error:

/usr/bin/cp: cannot create regular file 'E:/lsfprod/law/prod/metadata/r1meta/R102.pgm': Permission denied

Copyright © 2025 Infor. All rights reserved.