Anyone have any idea why these 2 errors are showing when Lawson service starts up? Windows 2003 SP1, Env 8.0.3.6. LAUA looks completely normal, laservstatus shows everything running in multiuser mode, data can be accessed - but problem we are having is that inquire, add, delete, next, previous all lock up the LID form. Drill downs all show data, so db connection is fine (and as I said, dbdump works fine).

These are the errors:

WIN32Error: sid.c(523): NT AUTHORITY\SYSTEM: laserv.exe: LookupAccountName(0) - No mapping between account names and security IDs was done.
Matthew Palmer [Thu, Mar 30, 2006 2:23 PM]
The second error is:

Error: laserv.c(988): NT AUTHORITY\SYSTEM: laserv.exe: Lawson Service (Get_Ladb_Latm_User) Unable to get ladb user SID for 0

Thanks!

OK - found that these errors are normal when record debug events is on. However, anyone have any thoughts on why LID forms would just hang? No errors in any log files at all. This is 8.0.2 apps - it happens across multiple prod lines.

All regular sys admin functions (laua, etc) work fine.

What do you mean when you say LID forms just hang. Is it when the form is first opened or has the user performed an Add, Inquire, etc?

only on Add, Inquire, Delete, Next, Previous. Drop downs show data just fine (as in CU00) - I can pick an item to inquire on but them form just hangs - this happens on all forms.

OK - Event viewer is showing this:

Application popup: run.exe - Unable To Locate Component : This application has failed to start because jvm.dll was not found. Re-installing the application may fix this problem.

LAW_JAVA_HOME is correct - what does PATH need in it?

What version of Java SDK do you have on your Lawson application server?

If you are using 1.3.1 then your PATH in laconfig should include:
%LAW_JAVA_HOME%\jre\bin\hotspot

Since this is 8.0.3.6, that strongly suggests that the JVM is 1.4.2. I would think that that would means that the PATH must include %JAVA_HOME%\jre\bin\server. (At least that's where jvm.dll is located for 1.4.2.)

My 2-cents'-worth: We're installing the same thing. We had the same problem -- jvm.dll not found. I researched and found this:

Net Express 4.0 was looking for a missing JVM.DLL that the PATH setting in LaConfig pointed to JVM.DLL in directory %JAVA_HOME%\jre\bin\hotspot. The solution was to move the path to a directory that contained JVM.DLL. That's according to Lawson. Now here's the tricky part: In Java 1.3.1_15 there are three directories that contain JVM.DLL:
jdk1.3.1_15
|-- jre
|-- bin
|-- classic
|-- hotspot
|-- server

Now in Java 1.4.2_11, there are two directories that contain JVM.DLL, but the Hotspot directory is gone:
j2sdk1.4.2_11
|-- jre
|-- bin
|-- client
|-- server

The real head-scratcher is that the size of the JVM.DLL's is different in all five directories. The 1.3 \hotspot JVM.DLL is mid-way in size between the 1.3 \classic JVM.DLL and the 1.3 \server JVM.DLL. The 1.4 \client JVM.DLL is about half the size of the 1.4 \server JVM.DLL.

With no idea of what is was missing, I figured, Lawson didn't use \server when \hotspot would do. So I pointed LaConfig to \client. So far, so good; if it fails at some point, I can always switch to \server.