I am getting the following error when I try to login to my ContentBox 3 installation. I got this working on my local Windows 8.1 running on ColdFusion 2016 and IIS. I then transfered the whole thing to a new Azure VM setup with Ubuntu, Apache 2.4 and Lucee (latest release). I finally got it running and got the SES URLs working but I get this error when I try to login. My home page works fine though so I know the DB connection is ok (content page with favorite URL links). My database is an Azure DB instance.
We have to do more testing with Lucee 5. I’ll try and get this tested soon… and report back.
Looking at the error, it looks like ORM… so I wonder if its a Lucee 5 ORM issue, or the Azure DB ORM issue.
I thought someone had issues with the latest MS SQL 2016 with ORM. Does that ring any bells to anyone?
If you can… use the latest 4.x
We are actively testing and using against 4.x. Since Lucee 5 released, we are updating our Lucee Extensions, but most of our Ortus Sites require those extensions, so we’re running them on 4.x still.
Since Lucee 5 came out, we have only had minor testing.
I’ll try to run through an install and setup asap and report my findings on Lucee 5.
In the meantime, 4.x would be the best bet.
Thanks for the feedback.
I realized that I was running on 5.0.0.254. So I updated to 5.1.0.34 and I got a different error (attached below). I will downgrade to Lucee 4.5 for now until you announce that it is working on Lucee 5.x.
I went ahead and built a second VM for Lucee 4.5 and ran into issues there as well. I currently have:
Ubuntu 16.10
Apache 2.4
Lucee 4.5.4.017
I transferred my ContentBox folder to the new VM and got it up and running. I can hit the home page and can login, but I get the following error on the Dashboard page in the ContentBox Admin. I then thought to try the latest development release of Lucee so I updated to 4.5.5.004 and got the same error. I realized then that I had setup my data source using the jTDS JDBC driver. So I renamed it and created a new data source using the native Microsoft JDBC driver and then it started working! Not sure what the difference is, but I’m glad I got it working.