Question
Accenture
PH
Last activity: 5 Jan 2017 22:49 EST
Error Message encountered "Server was unable to process request"
Hi,
We need assistance for this encountered issue. When we tried editing a work item we encountered the following error message:
"Server was unable to process request. Object reference not set to an instance of an object"
Please let me know for the actions required from our end to fix this issue. We are all relatively new to PEGA Developer role.
You may see the attached screenshots for reference.
Thanks,
Dar Ganata
***Updated by moderator: Lochan to update Categories***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
Is there a stack trace in the log? What do you see in Tracer when trying to edit the item?
Accenture
PH
Hi,
Thanks for your response. I'm really sorry since im not familiar with the tracer tool. Please see the attached file for the screenshot of the Tracer when i tried clicking the Edit button.
Please guide me for the steps i need to resolve this issue.
Thanks so much.
Pegasystems Inc.
US
It looks like a SOAP service is being invoked. Is the error occurring in the SOAP call?
Accenture
PH
Hi,
Yes you are correct. Upon checking the Tracer there is a FAIL step on the SOAP activity.
Thank you so much for your help, please we'll be needing your guidance to solve this issue.
Please see attached document for reference.
Thanks,
Dar Ganata
Pegasystems Inc.
IN
click on 8th & 15thy steps of rule-connect-soap rule from the tracer, send us.
Pegasystems Inc.
US
When you click on the Fail rows in Tracer, what is the error message?
Accenture
PH
Hi Pyla,
Please see attached files for the steps and actual source code.
Thanks,
Dar Ganata
Pegasystems Inc.
US
Hello Dar,
In your tracer screen shots, there are places where you see the word "Fail" in a red box. If you click on that, a window should pop up, hopefully telling you more about the fail. Can you click on the first one of those (presumably the later failures are as a result of this first one, although if you find that the error changes as some point, you could include that as well, along with whatever context you can muster)? The activity InvokeAxis2 fails at a Java step, so hopefully the error will help you figure out exactly where the java code is tripping up.
If you are comfortable going into the java, you can do a private checkout of the activity and add oLog.infoForced("debug statements"); to the code to get more insight into what's going on. That will write your custom message to the logs when you run the activity.
Thanks,
Mike