[sknmail@rediffmail.com]

Dear Nick,

Please refer to your post as below -

"It appears that the installer is not entering the correct encrypted password in the OTM/tomcat/bin/tomcat.conf file. You may see something like this:

wrapper.java.additional.18=-DGuestEncodedPassword=TVdPVE1HVUVTVA==

This is incorrect...the correct entry should be: wrapper.java.additional.18=-DGuestEncodedPassword=VAU9uZtJtMwEb3tIVKgN49bfrnE=

I however tried this and that did not work as well. I had to use the plain password entry to get the application started: wrapper.java.additional.18=-DGuestPassword=CHANGEME

Please make sure to restart both your application and web instances when making this change. I tried restarting just the web instance as was still getting the error message."

I was also facing the same issue (same error message as mentioned), however I could find that there was another user "guest" (Not GUEST.ADMIN) which was having password in database in gl_password column as NWdeaPS1r3uZXZIFrQ/EOELxZFA= (My database was newly created available from CU#4 OTM installer). I am not sure what this password was. Now I had to set the password of this user to CHANGEME in encrypted format as VAU9uZtJtMwEb3tIVKgN49bfrnE=. This resolved my issue and I could see my login page.
The parameters in TOMCAT.conf was not set as my current password for GUEST.ADMIN was already CHANGEME. I could find in one of the thread that if the password is already CHANGEME for GUEST.ADMIN, no need to set this parameter; so I removed it. I think this is another issue resolution.
Please let me know if you have faced same issue.

Thanks,
Suresh

After writing above email, I found that there was error while running update_password.sh as a part of dbpatch_55.sql, so my passwords were not reset as CU4 standard password. So I resolved the problem and again re-ran dbpatch_55.sql again. So we have to take care that if for some reason update_password.sh file didn't get executed as part of dbpatch_55, then the problem I mentioned can happen.
- Suresh