"Server Busy" window blocking control

Hello Forums,

when I edit a file in Grasshopper, it doesn't take long before I get this popup, which tells me, that some application is busy and I have to wait. When I click the "Switch to..." button, the Windows start menu opens up (the same like using the Windows button on your keyboard).
Whenever this error occurs, I can change the view in Grasshopper and enter commands within Rhino, but the views within Rhino don't update and that "Server Busy" windows is on top all the time. I cannot close Grasshopper and/or Rhino without loosing data, so this is annoying.
Has anyone experienced something similar? I could not find a solution to this.

I am using Rhinoceros with Grasshopper on a virtual WinXP x64 machine, namely VirtualBox (v 4.1.8), so I don't know if the issue has to do with Grasshopper, Rhino or the VM, but I presume that this has to do with Grasshopper.

Attachments:

screen.png, 203 KB

▶ Reply to This

Replies to This Discussion

Permalink Reply by David Rutten on February 28, 2012 at 4:14am

I have seen this a number of times with all kinds of applications on different versions of Windows. Usually if I wait for a bit the message goes away, but sometimes I have to kill the application via the Task Manager.

I don't know what causes it and I certainly don't have a solution. If there's some steps that allow me to repeat this on Grasshopper then I can try and look into it deeper, but in my experience this Server Busy crap is quite unrepeatable.

David Rutten

david@mcneel.com

Poprad, Slovakia

▶ Reply

Permalink Reply by Jon Mirtschin on February 28, 2012 at 4:21am

I can't really help with making the process faster or with patience to wait, but you can at least suppress some of these warning messages using this rhino common method:

Rhino.Runtime.HostUtils.DisplayOleAlerts(false);

▶ Reply

Permalink Reply by Thorsten Strathaus on February 28, 2012 at 5:31am

Exactly John,

this did help me when using VB.net code to communicate with Excel and others.

Just add this line into your code and you should be fine.

Thorsten

▶ Reply

Permalink Reply by Julius on March 1, 2012 at 6:22am

Thanks for all the replies.
This behaviour seems to be quite unrepeatable. Sometimes it happens, sometimes it doesn't.
Sorry, but I don't know where to put that line. I don't have any VB/C# code blocks yet. Should I simply create one for sole purpose of hiding OLE alerts? And how should I connect this?