RhinoCam 2 issue

We've been using Rhino4 and RhinoCam 2 for years without many issues. Saturday when we selected Rhino to work on some projects we got the following error message concerning RhinoCam.

Unable to load RhinoCAM 2.0rhp plug-in: no class derived from CRhinoPlugIn in plug-in file.

Please contact the plug-in vendor to get the latest version.


I know that 2 is no longer supported but does anyone have an idea on how to fix this. We spent a lot of money on this program but now the only answer we got from the manufacture was that we needed a $6000 upgrade.

Thanks,

Mike

I had this same issue about a year ago. The problem was attached to a user on our domain. The domain user could go to any machine and get the same error, while no one else had any problems. I looked through my email to see how we resolved it, but it must have been resolved over the phone. I think we had to delete some files(or registry entries) for them to repopulate, or maybe we just reinstalled rhinoCam for that user. Sorry I can't remember exactly what we did, but it was definitely tied to the user account. Have you tried another user account?

It seems to be tied to one user account. We can sign in on another machine using a different account and it works. Now to figure out what files.

I am thinking it might be registry related, but I'm not positive on this.

He had a windows update on Friday night and Saturday morning it didn't work. I think he's going to run a recover back to Friday and see if that fixes it.

OK. Keep me posted.

Just found this by putting the error code in a Google search.

We identified the issues as caused by an entry in the Windows registry:

In the registry folder:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

There is an entry:
“C:\Program Files\Rhinoceros 5.0 (64-bit)\System\Rhino.exe”="$ IgnoreFreeLibrary<symvol.rhp>"

(Where symvol.rhp is our plugin.)

Deleting this entry allowed the plugin to install/load correctly. It appears our plugin triggered some Windows compatibility behaviour somehow (maybe a crash during loading or unloading or something), which then got in the way of the process Rhino uses to load plugins.

this is the website: https://discourse.mcneel.com/t/no-cl...-file/11254/29

Glad you got it straightened out!

The registry edit did the trick. Thanks for your help.