Automation Addin Time Out Problems

[daharper]

Hello,

I've written an EA Addin which takes about 7+ secs to complete. Before completing a windows prompt notifies me that the Server is Busy - I can select 'switch to' or 'retry'. After clicking retry, the Addin finishes okay.

Does anybody know if there is a way to avoid this? Not sure if it is an EA or a COM+ issue.

Thanks in advance for any help!

[thomaskilian]

A bit too few detail to give actual help. I assume it's not an EA issue. Maybe you could state a bit more about the message box (screenshot?).

[Uffe]

I've seen this message pop up now and again too, when doing nothing very much in EA. It's a Windows error message and it reads "This action cannot be completed because the other program is busy. Choose Switch to, Retry or Cancel to activate the busy program and correct the problem." The dialog title reads "Server busy."

However, you are not told which server is busy doing what, so it's not a lot of help. As I say I have seen it too when using EA (sorry I can't be more specific, it's highly intermittent), and after randomly going "Switch to" and "Retry" a few times it seems to sort itself out.

[Mr. Sanders]

Hi,

as far as I know this, it is a general COM/DCOM timeout problem. I think the dialog is raised by from the SCM (service control manager) when a timeout occures on an COM/DCOM call.

You are right, you can not find out which com server is currently having the problem.

I am not sure if the timeout is configurable for the com calls. Maybe another expert here for COM/DCOM/COM+ configuration? I left this subject years ago behind me.

May be you see in a process explorer who is taking cpu time, or something like that. And may be in addition with antother hint you can configure this timeout.

I will have look at the microsoft msdn if I can find something and will be back when I have found something worthy to mention.

Michael

[thomaskilian]

That's simply bloody Windoze. Two COMs waiting for each other. Eventually one of them has some "doEvents" inside to unblock. Just blame Bill.

[daharper]

Yup,

I suspect the same thing, a COM+ time out. Unfortunately, I too left COM development as soon as I could

My guess is EA is calling my C# code via interop, and the 7-10 second response delay is causing the timeout. Wasn't sure if there is a setting for this.

I'm thinking of threading the request, since I have the Repository I can return control to EA and work in the background.

Thanks for your feedback, appreciated. If I can find the problem in msdn I'll be sure to post it.