Posted on 08-05-2022 12:54 AM
Solved! Go to Solution.
Posted on 08-05-2022 11:59 PM
Hi Everyone,
I fixed the issue by doing the followings.
Posted on 08-05-2022 01:00 AM
No yet, my friend. this just happened today. I have sent an email to Jamf Support. I will let you know when I hear from Jamf support or have a solution.
Posted on 08-05-2022 07:52 AM
What specific version of MySQL 8.0 did you both upgrade to? Jamf only supports up to 8.0.28 as detailed here:
https://docs.jamf.com/10.40.0/jamf-pro/release-notes/System_Requirements.html
Posted on 08-05-2022 07:59 AM
I upgraded to 8.0.28.0
Posted on 08-05-2022 11:08 AM
Have you verified the DataBase XML file located in JSS/Tomcat/WebINF/XML was not reverted to a default value or changed after the update? Also we experienced an issue and had to downgrade from 10.40 back to 10.38 due to some on-premise limitations and discovered the schema for the database tables was altered in the update resulting in me needing to torch the sql database and restore from backup, upon this JSS will load. Hopefully something here helps you, Jamf Support has been less than ideal when dealing with hosted on-prem instances in my recent experience, seems they want everyone on Cloud.
Posted on 08-06-2022 12:07 AM
Hi Matt, thanks for the advice. I did check the database.XML file. The values there are the correct new values. This is why database is connected successfully in Server Tools. However, no database connection through the web interface. Although my Jamf is working now, I still don't know the reason why it didn't work before.
Posted on 08-05-2022 11:59 PM
Hi Everyone,
I fixed the issue by doing the followings.