Be advised the following "fix" is specific to the situation outlined below. If your upgrade is the same as mine and your Firefox will not launch custom actions then this might fix the problem.
Shame on Lansweeper...
I found the problem and I've corrected it in my installation.
The problem was that I downloaded the upgrade351.zip to soon. Lansweeper made subsequent changes to the sql script and then reissued an updated upgrade351.zip with out notice to the early adopters (me & possibly others). The change was the addition of a SQL alter table statement to the "upgrade 35 to 351.sql" script.
To find this problem I redownloaded the firefox plugin file and did a md5 on files and the ones I had installed. They were the same. So I redownloaded the upgrade351.zip file and checked the md5 to what I had downloaded the other day. They did not match.
So I started checking the md5's on the files I installed from the older upgrade351.zip and the compared them to the newer ones in the new upgrade351.zip.
The only file that had changed was the sql upgrade script. So using the ExamDiff.exe utility to compare differences between files I compared them.
The newer sql script adds the following two lines (which the previous one was missing).
ALTER TABLE tsysconfig ALTER COLUMN Licensekey varchar(2000)
GOBeing the only differences between all these files I decided to run the command.
I launched the lsupgrade.exe utility and pasted only the above portion of the script and ran it.
I then refreshed my firefox browser and drilled down to a computer and tried an action.
I got an alert telling me that myserver needed to be added to some safe list. I ok'd it and then the custom command worked. They all work now.
The only change was the running of the sql portion of the script above.
Shame on Lansweeper for not incrementing the version number and supplying a script to correct their error.
Hopefully I'm the only one this has happened to.
Kevin