CDR Tickets

I found this post on the Microsoft knowledge base that could possibly be of use.
https://support.microsoft.com/en-us/kb/240809
How to prevent the "Switch To" or "Application Busy" error messages using OLE Automation

I read this post but I have to admit I was lost at step #1 🙂. I do think it's worth investigating though because we continue to get this message on a daily basis and some users have had to resort to using Task Manager or rebooting their computer in order to resolve it.

If you could collect any additional information on when this is happening that would be great. I am reading about possible causes and possible fixes but since I can't recreate the problem I'm unable to test a proposed fix.
If we could identify certain situations when the problem shows up that could help. I'm thinking at things like "Always happens on Monday mornings", "It happens between 5-6pm", "it happens when Word is open", etc.

Here is some information from Intuit because users of their QuickBooks are experiencing the same problem and they identified the following possible causes:

Why this is happening
A number of issues can cause QuickBooks to pop this error message. Among them are:

• Another program that QuickBooks is trying to work with is waiting for a response from you.

• Windows Update is running in the background.

• QuickBooks or some of its components did not completely shut down last time you closed it.

• Multiple computers are setup to host the QuickBooks company file.

• A firewall or other security software is blocking QuickBooks updates.

• A conflict occurs between the QuickBooks update manager and another program on the computer.

• A *.qbi file is locked (QuickBooks 2005 only) or more than one computer is configured to host the company file.

• A Conflict with Intuit ProSeries may cause a conflict.

• Your network does not have sufficient resources to run QuickBooks.

Here is another post addressing the same type of problem reported for cuteFTP:
http://kb.globalscape.com/KnowledgebaseArticle10441.aspx
with the following quote:

The “Server Busy” message is a Windows error prompt, NOT a CuteFTP message.

This message appears whenever there is a resource conflict between two processes in Windows and one of the processes will not release the required resource so that it can be used by another process.

I suggest to submit a HelpDesk ticket for the user getting this message the most and have the support team take a stab. The post suggests that a specific program may cause the conflict.

My next step for this ticket will be to revive the code to launch the user's preferred browser instead of automatically launching IE, not as a solution to the problem but as an effort to glean more information about the problem and its causes.

I just thought I'd report that I'm still getting the "switch to" error today. I think we were hoping Friday's update might resolve the issue.

We were hoping for that (though not as optimistically after we learned that throttling the delay for waiting for the switch down to a couple of milliseconds didn't cause the problem to occur). Oh, well. :-(

~mbeckwit, ~juther, and ~oseipokuw: I have had CBIIT deploy a new DLL to STAGE. Please do some testing on STAGE of the buttons/menu items which launch reports or the admin interface from XMetaL. If it looks like the "switch-to" problem has been resolved (and I haven't broken something in the process), we'll get them to deploy it to production.

This is going pretty well on Stage (I haven't seen the "Switch to" error at all!), but I can't pull up a Bold/Underline, RLSO, or PP report for the Genetics of Breast/Gyn summary (CDR62855). I'm getting a Page Cannot Be Displayed error for each of these. I was able to generate these reports for other summaries.

I'm unable to reproduce the failures for that document, though it does take a very long time. Are you able to run the reports directly from your browser (so, bypassing XMetaL and the DLL)?

I was able to get the bold/underline to come up after a few more tries, but I still can't get the RLSO or PP to come up (using the toolbar icon or directly in the browser).

Well, that's sort of good news, at least for this ticket, as it means that the problem you're running into is unrelated to the change to the DLL. Please open a separate ticket for the GBG summary failures (and include specific error messages and times).

Thanks.

Good news - Margaret's tests were also successful (no "switch to" errors), so I think we can ask CBIIT to promote this change. Thanks!

The fix has been installed on PROD. Please verify that the problem has been resolved.

Verified on PROD. Thank you!