Copy link to clipboard
Copied
After applying CF2021 Update 19, the following three services failed to start:
I was able to get the add-on working again by reinstalling it, but the ODBC services are no longer working. I even rolled back to update 18 and ODBC services are still failing to start. Any guidance with this would be greatly appreciated.
@Demetrius34669657am05 Please try to reinstall the ODBC Agent and Server. Open the command prompt as an administrator, navigate to \ColdFusion2021\cfusion\bin, and run cfpm.bat.
\ColdFusion2021\cfusion\bin>cfpm.bat
1. cfpm>uninstall ODBC
2. Stop the ColdFusion service.
3. Clear all the folders inside \ColdFusion2021\cfusion\bin\felix-cache.
4. cfpm>install ODBC
5. Restart the ColdFusion service.
Thanks,
Vikram
Copy link to clipboard
Copied
Do you have anything like Microsoft SQL Server running on the same machine? You might have to add the DependOnService registry value to these services so they don't stumble over each other.
Also, out of curiosity, are you using ODBC from ColdFusion? This is pretty rare nowadays. Usually, you can connect with JDBC directly and see better performance - not always, though.
Copy link to clipboard
Copied
@Dave Watts Thank you for your follow-up. We are not running MSSQL on the same machine, and yes...we are using the CF ODBC.
Copy link to clipboard
Copied
@Demetrius34669657am05 Please try to reinstall the ODBC Agent and Server. Open the command prompt as an administrator, navigate to \ColdFusion2021\cfusion\bin, and run cfpm.bat.
\ColdFusion2021\cfusion\bin>cfpm.bat
1. cfpm>uninstall ODBC
2. Stop the ColdFusion service.
3. Clear all the folders inside \ColdFusion2021\cfusion\bin\felix-cache.
4. cfpm>install ODBC
5. Restart the ColdFusion service.
Thanks,
Vikram
Copy link to clipboard
Copied
@Vikram_Kumar_M Thank you. That resolved the issue.
After update 18 and prior to this update, we upgraded SOLR from 7.2.1 to 8.11.3. Do you think that may had some involvement with the issue?
Copy link to clipboard
Copied
@Demetrius34669657am05 This is issue-specific to the latest updater, and we will publish the workaround soon in the article.
Copy link to clipboard
Copied
Thank you.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now