IBM Support

IV84819: ATTACHMENT 400 ERROR WHEN USING SPECIAL CHARACTERS IN ATTACHED FILE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Attachment 400 Error
    
    Sometimes one attachment is missing other times all attachments
    are missing. Issue does not occur at all times.
    
    Steps to reproduce problem:
    
    1. Disconnected
    2. Created followon
    3. Added jobplan (hence Specs)
    4. Editied 3 specs
    5. Added 3 photos
    6. Added 3 worklogs
    7. Reconnected
    8. One of the attachments seemed to be missing in Maximo
    9. But there was an error in Anywhere
    
    First attachment of three was missing. The last 3 attachments
    should be one, two (mistyped to twoy) and three.
    One is missing.
    The reason that there are more is that the query pulls
    attachments from other workorders in the hierarchy.
    
    Expected behaviour:
    All the attachments should be uploaded to Maximo when device is
    reconnected to the device.
    
    Environment:
    
    IBM Maximo Anywhere 7.5.2.1 Build 20150730-101121-0400 DB Build
    V7521-04
    Tivoli's process automation engine 7.5.0.8 Build 20150401-2000
    DB Build V7508-33
    IBM Maximo Asset Management 7.5.0.8 Build 201504071004 DB Build
    V7508-00
    IBM Maximo for Service Providers 7.5.3.0 Build 20140708-1430 DB
    Build V7530-19
    MaxTAF 7.5.0.0 Build 2.4.0.0 DB Build V7500-24
    IBM Maximo for Utilities 7.5.0.1-20140311-0927 Build
    20120710-0136
    DB Build V7501-14 HFDB Build HF7501-04
    TPAE OSLC Object Structure 7.5.2.1 Build 20150730-101114-0400
    DB Build V7521-03
    IBM Maximo Asset Management Scheduler 7.5.2.0 Build
    20150401-2000 DB Build V7520-181
    IBM Maximo Spatial Asset Management 7.5.0.1-20151113-1143 Build
    20120714-2208 DB Build V7501-13 HFDB Build HF7501-07
    IBM TPAE Integration Framework 7.5.1.3 Build 20150403-1800 DB
    Build V7513-02
    A.W. 7.5.0.R4 Build 0 DB Build V7500-00
    
    WAS 7.0.0.33
    Oracle 11.2
    
    Mobile device: Panasonic Toughpad FZ  G1 : Windows 8.1
    
    Operating System:
    
    Windows Server 2008 R2
    

Local fix

  • Dev provided fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Any users trying to attach from the Gallery on Windows       *
    * Tablet would see this.  Any Android or iOS users who tried   *
    * to attach files with special characters                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Attachments with special characters cannot be uploaded to    *
    * the Maximo server, the end user receives a 400 error on the  *
    * Workorder.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to the latest fixpack                                *
    ****************************************************************
    

Problem conclusion

  • Maximo cannot handle these special characters at the OSLC layer
    when we attempt to upload.  Therefore, we will strip these
    special characters out of the filename before uploading.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV84819

  • Reported component name

    ANYWHERE APPS

  • Reported component ID

    5725M39MA

  • Reported release

    752

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-15

  • Closed date

    2016-05-18

  • Last modified date

    2016-05-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • ATTACH
    

Fix information

  • Fixed component name

    ANYWHERE APPS

  • Fixed component ID

    5725M39MA

Applicable component levels

  • R752 PSY

       UP

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPJLC","label":"Maximo Anywhere"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"752","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
18 May 2016