The remote procedure call failed. (Excepción de HRESULT: 0x800706BE)

Replies to This Discussion

Permalink Reply by David Rutten on February 7, 2013 at 3:49am

Nobody will be able to tell you what's wrong with it without having both the external dll (was it written in pure C#?) and the python script. And even then I think it may be a long time before someone figures it out. Since Giulio left Python support has suffered quite a bit.

You could also ask on the Rhino Python forum if there's no answer forthcoming here...

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Manuel Sotomayor Millan on February 7, 2013 at 4:09am

so I upload the dll and the python script itself.

You are going to need RSTAB to check it.

Thanks in any case. Very valuable help

Attachments:

• RhinoRStabInterop.dll, 10 KB
• PythonLinesTest.py, 1 KB

Permalink Reply by Steve Baer on February 7, 2013 at 8:43am

Hi Manuel,

If you wrote the interop DLL, I would recommend debugging it from visual studio and placing breakpoints in the functions/constructors that you are calling from python.  In your DLL project, set the start up application to be Rhino and you should be able to debug your functions once you run your grasshopper solution.

Thanks,

-Steve

Permalink Reply by Manuel Sotomayor Millan on February 7, 2013 at 11:34pm

Thank Steve.

Yes I wrote it, and i also was debugging it from visual studio, but at some points what was working in Visual Studio was not working on python Editor.

Anyway, when I try to debug from Visual Studio I get the following message:

DisconnectedContext was detected
Message: Error en la transición al contexto COM 0x413d88 para este RuntimeCallableWrapper: El objeto invocado ha desconectado de sus clientes. (Excepción de HRESULT: 0x80010108 (RPC_E_DISCONNECTED)). La causa más probable es que el contexto COM 0x413d88 en el que este RuntimeCallableWrapper se creó se haya desconectado o esté ocupado haciendo cualquier otra cosa. Liberando las interfaces del contexto COM actual (contexto COM 0x413c60). Esto puede ocasionar daños o pérdida de datos. Para evitar este problema, asegúrese de que todos los contextos, apartamentos y subprocesos COM se mantengan activos y estén disponibles para la transición de contexto hasta que la aplicación haya terminado completamente con el RuntimeCallableWrappers que representa a los componentes COM presentes en su interior.

Attachments:

• Untitled-1.jpg, 165 KB

Permalink Reply by Manuel Sotomayor Millan on February 7, 2013 at 11:35pm

Maybe that is a bit too much anyway.

Thank you very much.