portal entry

select a category, or use search below
(searches all categories and all time range)
Title:

Having problems after applying a CF update? What to check, and how to recover!

| View in Portal
March 06, 2019 02:20:43 AM GMT
8 Comments
<p>Are you finding problems after applying a CF update? The explanation may be someplace you're not even looking: the update's "install log".  And the resolution may be just minutes away!</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2019/03/problems-applying-cf-update-check-first/">Having problems after applying a CF update? What to check, and how to recover!</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: Blog, Information, Updates, blog, ColdFusion, information, updates

Comments:

I'd also suggest looking on the CFML Adobe Slack channel to see what other folks are running into.  There were some issues reported on Slack that I did not run into with my update.
Comment by Jim Priest
1867 | March 06, 2019 01:40:30 PM GMT
Sure, Jim. Again, the title was what to check first. :-) I find too many people run to slack or the portal or  the bug tracker to claim "bug, bug" when it turns out it was indeed just an error in the applying of the update. But I could have added a PS saying, "what if you have problems but no errors in log?" I will consider that, but since editing a post takes it offline until moderated (vs just leaving the old version in place--grr), I'd not do that for at least a couple of days. Until then, these comments can help people. Thx.
Comment by Charlie Arehart
1871 | March 06, 2019 03:05:10 PM GMT
Grr. That was of course supposed to be a reply to Jim's comment below. It's just too easy (especially on mobile, it seems) to make that mistake, and it can't be corrected.
Comment by Charlie Arehart
1870 | March 06, 2019 03:07:38 PM GMT
Hi, Just one more guy having one more problem... sorry to bother.. I went to the update, and for some odd reason, it would not update. that is, the buttons on the update page would not work. you could click them, but they acted as if disabled. So i downloaded the latest update, and did a manual update. in a way hoping things would fix themselves. this seemed to go fine. the log issues no errors and the server came up. 2016 Successes 0 Warnings 0 NonFatalErrors 0 FatalErrors However, now when you go to the admin update page, its blank...  it says "Server Update > Updates " and the rest of the page is blank Looking at the XML for the page, and the update was not written to it...   how do i get this back so that i can update things automatically, or at least know i need an update? eventually this will be moot as i uninstall and reinstall 2018 express...   thanks  
Comment by Rumments
4771 | June 27, 2020 09:20:43 PM GMT
<p>Rumments, I have a guess at the cause of your problem, and the good news is that there are a couple of solutions to an unfortunate situation.</p><p>I suspect the issue is that you or someone else changed your cf admin “settings” page value for the “default scriptsrc directory”.</p><p>To prove if this is the problem, take note of the current value, and change it back to the default, which is /cf_scripts/scripts, as of cf2016. Does the cf update page work then? If so, use it to do your update, then you could set the value back to what you copied and move on. (See below for a better long-term solution.)</p><p>The admin setting you just changed is a “security” feature that allows one to specify a “non-standard” name that will ALLOW you to then change your external web server (iis or apache) to use that name as a virtual directory or alias. The thinking is that then bad guys can’t easily know your chosen name, and try to leverage those scripts for ill. It’s security by obscurity, which is weak security.</p><p>Anyway, the problem is that that admin change does NOT also change CF’s *built-in* web server (which is what the cf admin uses by default since cf2016) to have IT use that changed path, and so cf code used in creating the cf admin pages like that cf update page (which leverages javascript for the tabs shown) now fail to load properly.</p><p>FWIW, other have opened bug reports on this, and sadly Adobe has closed them offering not the solution but workarounds for how WE can MANUALLY change the built-in/tomcat web server to use the changed scriptsrc ourselves We should not have to.</p><p>Anyway, comments in the bug reports address the workarounds either for the version of tomcat in cf11 or 10 (<a href="https://tracker.adobe.com/#/view/CF-3955573" rel="nofollow">https://tracker.adobe.com/#/view/CF-3955573</a>) or for cf2016 and up (<a href="https://tracker.adobe.com/#/view/CF-4203348" rel="nofollow">https://tracker.adobe.com/#/view/CF-4203348</a>) .</p><p>But if you can’t or don’t want to do that change, again I proposed you could just change the admin value back to its default, do the update, and then set it back to the value you found it set to.</p><p>Let us know if this solves things for you.</p>
Comment by Charlie Arehart
4772 | June 27, 2020 10:23:29 PM GMT
Well, there is no someone but me here...  <span>  (this is my development server at home) and so, its still "/cf_scripts/scripts/" </span> So we will have to now assume that this is not it.. However I am very impressed with the speed you answered. I tend to keep most if not all settings quite the same in my at home system It Doesn't have access to the outside world (for that i migrate my app to a hosting server) This issue is small but annoying like a gnat...            
Comment by Rumments
4773 | June 28, 2020 12:33:46 AM GMT
Ok, my next guess would be that if you really mean the page is "blank", that instead you may be having an outofmemory metaspace error. For more how to KNOW and how to fix it, see my post at <a href="https://www.carehart.org/blog/client/index.cfm/2020/2/24/solving_metaspace_errors" rel="nofollow">https://www.carehart.org/blog/client/index.cfm/2020/2/24/solving_metaspace_errors</a>. BTW, it has nothing to do with what's happening on that page, nor even with the recent update you did. It just would randomly affect some pages. But the solution will work for all pages. Let us know if that's it, or not.
Comment by Charlie Arehart
4774 | June 28, 2020 01:39:09 AM GMT
Rumments, how did things turn out? I tried to help with enough detail to get you going. Was it on the right track? Or still issues?
Comment by Charlie Arehart
4812 | July 25, 2020 06:00:34 PM GMT