I saw that workaround. I currently have a basic HTTP server serving that jar file. the line in run_protege_server.sh is: CODEBASE_URL=http://ess-app1.wglabs.local:8000/protege.jar ess-app1.wglabs.local is the name of the local machine. It is not using tomcat to serve it, but rather it is using webfs...

Yes, things worked to set up the DB in client mode. Converting the project to a DB project was successful, and the DB was populated - I went in using the DB client to check to see if the tables had anything in them.

So, everything is good as far as setting up the database - to my knowledge.

I haven't messed with Max memory, but the other two settings (pprj exact locations, and JDBC driver) are good.

Ok, maybe I'm not seeing it, but I can't see the log file I attached to the original post. Here is it's contents: 2013.06.07 15:56:06.284 EDT INFO: *** SYSTEM START *** -- Server.startServer() 2013.06.07 15:56:06.288 EDT INFO: Protege server is starting... -- Server.startServer() 2013.06.07 15:56:06...

I forgot to mention that I am using SQLfire as my DB

Hello everyone, After working through several start-up errors with protege server, I am now confronted with one that I can't make heads or tails of. Essentially, you just start Protege Server ./run_protege_server.sh it loads up the project, but just as soon as the project is loaded protege barfs. I'...