Well I ran the scripts which are mentioned in the Upgrade file. I´m running
my OTRS on a Linux CentOS 5.3 Server with mod_perl, so I don´t know if the
manual from the win wolrd would help me out, but I´ll have a look just in
case I oversaw something.

Mit freundlichen Grüßen / Kind regards
Markus Moj
Technik

TimoCom Soft- und Hardware GmbH
In der Steele 2
D-40599 Düsseldorf
Tel: +49 211 88 26 80 14
Fax: +49 211 88 26 70 14
eMail: [email protected]
www.TimoCom.com
Geschäftsführer: Jens Thiermann, Gunther Matzaitis
Amtsgericht Düsseldorf, HRB 34489


                                                                       
  From:       Lars Lindgård <[email protected]>                    
                                                                       
  To:         User questions and discussions about OTRS. <[email protected]>
                                                                       
  Date:       20.08.2009 16:11                                         
                                                                       
  Subject:    Re: [otrs] Update OTRS 2.3.4 -> 2.4.3 - DB convert latin1 -> utf8
                                                                       
  Sent by:    [email protected]                                    
                                                                       





Did you run the sql-update scripts as described in section 6 in the install
FAQ - http://faq.otrs.org/otrs/public.pl?Action=PublicFAQ&ItemID=301 ?
I had the same problem with an upgrade from 2.3.4 to 2.4.2.  After I ran
the scripts, the tickets had all the information intact.

--Lars

From: [email protected] [mailto:[email protected]] On Behalf Of
Marco Vannini
Sent: 20. august 2009 15:22
To: User questions and discussions about OTRS.
Subject: Re: [otrs] Update OTRS 2.3.4 -> 2.4.3 - DB convert latin1 -> utf8

I had the same problem (content of the ticket empty), for me wasn't a
charset problem.

I've restored a previuosly backed up otrs db and restarted with step 1 of
migration. After that data was correct either if 4/5 tables resulted to be
latin. After a period of time overwathing the system just to be sure that
it was all ok, I've used phpmyadmin to assign utf_general_ci to the tables
that weren't so without problems (obviusoly there should be mysql manual
command to do that but I'm a lazy boy ;) )

MV


On Thu, Aug 20, 2009 at 3:04 PM, <[email protected]> wrote:


Hi there,
I have a little problem. I´m running OTRS 2.3.4 without ITSM and want to
upgrade it to the new 2.4.3 with ITSM. Just in case that there are some
problems, I´ve set up a test enviroment. The Upgrade worked fine for me,
following the instruktion in the Upgrade file. But the tickets are not
shown Properly in the ticket system. I just get to see the ticket number
but the content is gone. When I look in the Admin Support Assessment I get
the error message that the charset is latin1 instead of utf8. Now I would
like to know if there is a possibility to convert the DB to utf8 without
loosing all the tickets in the system.


Mit freundlichen Grüßen / Kind regards
Markus Moj
Technik

TimoCom Soft- und Hardware GmbH
In der Steele 2
D-40599 Düsseldorf
Tel: +49 211 88 26 80 14
Fax: +49 211 88 26 70 14
eMail: [email protected]
www.TimoCom.com
Geschäftsführer: Jens Thiermann, Gunther Matzaitis
Amtsgericht Düsseldorf, HRB 34489

---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/



                                                                                
                                                              
 CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may 
be privileged. If  you are not a named recipient, please notify the
 sender immediately and do not disclose the contents to another person, use it 
for any purpose or store or copy the information in any medium.
                                                                                
                                                              





                                                                                
                                                              
 CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may 
be privileged. If  you are not a named recipient, please notify the
 sender immediately and do not disclose the contents to another person, use it 
for any purpose or store or copy the information in any medium.
                                                                                
                                                              


---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

<<inline: graycol.gif>>

<<inline: ecblank.gif>>

---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Reply via email to