http://coldfusion.com logo
Join Slack
Powered by
These admin type errors for me have always been ab...
# adobe
d
These admin type errors for me have always been about installations problems. I normally resort to restalling CF, or get Adobe support to guide me through the fix. (btw I no longer experience this stuff because I use commandbox).
m
@priyank_adobe can you give Ray a hand here.
p
@raymondcamden Are these console error started to occur after update installation?
r
it happens on click, for Download and Install, for Download, I get nothing in the console, and nothing happens, except the UI change I showed above
p
You can manually install the update.
Let me share the steps
r
thank you
p
https://cfdownload.adobe.com/pub/adobe/coldfusion/2021/updates/hotfix-004-330004.jar 1. Download the hotfix 4 jar from above link. 2. Copy the jar in \ColdFusion2021 folder 3. Launch the command prompt as Run as Admin and navigate to the Java\bin folder. Now this java has to be the one which you are using with CF. If it is default, then it should be \ColdFusion2021\jre\bin 4. Type the command "java -jar hotfix-004-330004.jar" and follow the on screen instructions. You don't need to download the packages as you are connected to internet. Please let me know in case of any issue.
"java -jar \ColdFusion2021\hotfix-004-330004.jar"
m
Thank you sire!
r
should i stop CF before doing this?
p
not required, hotfix will do it.
r
So, good news bad news. It did work. Thank you. But the example @Adam Cameron shared on his blog isn't working, and from what I know, it should.
p
Do you have the link handy from Adam's blog which I can check?
r
specific error: "The setPageContext method was not found."
a
Thanks for looking @ it @priyank_adobe
p
Let me try and get back to you.
r
kk- thank you
a
@priyank_adobe if you could give advice on how to access the page context object from within the Java code, rather than needing to pass it from the calling CFML code, that would also be excellent 😄
p
I haven't tried so far, so it new for me too. 🙂
r
yea, and ugly is fine - its just for debugging
a
I got someone else to run that code, and they get the same error.
p
I got the same error, I am checking
a
So... why am I special? (other than like the obvious, but that's not gonna help my CFML...)
@raymondcamden / @priyank_adobe what exact CF version? I'm on 
2021,0,04,330004
, Tim, my other tester, is on 
2021.0.02.328618
And I am running in a 
adobecoldfusion/coldfusion2021:latest
(build y/day) container.
p
I am on update 2021,0,04,330004
a
grrr. Pity it was not that.
p
I am on a standalone installation, I can try with update 2, if that makes any difference
a
What have I done that's different / non-standard I wonder?!
r
i tried update 2 earlier, also didnt work (hence me trying to update to 4)
p
Let me raise this and see someone from the engineering can shed some light on it.
a
Thanks so much Priyank.
Yeah my pal has updated to same version as me too: still the error.
He and I both are on Windows.
r
Same here
a
just blew away the container, redid my Dockerfile to just do stock 
adobecoldfusion/coldfusion2021:latest
, and nothing extra. Recreated the file within the container filesystem rather than voluming-in my work dir and... code still works.
@raymondcamden / @priyank_adobe... I am guessing you are both using a local install, not a docker container
p
I am using local install, but I can try this on Docker
a
I have an old local install. Lemme try first. Less effort.
The setPageContext method was not found.
p
something is wrong
a
So what's different about yer local install vs Docker image?
p
I have to check Adam, difficult to answer.
a
Yeah I know. Was more talking out loud than asking
p
It works with Docker and failing in standalone installation.
d
just a quick thought - the docker image will be case sensitive - a windows volume will not be - been caught with cfc / class filename issues like that before. May be barking up the wrong tree there but it is a difference in the installs (possibly)
a
Yeah good thinking, but I've made sure the casing is correct here. Like I literally copy and pasted what the thing declared itself to be when calling 
.getClass().getName()
etc. So the code is portable (it was written for a case-sensitive file system in the first place).
m
I see these all the time too! It's frustrating. I have to install it through the jar file from the command line. Even those directions got more confusing lately.
a
Any movement on this, @priyank_adobe?
3 Views
Open in Slack
PreviousNext
Powered by