I had the same issue. I had created a backup of my one location's 8.71 JSS database (prodserver.domain.com) with the database utility tool and imported it over into a new Casper 9 test box (casper.domain.com). Everything on the test box was a fresh install (OS X 10.8.4, Server.app 2.2.1, MySQL Community Server 5.6.13, Casper 9.0, latest Java 6 from Apple).

After importing the 8.71 database from prodserver, Tomcat on casper was restarted by the database utility. It got partway through the JSS startup process, then I received the error shown below.

external image link

Hey guys,

This is a known issue when restoring an 8.x database over the top of a 9 database. Since some of the new tables from 9 still exist after the restore, it causes some upgrade steps not to launch and some data mismatches. Could you give this a try to see if resolves the issue?

1.) Stop Tomcat
2.) Log into MySQL and run the following: drop database jamfsoftware; create database jamfsoftware;
3.) Restore the 8.x database with the Database Utility
4.) Start Tomcat

Running the drop and create will completely remove the database from within MySQL, ensuring that we don't have any stray tables in there and that we are restoring on a clean slate.

Hope this helps!

Yup, that fixed it on my end. Thanks!

I just ran into this as well. If this is a known issue when restoring a 8.x database to 9, why isn't it documented anywhere? I just looked at the 9.0 release notes and this is not listed in the known issues.

I think it would be good to add a note to the “Upgrading the JSS” section of the JSS Installation and Configuration Guide for Linux 9.0.pdf document (page 17 currently). I'd suggest adding a callout saying something like this:

Ensure that the MySQL service is properly configured with the jamfsoftware database from version 8.2 or later before running Casper 9 for the first time. If migrating the jamfsoftware database via SQL dump, be sure import the SQL dump BEFORE starting the JSS Tomcat Application.

When version 9 of the JSS starts up, it begins upgrading the jamfsoftware database to which it has been configured to connect (as defined in <tomcat home>/webapps/ROOT/WEB-INF/xml/Database.xml)

--Gerrit DeWitt
Amazon.com

Thx David, that is the solution!

hi... i might be off topic but how do you stop tomcat and also acces mysql commands ?

@ jmercier

Here is a link on Tomcat:
https://jamfnation.jamfsoftware.com/article.html?id=117

For my MySQL,
once you login to mysql the commands are available to use. The MySQL web page has resources to answer any other MySQL questions you may have.

Just ran into this problem but not related to a migration. If you are running 9.x and upgrade Java then you need to re-add the Oracle JCE files to /Library/JavaVirtualMachines/jdkversion/Contents/Home/jre/lib/security

JCE files for Java 1.7 can be found at http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html

David, we ran into this on two servers. Thanks for the fix. This might make a good knowledge base article. ;)

Don

Need. Delete. Button. :)

David - solved it for me too. Thanks!

if you need to stop Tomcat - try this link:

https://jamfnation.jamfsoftware.com/article.html?id=117