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
Customer backend issue after upgrade to 3.3.7
Moderator: crythias
-
- Znuny newbie
- Posts: 1
- Joined: 09 Jun 2014, 00:39
- Znuny Version: 3.3.7
Re: Customer backend issue after upgrade to 3.3.7
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
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
Re: Customer backend issue after upgrade to 3.3.7
Please don't hijack old posts and Threads!
"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