Skip to content
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

Exception: Error dynamically compiling pyRevit runtime when installing "pyRevit_4.8.14.24016_signed.exe" #2055

Closed
Ray-gurge opened this issue Jan 19, 2024 · 2 comments

Comments

@Ray-gurge
Copy link

I try to Install the last update of pyRevit "pyRevit_4.8.14.24016_signed.exe", was initially on "pyrevit-installers_4.8.11.22103"

first at Windows opening :
Revit_pyrevit MAJ---

and at Revit 2023.1 opening
Revit_pyrevit MAJ2
... but it works with Revit 2020.2.9 !!

First time i've have problems with pyRevit
I followed the instructions from :
https://pyrevitlabs.notion.site/Installation-issues-f6495adb56254e9e8021f8a68e3b2ab7
https://discourse.pyrevitlabs.io/t/error-message-loading-pyrevit-in-2023/948/2
...Uninstall, reinstall...
Can't work without pyRevit

Thank's for reply

@jmcouffin
Copy link
Contributor

as mentioned many times around, following precisely this, fixes the pb:
What seems to work in most cases:

  1. Uninstall pyRevit
  2. Delete C:\ProgramData and %AppData%\ pyRevit folders
  3. Move all Revit addins to a temporary location. Usual addins locations include:
    1. %AppData%\Autodesk\Revit\Addins<year>
    2. %AppData%\Autodesk\ApplicationPlugins
    3. %ProgramData%\Autodesk\Revit\Addins<year>
    4. %ProgramData%\Autodesk\ApplicationPlugins
  4. [Reboot computer]
  5. Reinstall pyRevit
  6. Started each version of Revit confirming pyRevit successfully compiled at startup.
  7. Moved all Revit addins that were moved in step 3 back to their original location.
    1. you may want to add them one at a time and start a revit session everytime to figure out which ones are causing the issue.

also, your config file must tell that it uses the CustomTools extension but that it cannot find the folder where it is located.
Removing the pyrevit-config.ini file or the CustomTools extension should fix it

@Ray-gurge
Copy link
Author

... Fixed!
Merci beaucoup!!

It was certainly some mishandling on my part (which one? never had this before) during the set up, and not a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants