How to Debug RPC_E_SERVERFAULT

[jangroetzner]

Hi all,

while developing an addon which creates many business documents (more then 50) within one transaction we often get this COM-error RPC_E_SERVERFAULT exceptions. But not always. And not on the development system but always on the customers system.

I'm looking around all these posts in here and there is always say, try this, try that, delete temp-folder, reinstall DIAPI, ...

Is there no exception handling within DIAPI or logging mechanism or stack trace to get the reason for this RPC_E_SERVERFAULT? Is it database dead lock, an out of memory, a version conflict, a timeout?

RPC_E_SERVERFAULT is so global.

Any help appreciated.

Best regards

Jan

[maik_delly]

Hi Jan,

identify such issues is always a hard task. If the error is reproducible - meaning same transaction always leads to same outcome - you may be able to find the cause easier,

If not, and your text suggests that, you have to dig deaper. First step should be to check and understand DI API logs. Also using SQL profiler can hint to the right direction. Since you say, the problem doesn't occur on development system, check for different system setups - often dev environments are one-machine only -> rule out network related issues for productive.

In the end, SAP support would be the right contact - but it would be much easier to provide a reproducible proof of concept.

best regards,

Maik