Must be missing a step

[Fasano, Christopher G.]

My apologies in advance.  I must be missing a step.  I have just updated my install of Unitime

I am at 4.8.198, running on an updated openSUSE tumbleweed machine.

I installed mysql-connector-j-9.3.0.jar

I have installed the blank database running on mysql.

When I try to login as admin I get the error that begins with:

Authentication failed: JDBC exception executing SQL [/* from TimetableManager where externalUniqueId = :id */ select tm1_0.uniqueid,tm1_0.acad_title,tm1_0.email_address,tm1_0.external_uid,tm1_0.first_name,tm1_0.last_name,tm1_0.middle_name from timetable_manager tm1_0 where tm1_0.external_uid=? limit ?] [Unknown column 'tm1_0.acad_title' in 'field list'] [n/a].

In the unitime.log I can find the error “Table ‘timetable.task_execution' doesn’t exist.  “   I’m not really sure where this table should be, but it’s not in the timetable database when check in mysql.

Again—I’m trying to get Unitime back up and running again and my apologies in advance for something silly.  

Best regards,

Chris Fasano

Prof. of Physics

Department of Physics and Engineering

Monmouth College

Monmouth, IL 61462

[Tomáš Müller]

Dear Chris,

Have you populated the UniTime database with either the blank-data.sql or woebegon-data.sql after it was created (using the schema.sql)?

If done correctly, UniTime will update the database version (and create the new tables/columns automatically during the first deployment).

You should see something like the following in the Tomcat log during the first deployment of UniTime:

[05/26/21 04:01:43] INFO <init> -> Reading file:/Applications/apache-tomcat-9.0.13/webapps/UniTime/WEB-INF/lib/timetable.jar!/dbupdate.xml ...

[05/26/21 04:01:43] INFO DatabaseUpdate -> Current UniTime database version: 190

[05/26/21 04:01:43] INFO DatabaseUpdate -> Performing UniTime update to version 191 (Registration Student Status Type)

[05/26/21 04:01:43] INFO DatabaseUpdate -> UniTime Database version increased to: 191

[05/26/21 04:01:44] INFO DatabaseUpdate -> Performing UniTime update to version 192 (Staff Campus)

[05/26/21 04:01:44] INFO DatabaseUpdate -> UniTime Database version increased to: 192

...

[05/26/21 04:02:00] INFO DatabaseUpdate -> Performing UniTime update to version 238 (Student Area Classification Major Unique Index)

[05/26/21 04:02:00] INFO DatabaseUpdate -> UniTime Database version increased to: 238

[05/26/21 04:02:00] INFO DatabaseUpdate -> Performing UniTime update to version 239 (Student Degree)

[05/26/21 04:02:00] INFO DatabaseUpdate -> UniTime Database version increased to: 239

[05/26/21 04:02:00] INFO DatabaseUpdate -> New UniTime database version: 239

The final version depends on the UniTime version that is being deployed. If the update fails for any reason, the individual update scripts are available in Documentation/Database/MySQL/Changes.

Additionally, please note that the installation instructions are specific to MySQL. If you are using MariaDB, a different driver and a change in the database connection string are required.

Best regards,

Tomas Muller

UniTime

--
You received this message because you are subscribed to the Google Groups "UniTime Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unitime-discu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/unitime-discuss/etPan.685c1abc.61d67077.ac0c%40monmouthcollege.edu.

[Christopher Fasano]

Thank you for your quick and kind reply.  

I’m not entirely sure what happened—I had installed the schema and the blank-data.sql, but I went into mysql and dropped the timetable database and reinstalled, and things just started to work.  Maybe there was some remnant hanging around that didn’t get updated correctly.  In any case, I’m now logged in!

Again thank you.

Best regards,

Chris

To view this discussion visit https://groups.google.com/d/msgid/unitime-discuss/CA%2BWCZteWCmb7BQY7FxndbFwEv3G4xhnjRh4razT7abfQ0dV_mQ%40mail.gmail.com.