Security issue from Sharepoint Duet to SAP Gateway for Response Message

[Former Member]

Hi,

Sharepoint is in 2010,

.NET is in 2.0

We recently upgraded SAP Gateway from 731 to 740, and exported upgraded BDC models and imported them into SharePoint.

When we are running the BDC models, we are having below error at sharepoint side(Client side).. In the trace, we found that the request is coming to SAP and when the response sent back to Sharepoint, it is throwing this error.

Error at sharepoint side:

/// Unexpected error occured. View event viewer for more details. Security processor was unable to find a security header in the message.

This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties. This can occur

if the service is configured for security and the client is not using security ///

Also we found that the only difference we found between Old BDC model and new BDC model is in Property Name="WcfMexDocumentUrl"

Before upgrade:

<Property Name="WcfMexDocumentUrl" Type="System.String">https://gatewaytest.com/sap/bc/srt/wsdl/bndg_0050568E01AD1ED4959D7C5F77F4610E/soap12/wsdl11/allinone...</Property>

After upgrade

<Property Name="WcfMexDocumentUrl"Type="System.String">https://gatewaytest.com/sap/bc/srt/wsdl/flv_10002A111AD1/bndg_url/sap/bc/srt/pm/sap/ziwxzfi_ccodeszf...</Property>

Any idea whats need to be done to resolve this issue.

Thanks

[valentinbabias]

Hello:

We have the exact same issue. We have upgraded our SAP Duet/Gateway environment to NetWeaver 7.4 SP9 and Duet Enterprise 2.0. While investigating the issue we observed that the actual request is received and processed (we setup payload trace in SRT_UTIL transaction) so we can see the query results in the response but for some reason the response is rejected by SharePoint.

Please share the solution if you managed to find one or if you have a possible workaround.

Thank you,

Valentin

[Former Member]

Hi,

could you please take a look at this Note 2120717? There was a change in SOAManager which caused this issue.

Regards,

Holger.

[valentinbabias]

Hello Holger,

Thank you for your reply. The note 2120717 is already implemented in our system. After upgrade we are at SAPKB74009.

Regards,

Valentin

[Former Member]

Hi Valentin,

can you create a ticket for this? There are a few related notes, but ideally after implementing note 2120717 the BDC generator and the import into SharePoint should have worked again.

Regards,

Holger.

[valentinbabias]

Hello. The issue was resolved by implementing SAP note 2180079.

Regards,

Valentin