CORBA error knock-on effect on AJS

CORBA error while communicating with the SL Service

This is a well-documented error for large WebI reports based upon SAP B/W via Bex. For example, the master KBA https://launchpad.support.sap.com/#/notes/2354666
In my client’s case, they are not so fussed about the error, but rather the after-effects. What they see, after a large WebI report based upon SAP B/W has been scheduled and failed, is a job server that appears to be functioning normally, but anything sent to it just stays in Pending. It takes a Force Termination and Start to bring it back, at which point it is fine…until the problem report is scheduled and fails again. At which point, AJS is incommunicado.
Has anyone experienced anything like this?


Nick Daniels :uk: (BOB member since 2002-08-15)

Bump. Anyone?


Nick Daniels :uk: (BOB member since 2002-08-15)