[ChuNu]

Hello,

While I am crossing the 90-minute mark with Sprint/Nextel (who themselves simply seem to be calling RIM) on this problem, I thought perhaps someone here could help me fix this problem sooner.

I have added .XML filetypes to the LoadTextDistiller\Extensions registry entry as well as added .XML as a valid filetype in connector configuration of the attachment server area of the BlackBerry Server Configuration Panel.

I have used the "Test Attachment Service" feature to successfully view an XML attachment. These are 'straight-up' XML files about 9KB in length and only ASCII. The XML is being generated automatically by our CISCO MARS device (security device that sends alerts as XML attachments)

These attachments used to work and display properly. Without knowing that anything has changed, however, the viewing of attachments no longer works.

I can view the 20-character or so summary.

When viewing the full file however, it always downloads the file and then says simply, "Document is Empty". The problem occurs for anyone viewing these types of attachments, not just my handheld.

Help!

BES Server Version: 4.1.4.15
Handheld Version: 4.1.0.380 (Platform 1.6.0.12)
BlackBerry Model: 7520

I have attached a copy of the (scrubbed, for data security reasons) XML file. For this BB, you must rename it to .XML

[DarkWater]

Well I'm not sure what to say. XML documents were never one of the supported file types.

Sure you can add the extension to make the server see it, but that doesn't change the content of the file.

[ChuNu]

Originally Posted by DarkWater

XML documents were never one of the supported file types..

It's just an ASCII text document, that happens to have a filename that ends in .XML.

This is identical (except for three characters) to the example on blackberry.com for adding .LOG as a valid text type. See How to add extensions to existing distillers for the BlackBerry Attachment Service

----
Update: The problem occurs for .TXT files as well.

[ChuNu]

Was finally able to speak to BB support direct. After some trial and error, it was determined that this is a known bug in SP4 - text attachments greater than 4KB cannot be displayed.

No reasonable workaround exists, unless you call installing an older instance of the attachment service on a remote server.

Grrr!

Cheers.

[DarkWater]

Oh... well not that you mention it I do recall hearing something about that.