Archive for category: News

Microsoft Windows Server provides a tool called ADSI Edit, which can be used to get a closer look at your LDAP configuration.

Please be careful when you are moving around in LDAP, as mistakes here can destroy your Lawson Security configuration.

Your first step should always be to back up LDAP. Nogalis provides another article with instructions on how to do that. (How to Backup LDAP in Lawson v10)

Next, verify that the necessary features are installed on your Windows Server.

1. Open your Windows Features & Roles
2. Navigate to Features
3. Check for AD LDS Snap-Ins and Command-Line Tools
   1. If not installed, install it
      

Once the AD LDS Snap-Ins are installed, go to Start > Run > mmc.exe

Go to File > Add/Remove Snap-Ins

Add the ADSI Edit Snap-In

Right-click on ADSI Edit, and select “Connect to…”

Type in your LDAP server name under “Select or type a domain or server”

• The LDAP URL can be found in your Lawson install.cfg file, under the setting LDAPHOST

Type in your Connection Point

• This can be found in Install.cfg under the LDAPBINDDN setting (everything except the ldap admin username)

If you need to provide credentials to connect to your LDAP instance, click “Advanced…”

Select “Specify Credentials”

Type in the LDAP admin username

• This can be found under the LDAPBINDDN setting in Install.cfg

Type in the port number

• LDAPPORT in Install.cfg

Select “Simple bind authentication” if applicable

Click OK and OK

You are now ready to expand the tree on the left side of the application, where you can view resources and other security settings

Sometimes users would like to go directly to Lawson through Ming.le, rather than clicking on the Lawson Icon (globe).  To help users with this requirement, you can generate a URL that opens Lawson when Ming.le is loaded.

1. Open your Ming.le site, and click on the Globe 
2. Make note of the URL
   1. 
   2. Add the following text to the URL: ?LogicalId=lid://infor.lawson-s3.1
   3. For example https://lawson.server.com/Lawson%20S3/SitePages/Default.aspx?LogicalId=lid://infor.lawson-s3.1
3. Users can either bookmark this new URL, or you can add it to your Intranet site

When applying updates to Lawson System Foundation, you may see an error returned  in the log saying, “Error: Fatal Not all files were delivered.”  While the red highlighted message does not indicate exactly what the problem is, the actual error can be seen earlier in the log.  It reads: “Failed to load inst-gendir-coreadmin/bin/launtdll.dll to D:\lsfdev\gen\bin\launtdll.dll – Delete failed.”  You may then try to delete the launtdll.dll manually.  If so, you will see another error message that the file is in use.  The file becomes locked by the Lawson Unix Utilities when the environment starts.  To resolve the issue, you can set the Lawson environment service to start manually.  Then restart the server.  After the restart, you should be able to manually delete the dll and run the update again.  Selecting the Reload option will redeliver all of the files and the update should continue past the original error.

Sometimes when you are troubleshooting issues with Ming.le, your support technician will ask which version of Ming.le you are using, Enterprise or Foundation.  There are a couple of ways to determine this.

First, you can open your Ming.le website and direct your attention to the header.  If you see the “social” apps section in the header (highlighted below), you are running Ming.le Enterprise.  Otherwise, you are running Foundation.

Enterprise:

Foundation:

Another way to determine your Ming.le version is to click the “i” icon at the top of the page .

 

Enterprise:

Foundation:

Users may find that the browser returns blank.htm when accessing the Lawson portal screen.  With Internet Explorer, this can be caused by Compatibility View Settings.  To verify the setting, click on the cog in the upper right of the browser.  From the menu under the cog, select Compatibility View Settings.  A window will return showing the Compatibility View Settings.  Uncheck the box labeled “Display intranet sites in Compatibility View” and refresh the page.  Also within the Compatibility View Settings, verify that the  site is not in the list under “Websites you’ve added to Compatibility View.”  If the site is in the list, click on the site and then click the Remove button.  After closing the Compatibility View Settings window, refreshing the page should then allow the portal to be displayed properly by returning the login screen.  If the compatibility view is not available or changes to it are not allowed, other browsers such as Chrome or Firefox could also be used to access the page.