cancel
Showing results for 
Search instead for 
Did you mean: 

SAP.Connector.RfcException: Element ES_XXX of container metadata FUBA_YYY unknown

0 Kudos

Hi Everyone,

We are having a problem on a P system:

2014.11.20 09:16:31:608: SAP.Connector.RfcException: Element ES_XXX of container metadata FUBA_YYY unknown ---> SAP.Middleware.Connector.RfcInvalidParameterException: Element ES_XXX of container metadata FUBA_YYY unknown

   bei SAP.Middleware.Connector.RfcContainerMetadata`1.NameToIndex(String elementName)

   bei SAP.Middleware.Connector.RfcXRfcParser.ProcessBeginTag()

   bei SAP.Middleware.Connector.RfcXRfcParser.parse()

   bei SAP.Middleware.Connector.RfcConnection.ReadRfcXmlData(RfcFunction function, RfcParameter& param, Int32 length)

   bei SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)

   bei SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)

   bei SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)

   bei SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)

   bei SAP.Middleware.Connector.RfcFunction.RfcCallReceive

   (RfcConnection conn)

   bei SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)

The problem is not reproducible on a Q system. I have seen posts with similar problem, but in our case the exception is thrown from the RfcFunction.Invoke() method.

The ES_XXX is an exporting by value structure. Both functional modules in both P and Q systems are identical.

Does anybody know what could be the reason?

Thanks in advance!

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Well, the reason is detected. Somehow the RFC user caused the problem. When we logged in under another (dialog) user, the problem was gone. We asked the customer to provide us information what settings were different for those both users. I will post it here as soon as get it (what can take long). So I would very appreciate if anyone could share his/her knowledge on this problem.

MarkusTolksdorf
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Michail,

actually, this means that the metadata does not fit to the received data. This can also happen, if the user looking up the metadata has insufficient permissions - though it normally should lead to an exception already at lookup time.

Best regards,

Markus

0 Kudos

Hi Markus,

You are right, insufficient permissions was the reason. The problem was solved when the customer added the following parameters:

Answers (0)