Solution : https://service.sap.com/sap/support/notes/87585 (SAP Service marketplace login required)
Summary :
When an ABAP program controls an OLE automation server, users may encounter a "Server busy" dialog, commonly followed by R/3 message SY002. This occurs due to the server not completing prior calls or being occupied with other tasks (e.g., opening a large or corrupt file). Key operations affected include object creation and method calls in applications like Excel or Word hosted on network servers. To manage this, SAPgui's default settings trigger a dialog after 8 seconds, which can be adjusted using parameters in FRONT.INI or Windows Registry. Preemptive patching (for early SAP releases) and setting adjustments help mitigate these issues, aiming to enhance process handling without expediting the underlying operations. For detailed management, users can modify wait times through specified registry entries or INI file configurations.
Key words :
hkey_current_user\software\sap\sapgui front\sap frontend server\customize, 1 profileparameter gw/cpic_timeout default 60 sec 2 property/registryeintrag automation, /general/frontend/patches/rel31h/windows/win32/front_z, /general/frontend/patches/rel31i/windows/win32/front_z, /general/frontend/patches/rel40b/windows/win32/front_z, unexpectedly long processing server calls trigger, retryreply default 10 secthe automation controller attempts, input field 'automation timeout', network link local installation, additional key words abap
Related Notes :
| 96885 | Downloading front end patches |
| 73056 | Collective note: ABAP as OLE Automation Controller |