-
-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archi error on startup (MacOs) - Cannot invoke "org.eclipse.core.runtime.IExtensionPoint.getConfigurationElements()" because "point" is null #1074
Comments
version 5.3 worked fine on this corporate desktop. only occurring with 5.4 |
Please post the contents of the error log file. This can be accessed in Archi by selecting the "About Archi" menu item. In the dialog box press the "Installation Details" button, then select the "Configuration" tab and press the "View Error Log" button. Please ensure that Archi has write access to its data and configuration folders at You could also try deleting the folder at |
archi error log |
Unfortunately permissions are good and deleting the config directory did not fix. Thanks |
As I can't reproduce this and we've not had this error reported before now I'm afraid you're going to have to try different things such as re-installing, deleting data folders, etc. |
Thanks for looking , will do. I presume there was nothing in the log that indicated anything? |
Only that a tabbed property sheet extension was null which indicates something weird like a corrupt installation, config area or conflict to do with an Archi plug-in or conflicting Archi versions perhaps running at the same time. The only thing I can suggest is to delete the |
Archi Version
5.4
Operating System
14.5
Archi Plug-ins
No response
Description
This is related to a corporate desktop, therefore there maybe some constraint or permissions issue. Works fine on my personal laptop.
Archi really slow to start. Once started this error continually appearsSteps to reproduce
Archi
startup
The text was updated successfully, but these errors were encountered: