Cisco Cisco Tidal Enterprise Scheduler 6.2 Brochure
Cisco Systems, Inc.
www.cisco.com
www.cisco.com
Controlling RPC Errors
June 6, 2014
Problem
Certain customers experience RPC errors randomly (codes 12002, 12019, 12152 etc) while
using 6.x Web client.
The RPC errors are primarily driven by CM/Master and/or Network performance issues. If the
CM/Master/Network takes more than default 30 seconds to respond, client gives RPC errors. In order to
avoid this, timeout/keep-alive related parameters need to be increased both in web server configuration
and IE/Firefox browser.
CM/Master/Network takes more than default 30 seconds to respond, client gives RPC errors. In order to
avoid this, timeout/keep-alive related parameters need to be increased both in web server configuration
and IE/Firefox browser.
Solution
Increase the timeouts in server and IE Browser as follows: First step is to be done on CM server
and second one is to be done by any user of TES using IE browser and third (optional) one if using
Firefox browser.
Firefox browser.
Step 1
Change maxIdleTime (from 30 seconds to 120 seconds or higher) in webserver.xml file in CM/config
folder.
folder.
<Set name="maxIdleTime">30000</Set> change to <Set name="maxIdleTime">120000</Set>
Note
This setting is in two places – one under SSL section, update both places (particularly important
if SSL/HTTPS is being used).
if SSL/HTTPS is being used).
Step 2
Add a KeepAliveTimeout for IE Browser:
a.
Click Start, click Run, type regedit, and then click OK.
b.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings
c.
On the Edit menu, point to New, and then click DWORD Value for 32 bit
Note
For 64-bit browsers/users, select QWORD or if in doubt, add both.
d.
Type KeepAliveTimeout, and then press ENTER.
e.
On the Edit menu, click Modify.