Salesforce Schedule Processer No Worky

mbarben · 2023-01-09T23:02:50+00:00

There was an error rendering this rich post.

Hi Guys,

We recently came across an issue whereby the Schedule Processor (processing document moves from Salesforce to OT) just stopped and now reporting an error:

Block could not be extracted - error: com.sforce.ws.SoapFaultException: No service available for class 'ECMLinkSPI'

From the SF side:

the package is correctly deployed
the login entries are successful
the user account has the correct Permission Sets applied.

And the on the CS side:

Business Application connects fine (version of 52 of the API)
Workspaces are still being created
And we have even re-created the Scheduled Processor job.

We are not seeing logs turn up on the sfecmlink-spi_Network.log file but we are seeing them in the xecmpfbulk.log

We have raised a ticket with support - but just reaching out to the community to see if anyone else has run into this kind of issue before.

Thanks Again

Matthew

Find more posts tagged with

xECM for Salesforce

Comments

mbarben

Small update - looks like the call to the queryDocumentObjectsBulk method returns a fault that the

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
        <soapenv:Fault>
            <faultcode>soapenv:Client</faultcode>
            <faultstring>System.LimitException: Apex heap size too large: 6852434


External entry point</faultstring>
        </soapenv:Fault>
    </soapenv:Body>
</soapenv:Envelope>

Alas, this is a managed app so I am not able to poke inside to determine how/if it is attempting to manage the heap size

appuq

If I am not mistaken the amount of Objects for the Distributed Agent is throttle-able by setting parameters appropriately. One goes to the place where you set up the job and apply some business logic. This screencap is from our product Extended ECM for IBM Maximo. https://www.qellus.com/qellus-extended-ecm-for-maximo

Not familiar with SF but if you can get to the screen I would think you can control the "gulp"

mbarben

Hi Appu,

Turns out there is a specific issue related to the 1.190.9 version of the OT package on Salesforce. The query limit in the package was hard-coded to 9000 - but because there are 5 queries per call if you have a backlog (for us it is about 11lk) then that will equate to about 55k worth of calls which then hits the global query limit within Salesforce.

And given that this is happening at the start up there would be no way to even start processing the backlog down or adjusting the page size

There is a patch - thankfully. Now to perform the regression testing dance.