Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Thursday, March 20, 2008

adsrtal.sh gives error: Cannot Complete Applications Logon

Anand pinged me this error:

adapcctl.sh start

adapcctl.sh version 115.54

Cannot complete applications logon. You may have entered an invalid applications password, or there may have been a database connect error.
Apache Web Server Listener is not running.
Starting Apache Web Server Listener (dedicated HTTP) ...
Cannot complete applications logon. You may have entered an invalid applications password, or there may have been a database connect error.
Cannot complete applications logon. You may have entered an invalid applications password, or there may have been a database connect error.

Reason was that GUEST user was end dated. Once that was updated as null, apache started fine.

Metalink Note:363662.1 has the answer:


Symptoms

On 11.5.X
When attempting to start services using adstrtal.sh
the following error occurs.

ERROR
adapcctl.sh version 115.XX


Cannot complete applications logon. You may have entered an invalid applications password, or
there may have been a database connect error.
Stopping Apache Web Server Listener (dedicated HTTP) ...
Cannot complete applications logon. You may have entered an invalid applications password, or
there may have been a database connect error.

adapcctl.sh: exiting with status 0

.end std out.

This error can occur with the following scripts:
adapcctl.sh
adfrmctl.sh
adrepctl.sh
adfmcctl.sh
adfmsctl.sh




STEPS
The issue can be reproduced at will with the following steps:
Running adstrtal.sh or any of the other scripts listed above





Cause

Guest password was changed or end dated




Solution

To implement the solution, please execute the following steps:

1. Use the System Administrator Responsibility with the navigation of Security/User/Define and check to see if the GUEST user has been end dated. If the user has been end dated, clear the ending date field so the GUEST user account is useable again. If the user has not been end dated, then proceed to step 2.

2. Check the system profile option of "Guest User Password" and confirm that it is correct by attempting to login to applications using that username and password.

3. Confirm that the guest password in the '.dbc' files within the $FND_TOP/secure directory matches both the password specified by the system profile option and verified by step 2 above.

To reiterate:
The Guest username and password combination should match in all three locations:

--> .dbc file
--> FND_USER for Guest
--> system profile option %GUEST%

No comments: