[rt-users] dumpfile-to-rt-3.0 --> $ENCODING ?

Jens Porup jens at cyber.com.au
Wed Aug 18 03:20:10 EDT 2004


I am upgrading a production 2.0 RT to the latest and greatest.

However, the dumpfile-to-rt-3.0 fails when attempting to import the
Attachments table:

        Couldn't create attachment
        $VAR1 = {
                'Subject' => '',
                'ContentType' => 'application/msword',
                'Filename' => 'C:\\Documents and
                Settings\\adamc\\Des    ktop\\Hosting Apllication Form.doc',
                'Headers' => 'Content-Type: application/msword;
                        name="C:\\Documents and Settings\\adamc\\Desktop\\Hosting Apllication Form.doc"
                        Content-Disposition: inline;
                        filename="C:\\Documents and Settings\\adamc\\Des ktop\\Hosting Apllication Form.doc"
                        Content-Transfer-Encoding: base64 ',
                'Creator' => '3',
                'Parent' => '31',
                'Created' => '2001-12-17 13:44:39',
                'id' => '33',
                'ContentEncoding' => 'none',
                'TransactionId' => '31'

        ERROR: invalid byte sequence for encoding "UNICODE": 0xe1
        [Wed Aug 18 07:06:50 2004] [crit]: Died at dumpfile-to-rt-3.0 line 714.

My Attachments table is filled with binary files--MS Word docs, etc. I tried
changing the $ENCODING="base64" but that didn't work. (I don't really know much
about different coding sets.)

Is the solution to the problem $ENCODING="magic_word" ?

Or is something else going on here?



More information about the rt-users mailing list