"Error: Cannot save attachment to local temp file" is displayed in the Attachment Service Client log file

• BlackBerry® Enterprise Server 5.0 for IBM® Lotus® Domino®

In the Attachment Service Client log files (ASCL), the following error may appear:

[10000] (07/15 01:23:16.687):{0xE6C} [thr:0x0E6C] CAttachmentExtensionHandle::LogExtensionError() - [ASCL] Error: Cannot save attachment to local temp file

A Native Notes Encrypted email with a zipped attachment is being processed during the time the error occurs.  To confirm this it is required to increase the logging level of the Attachment Service Client log to DEBUG level.  The default setting for this is ERROR.

In the BlackBerry® Administration Service console select BlackBerry Solution Topology - BlackBerry Domain -  Component View and Logging.  Under Logging select the correct server, click the second tab Logging details and find Attachment Service Client and change the log level to DEBUG.  Within about 30 seconds the ASCL logs should start logging at the DEBUG level.

With the log level set to DEBUG the attachment server will show the name of the attachment file that was causing the error to occur. In the below example, the name of the original file is Test Powerpoint Attachment.pptx. 

[40000] (07/15 01:23:16.671):{0xE6C} [thr:0x0E6C] CAttachmentExtensionHandle::_HandleAttachmentArchive() - attachment name=Test Powerpoint Attachment.pptx.zip
[40000] (07/15 01:23:16.671):{0xE6C} [thr:0x0E6C] CAttachmentExtensionHandle::_HandleAttachmentArchive() - before GetAttachmentDataIntoFileW(..., 260)
[10000] (07/15 01:23:16.687):{0xE6C} [thr:0x0E6C] CAttachmentExtensionHandle::_HandleAttachmentArchive() - GetAttachmentDataIntoFileW() failed with rc=0
[10000] (07/15 01:23:16.687):{0xE6C} [thr:0x0E6C] CAttachmentExtensionHandle::LogExtensionError() - [ASCL] Error: Cannot save attachment to local temp file

The next step will be to relate this to the messaging agent logs; the following log line would appear in the MAGT log files at the same time as the error occurs in the ASCL logs.

[40000] (07/15 01:23:16.532):{0x17F8} {Test User/org} Constructing message (CMIME), size=407, body size=222, attachment data size=0, unid=232D7831D8FE4D5148257A520057E708, RefId=-765991160, TransactionId=0, Tag=6715, MsgType=0x30002, RenderMode=0x201

If the value in the MsgType field is 0x10002 or 0x30002, it means the server is processing an Native Notes Encrypted message, and this is likely the cause of the error.  To confirm this, it is required to open the potential offending document in the users mail file and make sure the attachment name matches the one reported in the ASCL logs.

If the BlackBerry® Enterprise Server processes a Native Notes Encrypted message with a zip file, the above error in the ASCL log is expected and can be ignored. No issue would occur.

If this message is logged on an attachment that is not in a zip file and part of an Native Notes Encrypted Message, further analysis may be required. Please contact BlackBerry® Technical Support to investigate the error message.