UF_OLOGON fail to login
-
nazirul_fitri
- Posts: 21
- Joined: Thu Sep 15, 2016 7:00 pm
UF_OLOGON fail to login
Hi all,
I try to do VLF-ONE login page that use my own db/lansa file but end up getting the error as follows:
1) Please check your server logs (I dont know where is the server log stored)
2) Call to user IIP failed.
Can anyone help me on this. If anyone get an example the edited UF_OLOGON would be really helpful for me.
I try to do VLF-ONE login page that use my own db/lansa file but end up getting the error as follows:
1) Please check your server logs (I dont know where is the server log stored)
2) Call to user IIP failed.
Can anyone help me on this. If anyone get an example the edited UF_OLOGON would be really helpful for me.
Re: UF_OLOGON fail to login
Could you start the shipped VLF-ONE demo framework as designer and get the build number and date?
Click the About button and scroll to the end:
Click the About button and scroll to the end:
Re: UF_OLOGON fail to login
Generally Visual LANSA reports errors into a cumulative file named X_ERR.LOG.
Where the X_ERR.LOG resides varies on what type of program is failing (eg: a windows form or a back end server module).
The first thing to try are these options in the top right of your Visual LANSA IDE .......
If that does not find the required error details I often just go looking for one with DIR X_ERR.LOG /S DOS command.
Where the X_ERR.LOG resides varies on what type of program is failing (eg: a windows form or a back end server module).
The first thing to try are these options in the top right of your Visual LANSA IDE .......
If that does not find the required error details I often just go looking for one with DIR X_ERR.LOG /S DOS command.
Re: UF_OLOGON fail to login
You appear to have a program failing in a server module.
I assumed that the web server you are using is localhost (ie: your PC).
If the web server is not on your PC then of course you have to look for the X_ERR.LOG file on the web server.
If the web server is an IBM i server then you should also look for a standard operating system QPJOBLOG (job log) file produced by your failing LWEB_JOB.
I assumed that the web server you are using is localhost (ie: your PC).
If the web server is not on your PC then of course you have to look for the X_ERR.LOG file on the web server.
If the web server is an IBM i server then you should also look for a standard operating system QPJOBLOG (job log) file produced by your failing LWEB_JOB.
-
nazirul_fitri
- Posts: 21
- Joined: Thu Sep 15, 2016 7:00 pm
Re: UF_OLOGON fail to login
The About is working perfectly fine. This is the detail (I cant attach the picture, dont know why):MarkD wrote:Could you start the shipped VLF-ONE demo framework as designer and get the build number and date?
Click the About button and scroll to the end:
VL Framework Build Number : 141006
VL Framework Build Date : 27th July 2016
I guess my code for UF_OLOGON is wrong somewhere because i edit a few line to suits my data in DB. Can you show me how to edit the UF_OLOGON to read the user & password from File (the shipped version not verify the password)?
Re: UF_OLOGON fail to login
UF_OLOGON is not involved in logging on as designer - I just wanted to know what version of the VLF you are using.
You should look for the X_ERR.LOG (and maybe QPJOBLOG spool files if using an IBM i server) as suggested in the other posts.
One of them should have detailed error messages that tell you why your UF_OLOGON program is failing
You should look for the X_ERR.LOG (and maybe QPJOBLOG spool files if using an IBM i server) as suggested in the other posts.
One of them should have detailed error messages that tell you why your UF_OLOGON program is failing
Re: UF_OLOGON fail to login
What type of web server are you using? Windows or IBM i?
-
nazirul_fitri
- Posts: 21
- Joined: Thu Sep 15, 2016 7:00 pm
Re: UF_OLOGON fail to login
MarkD wrote:What type of web server are you using? Windows or IBM i?
Im just running it in my localhost windows.
-
nazirul_fitri
- Posts: 21
- Joined: Thu Sep 15, 2016 7:00 pm
Re: UF_OLOGON fail to login
I have check the error log but there is nothing. A blank log.MarkD wrote:UF_OLOGON is not involved in logging on as designer - I just wanted to know what version of the VLF you are using.
You should look for the X_ERR.LOG (and maybe QPJOBLOG spool files if using an IBM i server) as suggested in the other posts.
One of them should have detailed error messages that tell you why your UF_OLOGON program is failing
Re: UF_OLOGON fail to login
I have never heard of a VL program crashing without producing a log.
Could you post screen shot(s) of exactly what you see in the browser window when you try to run your UF_OLOGON?
Could you post screen shot(s) of exactly what you see in the browser window when you try to run your UF_OLOGON?
Re: UF_OLOGON fail to login
Also, when you start try adding &Trace=System to the URL and see what the system trace says.
The system trace can be sent to a spreadsheet so posting that might be helpful as well.
The system trace can be sent to a spreadsheet so posting that might be helpful as well.
-
nazirul_fitri
- Posts: 21
- Joined: Thu Sep 15, 2016 7:00 pm
Re: UF_OLOGON fail to login
sorry i have delete the logon i made. basically the output is same like above but it show error :
1) Please check your server logs (I dont know where is the server log stored)
2) Call to user IIP failed.
1) Please check your server logs (I dont know where is the server log stored)
2) Call to user IIP failed.
Re: UF_OLOGON fail to login
The errors indicates that your version of UF_OLOGON could not be loaded, it did not fail when it was running.
You would not have changed UF_OLOGON because of what the comments say - you must have made your own copy of it.
What was your version of UF_OLOGON named?
What was the ID of your version of UF_OLOGON? (the ID is often different to its name).
Did you identify it to the framework (ie: snap it in) on the properties tab?
Did you identify it by its ID?
The most likely causes of this type of "cannot be loaded" error are:
=> It is incorrectly identified by its name instead of its different ID.
=> It does not have ancestor #VF_AC027O in its Begin_Com Role(*EXTENDS #VF_AC027O)
=> Not being compiled.
You would not have changed UF_OLOGON because of what the comments say - you must have made your own copy of it.
What was your version of UF_OLOGON named?
What was the ID of your version of UF_OLOGON? (the ID is often different to its name).
Did you identify it to the framework (ie: snap it in) on the properties tab?
Did you identify it by its ID?
The most likely causes of this type of "cannot be loaded" error are:
=> It is incorrectly identified by its name instead of its different ID.
=> It does not have ancestor #VF_AC027O in its Begin_Com Role(*EXTENDS #VF_AC027O)
=> Not being compiled.
-
René Houba
- Posts: 220
- Joined: Thu Nov 26, 2015 7:03 am
Re: UF_OLOGON fail to login
Hi,
What is the solution for this problem?
I have exactly the same problem.
I created a copy of the UF_OLOGON and use this one is my framework definition.
I created an admin user with password. But when I fill in the user and password I always get:
1) Please check your server logs.
2) Call to user IIP failed.
On my PC there is NO X_ERR.log at all.
Kind regards,
Rene
What is the solution for this problem?
I have exactly the same problem.
I created a copy of the UF_OLOGON and use this one is my framework definition.
I created an admin user with password. But when I fill in the user and password I always get:
1) Please check your server logs.
2) Call to user IIP failed.
On my PC there is NO X_ERR.log at all.
Kind regards,
Rene
-
René Houba
- Posts: 220
- Joined: Thu Nov 26, 2015 7:03 am
Re: UF_OLOGON fail to login
Hi,
I think that I found the solution for this problem.
In the framework properties --> Web/RAMP Details tab --> IIP Component to validate VLF-ONE sign on
You can fill in the IIP Component name.
We created a copy of UF_OLOGON and give it the name: DIL_LOGON. We used that name, but the VLF uses the (short) internal name to call this program.
So instead of thus the name DIL_LOGON, we used the short name (max 8 characters) now: DIL_LOGO and this works now!!
So when you use the LANSA shipped component, you should fill in the short name UF_OLOGO.
I think that I found the solution for this problem.
In the framework properties --> Web/RAMP Details tab --> IIP Component to validate VLF-ONE sign on
You can fill in the IIP Component name.
We created a copy of UF_OLOGON and give it the name: DIL_LOGON. We used that name, but the VLF uses the (short) internal name to call this program.
So instead of thus the name DIL_LOGON, we used the short name (max 8 characters) now: DIL_LOGO and this works now!!
So when you use the LANSA shipped component, you should fill in the short name UF_OLOGO.