Initially the Service Catalog "install.log" recorded issues with the database connection while trying upgrade and changed the database password.
Perform an upgrade first on a test server in order to check that it works. Never directly upgrade on a production server.Further Analysis
The common installer was failing to connect with the MDB.
Changed to plain password to rule out issues with special characters, but this did not work.
See During Service Catalog installation, the error "Configuring mdb failed." is received.
It was identified that due to the database password change, the config.properties
file had old encrypted passwords.
Suggested to use encrypter.bat to encrypt new password and update in config.properties.
Due to some file access issues config.properties was not updated properly.
Client rectified the access issue and updated config.properites with new password and installation went to next step.
After laying the files, common installer failed at configuring MDB step, identified that this was because of permissions issue to mdbadmin user.
After providing sysadmin permissions to mdbadmin, installation succeeded.
Also there was some issue with which latest config.properties values were missing, we have copied the content from backup folder and modified couple of flags
__CLEAN_INSTALL__= 0 (was 1)
setup.utility.active=true (was false)
-PAM auto-detection failed as common installer was picking wrong URL, modified al_cdb_configurationparameters to set slcm.pam.integrated to 0 and pam.provider.url to empty.
Restarted the upgrade process once again
System completed all the tasks without any issue and completed successfully.
Did sanity tests on Catalog, saw request status showing as 'unknown', which is because of the customizations done on requestshared.xml.
Change customizations and integration with latest files (as customization in 17.1)
Used a compare file tool to identify the differences in requestshared.xml from 14.1 back to 17.1 and updated the content
Replaced the file structure for custom information
Recycled the services , Cleared the translets, cleared the browser cache and logged into the application. Successfully logged int and working as expected
Successfully upgraded till 17.1 and client would like to complete the RU2 patch at a later stage due to the deadline of go-live.