We’re having issues running RhinoCompute. The error we’re getting is:
Application startup exception
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at Rhino.Runtime.InProcess.RhinoCore.InternalStartup(Int32 argc, String[] argv, StartupInfo& info, IntPtr hostWnd)
We have a single plugin installed for Grasshopper. There was a history of the plugin not working which we fixed by matching Serilog to what Compute was using, thanks to @AndyPayne . More info here.
After fixing this issue, things have been working fine until a few days ago when we started getting Internal Server Errors returned from calls to Compute. This is strange as nothing has been changed on our Server.
I have tried double checking Serilog version. Then I tried removing the plugin altogether. But we’re still getting the same error.
Typically, this type of error comes for a licensing issue. Can you check your environment variables and make sure the auth token is correct. You may need to reset this variable. To do this, please follow these steps.
I checked and the environment variable is set correctly and auth token is fine.
Attempting to reset the auth token I’m going into a endless loop when clicking on Get Auth Token.
I finally got around the loop issue and got a new token. Added the token to server using the instructions and restarted Rhino compute but still getting the same error.
One thing that comes to mind is that our setup has been working okay until a few days ago. We did receive an email about our usage and that our credit card in the account was charged. Since you’re saying this is a licensing issue, could it be that the payment hasn’t gone through? I couldn’t find a way for us to check if there has been an issue with payments on our Rhino account page.
@AndyPayne do you have any other suggestion how we could debug/resolve this? We released our app with a lot of excitement when everything was working and then rhino compute suddenly broke so we had to disable our app for our users so we’re in an awkward situation atm.
Thanks @brian. Nothing has changed on our server that I know of.
When I remove the plugin we still get the same error. And our plugin was the only one installed.
We figured the issue and it was indeed licensing related.
Our server was blocking Rhino’s remote license server. We just needed to white list them.
See this thread for more info and url’s required to allow.
What remains a mystery however is how our setup was working for a few days in development and after release before suddenly not working.