I installed an update on my Win 10 laptop last night, and it blue screened (it’s happened before). After a reboot all seemed well, until I tried a CFM page.
It won’t load any pages, nor will the adminstrator come up, it just throws an error. Below are the errors, one from a random page, the other from the administrator.
It looks like my only option might be to reinstall (I did try uninstalling the last update, although the ininstall KB number did not match the one in the update history but they had the same date)
administrator.txt (5.9 KB)
error1.txt (6.3 KB)
Windows 10
IIS10
Lucee 6.2.0.321
before I give you the answer, did you google the exception first?
i.e. Incompatible magic value 0 in class file
I dropped it into ChatGPT, it said it was about the java class not starting up or being corrupt.
From there I did a reinstall, it would not work. I then uninstalled and manually deleted the Lucee folder which was still remaining and it worked, albeit lost all my tweaks and settings.
Luckily I have an image of my C drive which is OS only, so I’m going to put that back this evening to put things back as they were then check I have all MS updates and if not update and see what happens.
I suspect you’re going to tell me this was an simple fix 
I’m guessing somehow you are now running with a different JVM than before, most likely an older version than last time lucee ran and created the classes under dynclasses?
Lucee always ships itself with java bytecode for 11, but anything it compiles after install is going to be at the level of your current jvm for best results.
So if you installed with 21 but somehow ended up having lucee picking up a java 11 jvm, it’s going to cause these type of errors
You could try stopping tomcat and purging c:\lucee\tomcat\lucee-server\context\dynclasses and restarting?
Unfortunately as I’ve performed a full reinstall and deleted the directory before I did it I can’t try that now.
I can confirm I was up to date, with version 6.2.0.321 and that is the same version I installed. However there was the odd issue where in add remove programs there was an instance of 6.1.x as well, which it could not remove as the installer was removed when I removed 6.2.x so I had to hack it out of the registry.
If not tonight, certainly by tomorrow morning I’ll have brought back my C drive OS image into play, so it’ll need the same windows updates again, so I’ll see if I am able to replicate the issue and will report back.
1 Like