Servererror when viewing ticket (Malformed UTF-8)

[Frippe]

Hi.

I just tried to upgrade from OTRS 3.0.11 to 3.1.1 and I'm getting a Server 500 error when i try to view a ticket.
I did the following steps and hope i didn't forget anything:
1. Backed up otrs database on the old server
2. Installed OTRS 3.1.1 on my own computer (Did not run the webinstaller)
3. Setup otrs database and imported the SQL-file from the backup
4. Copied the config files from the old server
5. Imported the DBUpdate-to-3.1.mysql.sql file
6. Executed the DBUpdate-to-3.1.pl script
7. Imported the DBUpdate-to-3.1-post.mysql.sql file
8. Executed the RebuildConfig and DeleteCache scripts
9. Restarted the services

I'm able to log in and the see the dashboard and all, but I get a server error when i try to view a ticket or when i go in to Administration/Dynamic Fields.

When i check Apache server logs I get the Following error message:

[Wed Feb 22 13:27:17 2012] [error] Malformed UTF-8 character (fatal) at D:/OTRS/OTRS/Kernel/cpan-lib/YAML/Loader.pm line 36.\n

In my old configuration i use one Free Text Field with some Swedish characters in the name, could this be the problem?
Anyone else got this problem?

Hope any of you could help.

[jpr]

Hi,

same issue with me when upgrading from 3.0.11 to 3.1.1:

Anyway, did you run the DBUpdate-to.3.1.pl script as otrs user and not as root? This didn't fix the issue but throws the UTF-8 error already when running the script.

I filed an error on the otrs bugzilla, (http://bugs.otrs.org/show_bug.cgi?id=8239) but until today no fix. They posted a sort of workaround which in my case didn't fix it.

The issue is not platform dependent as we use Debian Linux as platform.

We, too, had a german umlaut char in ticket free text fields. I tried to remove this / convert it to utf-8 directly in the database: Still not working.

Sorry not to give you any help, but you are not alone.

Jan