Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Our World Statistics Day conversations have been a great reminder of how much statistics can inform our lives. Do you have an example of how statistics has made a difference in your life? Share your story with the Community!
Problems installing JMP PRO 14.1 concurrently with older versions
Dec 3, 2018 11:30 AM(9856 views)
We've had reports in our company of a few users who had troubles after installing JMP PRO 14.1. All of them had in common that they had an older version of JMP still installed on their machines (regular 14.0 and regular 13.2.1 to be exact).
These are the issues they reported:
User does not see the home page, with the recent files and opened windows.
The main menu does not work, is disabled.
The below window (Window List) is stuck, cannot be closed.
The second command line (New Table, New script, open...) is working, and one can access tables and work with them from there.
See picture below:
Other complaints from different users:
opening files from windows explorer opened a new instance of jmp each time.
Excel third party add-ins that targeted JMP stopped working.
Users do not have aditional permitions/admin rights.
JMP was installed through windows Software Center/SCCM.
Only a few users reported similar problems.
OS = Windows 10 64bit
Enterprise License for desktops (Anual)
If anyone has experienced similar issues, or know the root cause/work around for these problems I would apreciate some help.
Once you click on the new table, a table opens and you can use JMP normally, including all the Menus. So it's the home page that is broken.
I have cleaned the local user SAS registry, as to start fresh on the defaults and recent files. Didn't work.
I have uninstalled the older version (13.2.1), the new version(14.1), deleted all the JMP related registries I could find, all the appdata , user, program files and then install fresh. Did not work either. That was installing using an Administrator account, and aparently nothing got blocked during installation.