Customer backend issue after upgrade to 3.3.7

Moderator: crythias

Post Reply
netsmartnz
OTRS newbie
Posts: 1
Joined: 09 Jun 2014, 00:39
OTRS Version?: 3.3.7

Customer backend issue after upgrade to 3.3.7

Post by netsmartnz » 09 Jun 2014, 01:10

We have an MS SQL customer backend database that has been working fine. After an upgrade from 3.3.5 to 3.3.7 it has stopped working with the following Invalid column name errors:

[Error][Kernel]::System::CustomerUser::DB::CustomerUserDataGet][Line:559}: [unixODBC][FreeTDS][SQL Server]Invalid column name 'change_time'. (SQL-42S22)#012[unixODBC][FreeTDS][SQL Server]Invalid column name 'create_time'.

The fields 'change_time' and 'create_time' are now included in the SQL SELECT statement. I'm sure they were not prior to the upgrade and our database does not contain these fields.

Is there an option in OTRS that determines if these fields are required or not? What are they for or is this just a bug?

The databse is read only to OTRS for displaying customer contact information in the Agent interface.

Any help appreciated.

Cheers,

Paul

mah
OTRS newbie
Posts: 7
Joined: 04 Jun 2019, 11:35
OTRS Version?: OTRS 6

Re: Customer backend issue after upgrade to 3.3.7

Post by mah » 18 Jun 2019, 14:00

The following configuration has worked for me in OTRS6:

Add the following line to the Config.pm
ForeignDB => 1, # set this to 1 if your table does not have create_time, create_by, change_time and change_by fields

jojo
Moderator
Posts: 14571
Joined: 26 Jan 2007, 14:50
OTRS Version?: Git Master
Contact:

Re: Customer backend issue after upgrade to 3.3.7

Post by jojo » 18 Jun 2019, 14:23

Please don't hijack old posts and Threads!
"Production": OTRS™ 6, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) git Master

Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com :: Share your ideas

Post Reply