RFC_VMC_COMMUNICATION_ERROR is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: F - Installation Errors
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Check whether the VMC is active on your application server. To do this,
run transaction SM52. If the VMC is not active, contact your SAP
administrator.
Parameter....: <runtime parameter>, <runtime parameter>
Error during VM Container communication between ABAP and JAVA.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
An error has occurred in the RFC layer during communication between
JAVA and the ABAP stack. This prevents data from being passed correctly
between the two stacks.
Message = <runtime parameter>
Return code = <runtime parameter>
Pointer = <runtime parameter>
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
Error in the RFC layer.
RFC_VMC_COMMUNICATION_ERROR - rfc vmc communication error RFC_SCRAMBLE_UNDEFINED_LENGTH - rfc scramble undefined length RFC_SCRAMBLE_PARAMETER_FAILURE - rfc scramble parameter failure RFC_SCRAMBLE_LENGTH_TOO_LONG - rfc scramble length too long RFC_NO_AUTHORITY - rfc no authority RFC_IOHANDLE_TOO_SMALL - rfc iohandle too small