Hi All,
Very often while booting peoplesoft application server, we get following error and app server is not started :
-- error initiating user error handler .
and no more information is available in logs .
Now it clearly states the reason that it has a problem with any user credentials .The possibilities could be :
1) Wrong, Locked or Expired Connect ID/Password
2) Wrong, Locked or Expired PeopleSoft User ID/Password
3) Wrong, Locked or Expired Access ID and Password
4) Wrong symbolic ID specified in PSOPRDEFN against that particular userid.
5) Owner ID could be wrong in PSSTATUS table
6) Entry in PSDBOWNER table could be wrong.
There are over ten reasons here.
In cases when you have done any instance refresh from a prod box which uses a different owner id or symbolic id, you would not have any idea whats wrong since it never has been started before otherwise atleast few things you could be sure are correct.
So what approach do you follow in this case ?
I am giving my approach here to exactly know what is wrong or locked or expired. I take advantage of application designer usnig the same mechanism to start as app server.
In configuration manager, give the same connect id and password you have specified in app server config file. Set trace by checking sql statements .
Now login to application designer with the same Peoplesoft user id and password as given in app server config file. It would not login to database but generate the trace.
Now just open the trace file with notepad and look at what step and table its stuck to move ahead.Now troubleshooting takes a minute only, if its stuck at dbowner, check the entry in that . If stuck at initial step while logging in from connect id, try logging to database with that id . if stuck at psstatus, check entry in that . And we are done , correct the thing and restart the app server ..it will boot !!!!
Note : In case of process scheduler, in addition to the above stated causes it might also occur due to incorrect settings in report nodes .see the distagent.log for details , if no errors are found there then above technique should work.
Very often while booting peoplesoft application server, we get following error and app server is not started :
-- error initiating user error handler .
and no more information is available in logs .
Now it clearly states the reason that it has a problem with any user credentials .The possibilities could be :
1) Wrong, Locked or Expired Connect ID/Password
2) Wrong, Locked or Expired PeopleSoft User ID/Password
3) Wrong, Locked or Expired Access ID and Password
4) Wrong symbolic ID specified in PSOPRDEFN against that particular userid.
5) Owner ID could be wrong in PSSTATUS table
6) Entry in PSDBOWNER table could be wrong.
There are over ten reasons here.
In cases when you have done any instance refresh from a prod box which uses a different owner id or symbolic id, you would not have any idea whats wrong since it never has been started before otherwise atleast few things you could be sure are correct.
So what approach do you follow in this case ?
I am giving my approach here to exactly know what is wrong or locked or expired. I take advantage of application designer usnig the same mechanism to start as app server.
In configuration manager, give the same connect id and password you have specified in app server config file. Set trace by checking sql statements .
Now login to application designer with the same Peoplesoft user id and password as given in app server config file. It would not login to database but generate the trace.
Now just open the trace file with notepad and look at what step and table its stuck to move ahead.Now troubleshooting takes a minute only, if its stuck at dbowner, check the entry in that . If stuck at initial step while logging in from connect id, try logging to database with that id . if stuck at psstatus, check entry in that . And we are done , correct the thing and restart the app server ..it will boot !!!!
Note : In case of process scheduler, in addition to the above stated causes it might also occur due to incorrect settings in report nodes .see the distagent.log for details , if no errors are found there then above technique should work.
No comments:
Post a Comment