CKB:Exception "SaveMailToSentFolder" is thrown after file upload has finished during the Cryptshare transfer: Unterschied zwischen den Versionen
Aus Cryptshare Documentation
(Imported from text file) |
K (Move page script verschob die Seite CKB:21233712 nach CKB:Exception "SaveMailToSentFolder" is thrown after file upload has finished during the Cryptshare transfer) |
(kein Unterschied)
|
Aktuelle Version vom 14. Januar 2022, 11:36 Uhr
Applies to:
Cryptshare for Office 365 & Outlook up to version 2.5.0
Symptom:
When the user has confirmed the transfer dialog and the files are finished uploading, the user is receiving an exception with the following message:
Logview Expand source 2018-06-13 09:07:02.0639 | ProcessException | ERROR: INCOMING CRYPTSHARE EXCEPTION TO PROCESS | System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. bei com.befine_solutions.cs4outlook.custom.main.EmailFactory.SaveMailToSentFolder(RDOMail originalRdoMail, RecipientsTypeObj recipients, DateTime expirationDate, ObservableCollection\`1 fileList, String recipientLanguage, TransferSettingsObj transSettingsObj, AccountSettingsObj accSetObj, TransferUploadInfoObj transUplInfoObj, List\`1 embedAttResultList, String subject) 2018-06-13 09:07:02.0639 | ProcessException | ERROR: Beim Speichern der gesendeten E-Mail in den Ordner Gesendete Elemente ist ein Fehler aufgetreten. Für detailliertere Informationen klicken Sie bitte auf 'DETAILS ANZEIGEN' | System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. bei com.befine_solutions.cs4outlook.custom.main.EmailFactory.SaveMailToSentFolder(RDOMail originalRdoMail, RecipientsTypeObj recipients, DateTime expirationDate, ObservableCollection\`1 fileList, String recipientLanguage, TransferSettingsObj transSettingsObj, AccountSettingsObj accSetObj, TransferUploadInfoObj transUplInfoObj, List\`1 embedAttResultList, String subject)
Cause:
This issue occurs if one or more recipients have not been resolved correctly before the Cryptshare transfer was started. This is especially common with third-party applications that trigger a new email window with a pre-populated recipient field. This symptom is known and being worked on.
Solution:
Update to the latest version of Cryptshare for Office 365 & Outlook