LSO MSI Install not showing M3 Transaction menu

I would start looking in the client log to see if there are any errors there. Another thought is if your system have several system profiles and you are using one that does not have the M3 feature enabled.

Hi Eklind,

Thanks for the tips, I have only one system profile for the environment so don't think this is the issue. The log shows the M3 menu is fetched but it shows nothing..log file entries:

INFO MForms.M3Menu.MenuHandler.HandleResult  M3 Menues fetched. No of record = 2897
INFO MForms.M3Menu.MenuHandler.LoadMenu  Menu version "" is used when fetching the menu. Timestamp = 0
INFO Mango.UI.Services.NavigationViewDS.GetRootNodesFromApplications  internal implements IClientApplicationTasks but AvailableTasksRoot() returns null so it will not have a root node in the Navigator.

Doesn't make much sense to me though

The machine where the .msi installation is not working properly, is the ClickOnce installation working on the same machine (or is that another machine)?

The reason for asking is th there can be problem with the internal DB in the LSO client and that cann occure when there is a SQL Server installed on the machine. If that is the case you should see entries like this one in the log file:
2012-02-23 00:10:50,661 [Mango.Main] ERROR Mango.Core.Persistance.DataBase.CreateDatabase - [COR0001] The SQL CE database could not be created from the connection string Data Source=C:\Users\user1\AppData\Local\Apps\2.0\Data\B8CCRPRD.9T5\RP4WW4TD.9VX\http..tion_0498f7d2f3e4539a_000a.0000_f2d1e0c02eb0bcb7\Data\S0\U0\Local\DB\Mango.sdf;LCID=1033. Functions depending on database will not be available.
Unable to load the native components of SQL Server Compact corresponding to the ADO.NET provider of version 8080. Install the correct version of SQL Server Compact. Refer to KB article 974247 for more details.

Yes the .msi install is on the same machine with the working ClickOnce installation and I have seen the error message you described. I've tried uninstalling all LSO installs and .Net 4.0, deleting all the c:\users\ folders and still the same problem.

Is there any issue to install both on the same machine? I'm testing the .msi install to package for Citrix hence the reason for the install.

There should be no problem having both the .msi and the ClickOnce installed at the same time. But I am surprised that you get the menues to work in ClickOnce if the there is problems with the SQL CE databse.

Anyway, I think if you solve the problem with the SQL CE databse you the menues should work in the .msi version.

This is what I have found when searched earlier for the problem with the SQL CA database.
"At any given point of time, the correct state of a 64-bit computer, for SQL Server Compact, would be the following: Both x86 and amd64 MSIs are installed. Both x86 and amd64 MSIs are of the same version.
Therefore, if you face any similar issues, make sure that the computer has both x86 and amd64 MSIs of Compact are installed and they are of the same version. In case, they are not, then install Compact SP2 x86 and x64 MSIs from following link as needed: http://www.microsoft.com/...DCE24&displaylang=en"

Some more information
http://stackoverflow.com/...f-sql-server-compact

Hope this helps.

I tried installing both versions of Compact and the errors relating to SQL have gone but still the same problem. Will do some more investigating tomorrow as getting a headache thinking about it. Tested the ClickOnce again on the same machine to confirm and this is still working perfectly. I checked the settings in Profile match both installs and other strange thing I found is the companion shows the following error message "The Link companion:/// could not be opened." whereas the ClickOnce works fine.

Guessing some connection to the server is not working correctly with .msi install but not sure how this component works differently between the two installs

Thanks for the tips & I'll keep trying tomorrow

I am out of ideas. Open up a case with Infor support, add the log file from the working ClickOnce and the log from the failing .msi installation.

Hi Eklind, found the problem was incorrect value in the FeatureLocation and once this was set correctly the .msi install worked correctly.

Appreciate the help and glad to finally get it working

Of course! If having the logging set to debug it will show what features is loading during the startup of the LSO client. I should have thought of that.

Mr.Potato or Eklind, where is the FeatureLocation set?  Have an issue where the menus are not working and launching applications requires the mforms:// prefix to launch them and want to see if i can locate this setting.

If the M3 programs can be started with mforms:// the features have loaded correctly. You can still view the FeatureLocation URL in the registry at: HKLM\SOFTWARE\Lawson Software\Lawson Smart Office

The client log should have some error entries regarding retrieveing the M3 menu.

In LSO 10.0.5 there is a missmatch between the msi and client. The registry is written to Software/Infor/Infor Smart Office but the client reads from the previous location under Lawson. So I guess you should check the registry. This means upgrades from 10.0.4 works but newly installed msis will fail.