• Replies 1 reply
  • Subscribers 136 subscribers
  • Views 932 views
  • Users 0 members are here
Options
Related

Tridion Docs 13 SP2: Server busy ('switch to' or 'retry') error when using the SDL Authoring Bridge

Paul Arellanes

Hello SDL,

We have about 30 users who are regularly getting a "Server busy" ('switch to' or 'retry') error when they try to do several actions that involve the SDL Authoring Bridge.

One example is when users are using XMetal 12 with the SDL Authoring Bridge to connect to the Tridion CMS. When the users open the Browse Repository and try to use the Search tab, they will get that message.

Another example, is when users are using the SDL Publication Manager, select Browse Repository, and then select to open an object like a map, or a topic.

We understand this is a Windows error message, however, the users who are experiencing this problem only get this error when trying to work with the Tridion CMS through the Authoring Bridge.

thank you

paul 
Rate translation
×
Suggest better translation
×

  • Hi Paul,

    Quite a while since I saw this one, in essence a "Server busy" is an absolute timeout. As you know, there are many things that can cause an absolute time out. Anything in the full chain from Client OS, XMetaL, networking, application server or database server can cause a timeout - but also the information architecture could be atypical causing extra loading effort that goes beyond the timeout.

    High level explanation...
    The Server which is busy is actually a OLE Server. XMetaL uses (js) scripts that are hooked on to menu buttons. These script do calls to ActiveX objects. If a call takes too long Windows detects this and shows the Server is Busy error dialog. So it is a local – in XMetaL – time out. It can still be caused by a request to the SDL server taking to long but it is the OLE Server that is not responding fast enough.


    As a throwback moment, see https://forums.xmetal.com/forums/topic/server-busy-message/
    So you can attempt increasing the ole_server_busy_timeout = 60000 (60s) in the xmetal...ini file (program files folder)

    If this doesn't help, then the analysis starts

    1. When did it start appearing? What changed? Any hotspot moments during the day?
    2. Which users have the problem, and which do not... does could even be about multi-monitor setups... or heavy ALT-TAB usage
    3. It could be about OS versions, patches, new antivirus, etc
    4. A typical reproduction scenario
    5. etc

    Hope this helps,
    Dave