Error: Server was unable to process request. --- Object reference not set

Question

Hi All,
I am using ALSB 2.6.
In the project, i have requirement to do transformation of incoming request with CData Tag and getting a response from the remote service.
I have configured the Proxy Service and Business Service with a message route in which transformation is happening using replace action and adding a XSLT there.
While sending the request from ALSB Test Console , its doing the transformation correctly as follows:
Transformed Request at ALSB
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<lif:MultipleTermLifeQuotePublic xmlns:lif="https://www.farmerslife.com/LifeNetWS/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<lif:xmlInput>
<TERM_LIFE_RATE_QUOTE>
<Quote_Request Quote_Sequence = "100">
<Face_Amount>
1000.00
</Face_Amount>
<Gender>
male
</Gender>
<Age>
100
</Age>
<Level_Term_Years>
100
</Level_Term_Years>
<Type>
string
</Type>
<Nicotine>
true
</Nicotine>
<CIR_Amount>
1000.00
</CIR_Amount>
<State>
string
</State>
<Waiver_Premium>
false
</Waiver_Premium>
</Quote_Request>
</TERM_LIFE_RATE_QUOTE>
</lif:xmlInput>
</lif:MultipleTermLifeQuotePublic>
</soapenv:Body>
After transformation, when its passing through Business Service its giving the followin error at ALSB console
<soap:Body xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>
Server was unable to process request. ---> Object reference not set to an instance of an object. </faultstring>
<detail/>
</soap:Fault>
</soap:Body>
[b]When i am sending the same request through SOAP UI, I am getting a correct response.
Can any one guide me what to do regarding this, where i am going wrong.
Please try to reply as soon as possible. Its an urgent issue.

Answer 1

That error you're getting is a typical error message from Windows web services. It simply means there was something unspecified that was wrong with your message. You'll need to find a way to extract the actual message being sent in both the "good" and "bad" cases and look at the differences. You can do that in ALSB with a "Log" action.