Topic
  • 4 replies
  • Latest Post - ‏2014-02-27T16:47:35Z by ehdeza
MaherBA
MaherBA
6 Posts

Pinned topic Action status "Transcoding error"

‏2013-09-25T09:05:15Z |

Dear all,

Do you know please what means 'Transcoding error' action status??

And how resolve this issue??

  • liuhoting
    liuhoting
    14 Posts

    Re: Action status "Transcoding error"

    ‏2013-09-26T06:12:54Z  

    That's a pretty weird one I think. When and how does this happen? Only on particular fixlets?

    We can do some diagnostics here but this one might need to go to support.

  • jgstew
    jgstew
    47 Posts

    Re: Action status "Transcoding error"

    ‏2013-10-21T19:28:39Z  

    I'm getting this error on a few clients as well. It seems very odd. In the summary I see "The action failed transcoding from the deployment codepage." but the error status is "Transcoding error"

  • SteveHull
    SteveHull
    13 Posts

    Re: Action status "Transcoding error"

    ‏2013-10-22T05:42:17Z  

    This error indicates an error occurred while trying to transcode data across codepages.  IEM currently supports deployments that are all running in the same codepage, so likely the endpoints that are failing are in a different codepage than the server.  Look for any filenames in the action that might be codepage specific (special or accent characters), or if relevance substitution might evaluate to something that contains unique characters.  Gathering a client diagnostics to review the logs should provide a bit more detail.

  • ehdeza
    ehdeza
    1 Post

    Re: Action status "Transcoding error"

    ‏2014-02-27T16:47:35Z  
    • SteveHull
    • ‏2013-10-22T05:42:17Z

    This error indicates an error occurred while trying to transcode data across codepages.  IEM currently supports deployments that are all running in the same codepage, so likely the endpoints that are failing are in a different codepage than the server.  Look for any filenames in the action that might be codepage specific (special or accent characters), or if relevance substitution might evaluate to something that contains unique characters.  Gathering a client diagnostics to review the logs should provide a bit more detail.

    I found out that this error reached on one of  my Aix IEM clients was due to a missing codepage data file icudt49b.dat, no matter what good the rest of client deployment it is, apparently all is working well, but when you try to make any task, fixlets and so on from IEM Console versus this IEM client you will get a "transcoding error" status.
     
    For me was very usefull to logs shown in the IEM client Log file, here is a piece of  good working scenario log file generated during IEM agent start up.
     
       ICU data directory: '/var/opt/BESClient'
       ICU deployment character set: ISO_8859-1:1987
       ICU local character set: ISO_8859-1:1987
       ICU transcoding between deployment and local character sets: DISABLED
     
    In case of IEM client do not find your own ICU datafile it end up using the OS default code page( in my case 7-bits ASCII C), and the problems arise 
    if local character set and deployment character set are different.
     
    Best Regards,
    Ernesto.