NR Error during 3 hr open-loop stimulation experiment

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open NR
2. Adjust settings for voltage stimulation using open-loop stimulation protocol.
3. Start stimulation protocol.

What is the expected output? What do you see instead?
I expected the experiment to run to completion, but instead I got the error 
attached 20 minutes in.

What version of the product are you using? On what operating system?
NeuroRighter V1.1.0.542
Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by SwimminQ...@gmail.com on 27 Nov 2012 at 5:43

Attachments:

• [NR error 3.png](https://storage.googleapis.com/google-code-attachments/neurorighter/issue-72/comment-0/NR error 3.png)

[GoogleCodeExporter]

1. Are you compiling NeuroRighter or using the binary version?

2. Please paste the text of the error message into your bug report.

3. Please provide the stimulation scripts that you were using when this error 
occurred.

4. Did you log out of your account while running this experiment? Did you 
computer automatically log out or lock?

Original comment by jonathan...@gmail.com on 29 Nov 2012 at 3:20

[GoogleCodeExporter]

Looks like it was just running through visual studio.

This post- <http://managedupnp.codeplex.com/discussions/276221> seems to 
indicate that these COM object switch errors don't have an effect on the 
compiled code, and so the best response is to simply disable reporting of these 
bugs.  Obviously that doesn't 'solve the problem', but we'll monitor the issue 
with that reporting disabled and see if additional problems are caused.

text of error:
Transition into COM context 0x42e920 for this RuntimeCallableWrapper failed 
with the following error: System call failed. (Exception from HRESULT: 
0x80010100 (RPC_E_SYS_CALL_FAILED)). This is typically because the COM context 
0x42e920 where this RuntimeCallableWrapper was created has been disconnected or 
it is busy doing something else. Releasing the interfaces from the current COM 
context (COM context 0x42e7b0). This may cause corruption or data loss. To 
avoid this problem, please ensure that all COM contexts/apartments/threads stay 
alive and are available for context transition, until the application is 
completely done with the RuntimeCallableWrappers that represents COM components 
that live inside them.

Original comment by RZellerT...@gmail.com on 3 Dec 2012 at 7:38

[GoogleCodeExporter]

Original comment by jonathan...@gmail.com on 10 Dec 2012 at 3:31

• Changed state: WontFix