Hi @harikrishnadevanabowina ,
Consider the following steps to resolve the problem:
- Verify the name and location of the backup serverConf.xml file. Ensure that it's not being confused with the active configuration file. Adobe Campaign might inadvertently reference the backup file if it’s incorrectly named or placed in a directory that the application scans.
- The backup file should not have the exact name serverConf.xml, as this can cause confusion. Rename the backup file with a different extension or move it to a directory that is not monitored by Adobe Campaign.
- Ensure that the Adobe Campaign application is referencing the correct serverConf.xml file, particularly the one with the proper database configuration. This can involve checking and updating any scripts, batch files, or service configurations that might incorrectly point to the backup file.
- Open the active serverConf.xml file and validate that it has the correct database connection details, including the dataSource and any other critical parameters. Compare it with the backup file to ensure there are no discrepancies.
- If the backup file is not needed in the immediate directory, relocate it to a secure archive or a different directory where it won’t interfere with the active configuration. This ensures that the application won’t mistakenly access it.
- After making the necessary adjustments, restart the Adobe Campaign services to ensure that the application loads the correct serverConf.xml file.
- If errors persist, check the logs in the nl6/logs/ directory, such as server.log and web.log, to identify any lingering issues or misconfigurations that might still reference the wrong file.
Best regards,
MEIT MEDIA (https://www.meitmedia.com)
Find us on LinkedIn
Contact Us: infomeitmedia@gmail.com