on 12-02-2009 9:56 AM
Dear colleague,
I'm using the Visual Studio 2008 Express edition to create a silver light application. When calling a web service created in net weaver platform, I got the following error:
Following are the detail error message. Can anybody tell me where goes wrong?
'Unrecognized message version'.
System.ServiceModel.CommunicationException was unhandled by user code
Message="Unrecognized message version."
StackTrace:
at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)
at TestAbapWebService.ServiceReference1.ws_ssc_usr_get_user_listClient.ws_ssc_usr_get_user_listClientChannel.EndSscUsrGetUserList(IAsyncResult result)
at TestAbapWebService.ServiceReference1.ws_ssc_usr_get_user_listClient.TestAbapWebService.ServiceReference1.ws_ssc_usr_get_user_list.EndSscUsrGetUserList(IAsyncResult result)
at TestAbapWebService.ServiceReference1.ws_ssc_usr_get_user_listClient.EndSscUsrGetUserList(IAsyncResult result)
at TestAbapWebService.ServiceReference1.ws_ssc_usr_get_user_listClient.OnEndSscUsrGetUserList(IAsyncResult result)
at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)
InnerException:
Hi Anders,
directly invoking from a Silverlight control via WCF proxy a SAP BAPI webservice can be "challenging"; reason is that Silverlight only supports a subset of the WCF functionality yet, and also SAP BAPI webservice are limited in only supporting WS-Basic profile.
I succeeded in invoking from a Silverlight control SAP BAPI webservice; but in the system architecture I placed an intermediair .NET WCF webservice (*):
1. Silverlight invokes the .NET WCF webservice (this already has it's challenges, with AsyncResult, binding, [custom channel|http://williamvanstrien.blogspot.com/2009/07/silverlight-and-wcf-faults.html])
2. .NET WCF webservice invokes the SAP BAPI webservice.
(*) I had some other architectural reasons in the beginning for placing the intermediair WCF webservice between client and (SAP) webserver; and later on when connecting via a Silverlight based client it proved helpful for some Silverlight peculiarities also ==> had to make some changes both in my Silverlight WCF pipeline, as on the .NET WCF webservice side.
Best regards, William.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have the same error, using a full 3.5 WCF. My binding in the config file looks like this:
<binding name="CustomHttpTransportBinding">
<textMessageEncoding maxReadPoolSize="64" maxWritePoolSize="16" messageVersion="Soap11" writeEncoding="utf-8">
<readerQuotas maxDepth="10000000" maxStringContentLength="10000000" maxArrayLength="67108864" maxBytesPerRead="65536" maxNameTableCharCount="100000" />
</textMessageEncoding>
<httpTransport authenticationScheme="Basic"
bypassProxyOnLocal="false"
hostNameComparisonMode="StrongWildcard"
keepAliveEnabled="false"
proxyAuthenticationScheme="Basic" realm="SAP Web Application Server [HU2]"
useDefaultWebProxy="true" />
</binding>
Thanks!
Michel
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.