An error occured during GHA assembly loading:

Components not loading into Grasshopper on startup. Has been occurring since this weekend. Here’s a snippet:

An error occured during GHA assembly loading:
Path: C:\Program Files\Rhino 7 WIP\Plug-ins\Grasshopper\Components\Kangaroo2Component.gha
Exception System.UnauthorizedAccessException:
Message: Access to the path ‘C:\Users\thans5\AppData\Roaming\Grasshopper\PluginLoading.txt’ is denied.

An error occured during GHA assembly loading:
Path: C:\Program Files\Rhino 7 WIP\Plug-ins\Grasshopper\Components\MathComponents.gha
Exception System.UnauthorizedAccessException:
Message: Access to the path ‘C:\Users\thans5\AppData\Roaming\Grasshopper\PluginLoading.txt’ is denied.

An error occured during GHA assembly loading:
Path: C:\Program Files\Rhino 7 WIP\Plug-ins\Grasshopper\Components\ScriptComponents.gha
Exception System.UnauthorizedAccessException:
Message: Access to the path ‘C:\Users\thans5\AppData\Roaming\Grasshopper\PluginLoading.txt’ is denied.

An error occured during GHA assembly loading:
Path: C:\Program Files\Rhino 7 WIP\Plug-ins\Grasshopper\Components\SurfaceComponents.gha
Exception System.UnauthorizedAccessException:
Message: Access to the path ‘C:\Users\thans5\AppData\Roaming\Grasshopper\PluginLoading.txt’ is denied.

An error occured during GHA assembly loading:
Path: C:\Program Files\Rhino 7 WIP\Plug-ins\Grasshopper\Components\TriangulationComponents.gha
Exception System.UnauthorizedAccessException:
Message: Access to the path ‘C:\Users\thans5\AppData\Roaming\Grasshopper\PluginLoading.txt’ is denied.

1 Like

If you start Rhino in administrator mode, does it work then?

Same result when I run in Administrator mode.

In that case, can you check whether the txt file it complains about exists? If it does, are you allowed to delete it by hand via windows explorer?

If not, can you restart Windows to try and get rid of whatever process is locking that file?

Upon launching Grasshopper, PluginLoading.txt file appears at the end of the start sequence, then disappears.

I’ve restarted Windows, uninstalled, reinstalled, etc… For both v6 & v7. Changed folder/file attributes as well.

Weirder and weirder. The file is created (as it should), the file is deleted (as it should), and yet access to the file is unauthorised. The three things I thought might cause this have been ruled out.

When you say “both v6 & v7” you mean you reinstalled both, or is it failing on both?

Yes, I’m seeing same errors with v6 and v7.

That’s particularly bad news for v6, I can make the loading check continue on failure tomorrow for v7, and next week’s Beta will have that fix, but i don’t know when or if there’ll be a Rhino 6 service release.

So unless the underlying problem can be solved, v6 is busted for the foreseeable future. I’m searching for possible reasons why Windows would restrict access to the app data folder, but I can’t do much until office hours tomorrow.

Thanks David. Any resolution that you can provide is appreciated. I’m happy to test any ideas that you have.

I did notice that a few others in my organization were experiencing similar issues earlier this week. Not sure on their status.

I’m using v7 for a particularly hot project right now. So v6 isn’t my highest priority.

Okay, before I call it a day, you running any anti- virus scanners? If yes, any chance you can tell it to not look at the folder C:\Users\thans5\AppData\Roaming\Grasshopper\ ?

That’s a good call. Will dig into that.

Interesting development, this whole plugin load tracking mechanism is already fail-safed up to the neck.
I’m now wondering if some other code is keeping tabs on files in that folder and trying to handle the file creation/deletion.

I’m wondering the same. I’ve asked our IT team to investigate. I’ll let you know what they find.

I’ve reverted to Rhino 6 SR7. Only issues with Grasshopper are breakpoint: components built against a newer minor version of the Grasshopper SDK. Those components fail, but all else is working normally.

When I revert to a previous v7, I’m getting the errors listed at the beginning of this thread.

I’ve redesigned some of the code involved here, and I’ll also make the checking disableable (is that a real word?), so hopefully next Tuesday you can try the latest Rhino 7 release again.

1 Like

I am also seeing this issue on Rhino 6 and Rhino 7. I won’t be surprised if it’s also related to IT.

Did it suddenly start happening a few days ago?

Thanks David. We look forward to Tuesday’s build.

Fwiw, Orion and I both work for the same organization.

Yes, it started a few days ago.