STYLESHEET_GENERATION_FAILURE Attempt to generate transformation required

[Former Member]

Hi,

Since regeneration of one specific proxy, we have been getting the following error occuring with calls to it:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Call Inbound Proxy -->
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" 
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 
SOAP:mustUnderstand="">
	<SAP:Category>XIProxy</SAP:Category>
	<SAP:Code area="ABAP">
STYLESHEET_GENERATION_FAILURE
</SAP:Code>
	<SAP:P1/>
	<SAP:P2/>
	<SAP:P3/>
	<SAP:P4/>
	<SAP:AdditionalText/>
	<SAP:ApplicationFaultMessage namespace=""/>
	<SAP:Stack>Attempt to generate transformation required 
for rendering/parsing failed (, class , method  )
STYLESHEET_GENERATION_FAILURE Attempt to generate transformation required 
for rendering/parsing failed (SAVE_STYLESHEET RC_5, class ZXI_II_ECC_BPSD_ASYNC_IN, 
method EXECUTE_ASYNCHRONOUS /1SAI/TXS00000000000000000004)
Attempt to generate transformation required for rendering/parsing failed 
(SAVE_STYLESHEET RC_5, class ZXI_II_ECC_BPSD_ASYNC_IN, method EXECUTE_ASYNCHRONOUS
/1SAI/TXS00000000000000000004)
</SAP:Stack>
	<SAP:Retry>M</SAP:Retry>
</SAP:Error>

When debugging the ABAP the problem appears to be with the following call:

Class CL_AI_RUNTIME_TEST
Method SERIALIZE_PARAMETER
              me->serialize( ).
18                 l_xslt = cl_proxy_stylesheet_runtime=>create_from_method(

We have tried:

Deleting queues.

Regenerating the proxy.

Deleting and recreating the proxy.

Restarting the server.

This is XI7.0, using the graphical mappings and nothing special in the schema. The error message above appears in the ECC system after approx 10 minutes of green-flag processing. Fortunately this is a development system!

Any ideas?

Thanks,

James.

[former_member189354]

Hi,

Once you regenerated the proxy I think you just "Activated the Proxy" But you need to

activate all the components of the Proxy. Just select the "Activate All" under Proxy menu.

Regards,

Daniel.LA

[Former Member]

Note 1060627 appears to have fixed the problem.

James.