Hi everyone,

XP Pro SP1, Mappoint 2002, VB6 SP5,

I have a PC running exclusively a tracking system 24 hours a day displaying vehicle’s movement on a map. A few times a day, the application crash giving a Mappoint unexpected error saying “Server busy” asking to “Switch to” or “Retry”. In the program, I’m capturing the error, not always at the same place, but always referring to the map, and I can’t regain control of the program because of the ‘Switch to’ message. No matter what I try, I have to shutdown the application using ‘Task Manager’ and then restart the PC to reuse Mappoint’s control object.

Does anyone have any suggestions or encounter this type of error? Can I avoid having that message showing? What does the ‘Server Busy’ really mean?

You cant avoid having that message show. Your going to have to narrow it down and when you do if you post the code that you think is doing it we might be able to help.

Also I know its been talked about alot here in this forum so if you did not already search here give that a try.

When I've seen this message it usually is code that uses one of the events so look there first.

actually the error is generated by the timeout expiring but not releasing the control thread back your app in a timely manner..


this can be resolved with any COM based object in VB by adding the line

App.OleRequestPendingTimeout = TimeInMiliseconds

to the length needed for the query....

Thanks you both,

I've increased the default value of OleRequestPendingTimeout and it's been running for the last few days.

Thanks again,

Sylvain

Does anybody know how can I solve the problem in .net. I'm implementing an application in C#.net and when I try to show a DialogForm it appears the error message "Server Busy ..." Please tell me how to solve it!

Thanks everybody!!!

hey umm....i dont know much about comps so umm....i have the server busy problem too like sylvania....whats App.OleRequestPendingTimeout anyways....?

is anybody gonna answer me?

Didn't see your post the first time around.

It is a property setting for COM.
So if you're using Visual Basic, you need to use that line.

For other languages, you'll need to look at your 'calling COM' documentation.

For MFC I think I read somewhere that it was hard-coded but I'm not sure.
It isn't something I've need to change - I've only seen the error in one circumstance, when running batch jobs in the background and test/developing in the foreground.

A faster PC would help as well!


RB

where do u find that documentation?

Well what language are you using?

For some, try searching the web. Eg. I think Perl has a library to do it.

For a Microsoft language, then MSDN (on their website) is probably a good place to start.


Richard