Change Password IIP failed

This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Post Reply
pravik
Posts: 60
Joined: Tue Dec 26, 2017 6:44 pm

Change Password IIP failed

Post by pravik » Fri Jan 19, 2018 6:30 pm

Hi All,

In the latest version of VLF_one, we have plugged in change password along with logon. Upon referring previous posts regarding similar issue we have checked below points:

- We created a copy of UF_OLOGON and give it the name TST_LOGIN_AUTH and its identifier being TST_LOGI and this name was only specified in WEB/RAMP
- This component has extended #VF_AC027O
- Changed #UseFrameworkObjectAuthority := True

Yet we are receiving similar errors:

1) Please check server logs.
2) call to change password IIP failed.

kindly guide me in rectifying this error message.

Thanks & Regards,
Priya

jyoung
Posts: 643
Joined: Thu Jan 21, 2016 6:43 am
Location: Oklahoma City, OK USA

Re: Change Password IIP failed

Post by jyoung » Sat Jan 20, 2018 2:29 am

Does the X_ERR.log file contain any thing?
You may want to enable tracing in VLF-ONE as well to see if anything shows up there as well.

Pablo
Posts: 41
Joined: Wed Dec 02, 2015 10:35 am

Re: Change Password IIP failed

Post by Pablo » Sat Jan 20, 2018 6:22 am

Hi Pravik,

To help you focus your investigation, these two messages:

"Call to User IIP failed."
"Please check server logs."

Are specifically issued when there is a failure to instantiate the nominated IIP.
The code looks like this:

Set_Ref Com(#UserValidationIIP) To(*Create_from #uIIPName.AsNativeString) Com_Error(*SET_NULL)
If (#UserValidationIIP *IsNot *null)
else
issue the error messages
endif


It means either that (for some reason) the IIP executes and crashes or there is no executable IIP with that name.

As Joe suggested, turning tracing on is useful because it will write out the name of the IIP and you can take it from there. And there should also be logs, x_err.log or joblog for IBM.

Regards,
Pablo

Post Reply