Hi,
Just to add on to the above point, a month back, we had migrated our SQL server repository instance from 2012 to 2016, and the server connection details was changed. Since i believe , during the initial installation of TDM portal we would provide inputs on SQL server repository details . So, is that during this upgradation, this might have not fetching the right repository details and is tending to fail? Now I am worried, if I do the TDM Portal installation on the working servers, will it affect the same issue over there, while upgrading from 4.4 to 4.5( Note in those servers, we haven't upgraded the SQL server versions from 2012 to 2016)
Now for the current challenge, Whats your suggestion
Do i need to go for the restore of the server sanpshot and do the installation again or
do I need to recover from the failed upgrade, manually remove all remnants of the Portal install:
- Ensure you have a current snapshot and valid backups of the directories noted above
- Open an Administrative command prompt
- sc delete CATestDataManagerPortal
- sc delete OrientDB
- reboot
- Delete C:\Program Files\CA\CA Test Data Manager Portal
- Delete C:\ProgramData\CA\CA Test Data Manager Portal
- Reinstall portal - during the reinstall you MUST specify the SAME OrientDB password and installation paths that were used in the original installation.
- Once the instillation is completed, stop the "CA Test Data Manager Portal" and "OrientDB" services
- Restore the backed up folders
- Restart services
BR,
Sunil