Although the CFAdmin > Updates shows that Update 7 is not applied and that there are two available updates, I am assume that the update is applied. The version number above shows a mux of 5 and 7, however implies 7 is applied since the build number (311392) matches that of Update 7, TomCat version was updated correctly and the new function GetCanonicalPath() is present.
I recently downloaded and installed CF 2016 Update 7 from CF Admin, all appeared to go well, however on restart, the Admin would not display correctly, however CF was running and our application was responding correctly. I was receiving errors on load of the CFAdmin, if I removed local cookies and tried again, I couldn’t log into the admin, received invalid un/pw error. I restarted the CF service manually. On restart (slow shutdown and restart), I was able to log in and everything appeared to be normal…I checked the update status and it did not appear that the update took place. Tried again, same results.
A check of the Setting Summary page and it appears that the patch is somewhat applied?
Server Details | |
Server Product | ColdFusion |
Version | 2016,0,05,311392 |
Edition | Standard |
Operating System | Windows Server 2012 |
OS Version | 6.2 |
Update Level | /C:/ColdFusion2016/cfusion/lib/updates/chf20160007.jar |
Adobe Driver Version | 5.1.4 (Build 0001) |
Tomcat Version | 8.5.32.0 |
- The Tomcat version was successfully updated and the CF Version is half (?) updated. Tomcat is upgraded from 5.28 to8.5.32.
ColdFusion was Build Number: 2016,0,05,303689 and is supposed to be updated to Build Number: 2016,0,07,311392
However we are displaying 2016,0,05,311392, what appears to be a combination of Ver 5 and 7?
Also, a new function was introduced with Ver7 GetCanonicalPath(path), I was able to successful show that the function does not exist on my local machine (CF2016) and does exist on the updated production machine.
Although the Admin > Updates shows that it is not applied and that there continue to be two available updates. I am assuming that the update is applied, the version number above shows a mux of 5 and 7, however implies 7 is applied since the build number matches that of Update 7, TomCat version was updated correctly and the new function GetCanonicalPath() is present.
Is this acceptable?
Your help is appreciated
Charlie, I found the update log you reference in your blog, and yes, there were errors, and they appear to be due to the service not stopping quick enough. I did see the service stop and start, as well, I restarted the service myself after the dirty update…however seems like our CF instance will not auto stop quick enough for the updater. As a next step, I will attempt to manually apply the update. I appreciate your help, thank you.
moalspvic, I suspect you’ll find that this is simply a matter of having had an error during the install of the update. Some parts got in, some did not. That explains the oddities you see.
You should just try installing it again. That usually works.
As for proof that you had an error, as well as more about handling if it happens again on the retry, see my blog post on the matter:
You must be logged in to post a comment.