Postgres Error

[otrspk]

Any solution to following error, using otrs 2.4.7 with postgres on Centos.

Error: ERROR: invalid byte sequence for encoding "UTF8": 0xa0

This message comes when creating a new ticket.

[Mike_B]

Hi,

Actually this looks like an old bugzilla report: http://bugs.otrs.org/show_bug.cgi?id=3793

I tried to reproduce this in order to fix it, but never succeeded in reproducing. Can you please provide some details about your configuration?
* Server OS
* PostgreSQL version
* DBI and DBD::pg version
* Character set used on front-end
* Whether or not you use SSO
* Client OS
* Web browser

--
Mike.

[jeffv]

I'm not finding a solution for the encoding error, and I don't see any instructions on how the Postgres database should be setup.
Confused about what needs to be fixed; otrs or postgres.

I am attempting upgrade from 2.3 to 2.4. Postgres encoding is UTF8. OTRS config's are using UTF8 also.

I created a brand new database in postgres, but can't update existing ticket or add a new one. The ticket is entered in the database, but the subject is not.

Apache Log:

Code: Select all

[Thu Oct 28 12:35:31 2010] -e: DBD::Pg::db do failed: ERROR:  invalid byte sequence for encoding "UTF8": 0xa0
[Thu Oct 28 12:35:31 2010] -e: HINT:  This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encoding". at /opt/otrs//Kernel/System/DB.pm line 427.
ERROR: OTRS-CGI-10 Perl: 5.10.0 OS: linux Time: Thu Oct 28 12:35:31 2010

 Message: ERROR:  invalid byte sequence for encoding "UTF8": 0xa0
HINT:  This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encoding"., SQL: 'INSERT INTO article (ticket_id, article_type_id, article_sender_type_id, a_from, a_reply_to, a_to, a_cc, a_subject, a_message_id, a_in_reply_to, a_references, a_body, a_content_type, content_path, valid_id, incoming_time, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'

 Traceback (22652): 
   Module: Kernel::System::Ticket::Article::ArticleCreate (v1.232.2.4) Line: 215
   Module: Kernel::Modules::AgentTicketClose::Run (v1.69.2.8) Line: 566
   Module: Kernel::System::Web::InterfaceAgent::Run (v1.43.2.1) Line: 819
   Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 48
   Module: (eval) (v1.88) Line: 204
   Module: ModPerl::RegistryCooker::run (v1.88) Line: 204
   Module: ModPerl::RegistryCooker::default_handler (v1.88) Line: 170
   Module: ModPerl::Registry::handler (v1.99) Line: 31

[jeffv]

OK, figured out MY problem. I was adding "$Self->{DefaultCharset} = 'utf-8';" to the wrong file.

I added it to /etc/otrs/Kernel, but it needed to be added to /opt/otrs/Kernel/Config.pm.
I added it just below the fs root directory section.

Works great now.