I have just upgraded my development server from OTRS 2.3.3 to 3.0.9. I started by upgrading to 2.4.10, which went very smoothly. I then followed the instructions to upgrade to 3.0.9 (using the tarball), and suddenly I can't log in. The error message I get is:
Panic, user authenticated but no user data can be found in OTRS DB!! Perhaps the user is invalid.
This is a Linux system with a MySQL database. Users are authenticated against the system_user table in the DB (this is specified in my Config.pm). I followed the instructions in the UPGRADING file to the letter, including running all the database changes, otrs.RebuildConfig.pl, and otrs.DeleteCache.pl. Everything looks ok in the DB as far as I can tell (e.g. the username I'm using is in the system_user table and is valid, there is information in the user_preferences table for the user, etc.).
So ... where did I go astray?
Thanks in advance for any help.
User authenticated but no user data found
Moderator: crythias
-
- Znuny newbie
- Posts: 2
- Joined: 11 Aug 2011, 19:50
- Znuny Version: 3.0.9
- Real Name: Nancy Hintersteiner
- Company: Spot On Networks
Re: User authenticated but no user data found
Problem solved. The salutation column in the system_user table needed to be renamed to title:
mysql> alter table system_user change column salutation title varchar(50);
Suggest that this be added to the database scripts.
mysql> alter table system_user change column salutation title varchar(50);
Suggest that this be added to the database scripts.
Re: User authenticated but no user data found
there is something wrong ith your database, as the table system_user was renamed to user in OTRS 2.3
So the MySQL Updatescript from 2.4. to 3.0 reflects the change of the column name:
ALTER TABLE users CHANGE salutation title VARCHAR (50) NULL;
So the MySQL Updatescript from 2.4. to 3.0 reflects the change of the column name:
ALTER TABLE users CHANGE salutation title VARCHAR (50) NULL;
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny superhero
- Posts: 723
- Joined: 10 Oct 2007, 14:30
- Znuny Version: 3.0
- Location: Hamburg, Germany
Re: User authenticated but no user data found
I ran into the same 'problem'.
This upgrading error comes up when the user table is defined in Config.pm, instead of SysConfig. Config.pm remains untouched during upgrade which will then still point to the old table.
This upgrading error comes up when the user table is defined in Config.pm, instead of SysConfig. Config.pm remains untouched during upgrade which will then still point to the old table.
openSuSE on ESX
IT-Helpdesk: OTRS 3.0
Customer Service: OTRS 3.0 (upgraded from 2.3)
Customer Service (subsidiary): OTRS 3.0
+additional test and development systems
IT-Helpdesk: OTRS 3.0
Customer Service: OTRS 3.0 (upgraded from 2.3)
Customer Service (subsidiary): OTRS 3.0
+additional test and development systems