Quantcast
Channel: SCN: Message List - SAP NetWeaver Technology Platform
Viewing all articles
Browse latest Browse all 4415

Re: Problems with calling webservice after system upgrade.

$
0
0

Hi Lev,

 

That's strange indeed, because the same solution should re-generate a new "binding key", and that was the root-cause to your problem, WS having the old binding key.

And you did get the same error prior to transporting to QAS?

 

>>  and error text <no error message available>:  

     ("Message "ZlibIndReadTblsCommonMass{urn:sap-com:document:sap:soap:functions:mc- style}"  

     not supported (interface: "ZLIB_FG_WS" binding key: 

     "50B1FBB961DA0459E10000000A840FEE")") (fault location is 1  ).</TEXT> 

 

Another check: Did the transport went OK (RC=0 or 4)? Did all objects activated correctly after the transport? Did you include everything in that transport which needed for those WS?

 

Regards,

Andre


Viewing all articles
Browse latest Browse all 4415

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>