SA-20300

Summary

Application uses out-of-the-box (OOTB) Silverlight-based (SL) Word Merge implementation.

Some users sporadically experience error while trying to save Word document edited after successful Word Merge.
In cases when save failed, the SL control raises error and the document is not saved in the work object.

Error Messages

SilverLight Control ERROR in 'ReturnMergeResultToJS': [IO.IO_SharingViolation_File]Arguments: C:\Users\B17142\AppData\Local\Temp\1\SLWord_42556\WordMergeTemplate.docDebugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.41212.00&File=mscorlib.dll&Key=IO.IO_SharingViolation_File.

Steps to Reproduce

1. Advance application to the Word Merge flow action and clicks ‘Create Merge Document’ button.
2. After the merge process successfully completes, make a few changes.
3. Click "Close" x button to start closing Word document.
4. Select the "Save" option from the dialog to exit session with save.

Root Cause

On slower workstations, Word can be slow to completely release the lock on the edited document.

This may conflict with the SL control trying to establish the exclusive lock on the same file, causing "file sharing violation" error.

Resolution

If the user saves the edited document prior to exiting Word session, takes a second long pause, and then closes the Word session, the "file sharing violation" error is not observed.