Debugging the LibXL installation

This page under construction
{Only If you cannot use libxl after registering...}

Libxl should function properly when registered. But some servers may need some more tweaking. This seems to be more common on servers that are using a service account to run ACP. When Service accounts are created they can have different permissions depending on the default settings of the organization and the hosting provider, and may require more configuration. You can check the following settings while debugging any trouble launching the Com object.

Check in Desktop Analytica

If you can't launch LIbXL from the test model It is probably a good idea to start with debugging the Desktop Analytica (DTA) problem first, since it just tends to be easier to figure stuff like this out. Launch suan.exe by double clicking on it from the Program Files\Lumina\Analytica *.* folder, and then open the Test LibXL Installation model.

/RegServer as Admin

It is possible that LibXLCOM.exe /RegServer was run from an account other than your own, which was also not an admin account. In that case, it may have registered the component for only that one user, and not for you. If you do a RegSvr as administrator, it will usually make it available for all users.

DCOM settings

If you get an access permission error when launching, go into DCOMCNFG, find “XL class”, go into Properties.

• Launch & Activation permissions, set to custom and make sure Allow local Launch and local Activation is enabled for the user running ACP.
• Identity tab. Normally here you should set the user to be the Launching user (which is the AcpUser).
• Try launching Libxl again in Acp.
  • If Libxl does not run under this launching user, try changing the identity to another user (eg yourself or an admin user.) If Libxl launches with this user then investigate the cause. What is the difference between the 2 users.

Task Manager

When you use the test model to Launch Libxl, check the task manager to see which user Libxl is running under. It should be running under the user whose identity was selected in the DCOM configuration. If Libxl is not running you can try changing this user.

Unregister

If you encounter a problem with using libxl one of the reasons could be a conflict with an earlier version. To uninstall libxl, start CMD as administrator, CD to the directory containing this file, and type:

LibXLCOM.exe /UnregServer

Note: launch the command prompt explicitly as an administrator even if you are an admin user.
This should remove libxl from the registry (the version contained in this folder only - if you have more than 1 version on the computer you will need to repeat for other versions in other directories if you want to uninstall all).

Windows logs

vbscript launch suan as a regular user lauch suan.exe as the user which runs ACP Service accounts can be problematic. Recheck the Windows application log for errors related to libxl.

Restart

On one occasion it was reported that Libxl could not be launchd, but then apparently after a server revboot ACP was ablt to use Libxl. You may want to try a reboot if nothing else seems to get Libxl to laucnh proplerly.