Accessing Lawson

This section provides you with solutions to some messages you might receive when you try to access the Lawson system.

Message

“Can't get shared memory. A file or directory in the path does not exist.” This can happen when performing a system function, running an online application or batch program, or compiling a program.

Solution

Make sure no Lawson users are on the system and then stop the Lawson system. Use the UNIX functions ipcs and ipcrm to find and remove shared memory, message queue, and semaphore entries whose key begins with the four characters from the following list:

• 0x70 database (ladb)

• 0x7d jobqueue (lajs)

• 0x7e compile queue

• 0x7c transaction manager (latm)

After removing these entries, start the Lawson system.

__________________________________________________________

Message

“Can't get shared memory. Permission Denied,” error when performing a system function, running an online application or batch program, or compiling a program.

Solution

Run stoplaw. Verify that the owner of files in the $GENDIR/bin directory is root with the setuid bit set for the owner. The group should be lawson, and file permissions should be 4777.

__________________________________________________________

Message

ChkLic - “Can't Open License File. No such file or directory.”

Possible cause

The Environment variables are not set correctly. This happens most often with clients who have multiple Lawson Environments.

Solution

Check the environment variables to make sure LAWDIR, GENDIR, and LADBDIR are set correctly. Check the LAWIPC variable to make sure it is unique for each Lawson Environment. Also make sure all servers are started correctly.