LADB startup error after LSF 9.01.13 update

We are getting an LADB error during our 9.01.13 install upgrading from 9.01.9 on Windows 2008 R2 64 / SQL 2008 platform.

ladb.log has error: ladb (main): can't create shared memory Invalid argument (22).

I came across KB 1190006 but it does not exactly apply to us since we are SQL 2008 not DB2.

Has anyone see this before? I'm wondering if Infor changed something or added a new env var in 90113 for DB connection?

Thanks.

[Updated on 12/3/2014 5:45 PM]

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

Painfully yes. We have had this as our application and SQL database share the same server. We have had to limit the SQL memory usage. We also don't auto start our Lawson services. And finally a clean reboot will clear memory. I will have to keep an eye on this as we are getting to upgrade to new servers and it seems like we have to work through this again. On our current server we upgrade to Env 9.0.1.13 and thankfully didn't run into this memory issue.

gwhiteford

Please keep me informed as to your workarounds for these issues as we are about to upgrade from 9.0.1.9 to 9.0.1.13 next week and we run SQL servers as well. Thank you!

unknown

We have rebooted and it did not help so it's not like a locked dll from an orphanded java process. Dealing with Infor support in Manilla has been painfully slow and our Test Env has been down for 6 days now!

rod-rupps

Make sure all of your Windows environment variables are correct on your application server, especially the ones pointing to MS SQL. Also check your variables in your MICROSOFT capital file to make sure it's pointing to the correct DB or if you are using a servicename check that in LS Security.

Copyright © 2025 Infor. All rights reserved.