Simply does not work with Outlook 2016 ProPlus about outlookbackupaddin HOT 13 CLOSED

Thanks for your quick response. [Note: I am a programmer, so I know a little more about this stuff than the average user.] I tried to attach a ZIP archive file with screenshots (each one is numbered for correct sorting in chronological sequence), but it failed at the GitHub server because it was too large. Can you suggest any way for me to get a 4 MiB ZIP archive file to you? In the meantime, here are my responses to your comments [by item number as you listed them]. They won't make much sense until you can see the screen shots and the JPG image file names (which describe what I wanted to show). 1. Neither Process Explorer NOR TaskInfo can locate an open handle for any of the PST files (all of which have a similar file name [for their initial 6 characters]). The behavior I have reported occurs regardless of whether or not Skype for Business is [still] running, was ever running, or was never, ever even started on the PC (since the last reboot). 2. Neither Process Explorer NOR TaskInfo can locate an open handle for the OST file. Yes, there is an error message (see attached screenshot #1). I know backing up the OST file is useless, but I had (eventually) added it to the list of files to be backed up just to see if doing so altered the behavior of the add-in. It is not a problem for me to leave it in the list of files to be backed up since the program decides rather quickly that it can't get the file lock. But I will take it out for all future tests. Additional note: At the end of backup processing by the add-in, it "stops" or "hangs" and no more activity takes place, and the window does not close (although it CAN _BE_ closed [using the X]). See the attached screenshot #13. It will stay displayed for hours until it is closed. Terminating the process will also, of course, remove the window. It appears that the process just goes into a wait, and no processor time is consumed, and no PST files (that is supposedly opened and copied) remain open. Is this normal behavior? I would not expect that to happen. But if it's normal behavior, I can live with it. 3. You are correct. In my many, many tests, I ended up making and keeping a lot of copies around in different folders. I *did* compare the wrong files. Comparing the right files shows that they ARE bit-for-bit identical. 4. See the attached screenshots for message(s). This behavior occurs regardless of the target of the copy (a local folder or a file server folder). Screenshots #1 thru #12 represent captures I made during processing. Screenshot #13 I discuss below. 5.A. First, I made several runs timing the copying of ALL of the PST files [the total file size of which is 16.2 GB] using various facilities other than your add-in. This should give you some idea of how fast a file copy here on my LAN can proceed. The two test file servers, Y and Z, are on the same Ethernet switch, actually in the same room here with the PC on which I am testing runs Outlook 2016 ProPlus. 5.A.1. Copying all PST files from a local folder to another local folder (on the same physical SSD) using the Beyond Compare utility takes 8 minutes 39 seconds (see attached screenshot #14). 5.A.2. Copying all PST files from a local folder to another local folder (on the same physical SSD) using Windows Command Prompt COPY takes 4 minutes 19 seconds (see attached screenshot #15). 5.A.3. Copying all PST files from a local folder to a file server folder on Server Y (via a gigabit LAN connection) using the Beyond Compare utility takes 3 minutes 7 seconds (see attached screenshot #16). 5.A.4. Copying all PST files from a local folder to a file server folder on Server Y (via a gigabit LAN connection) using Windows Command Prompt COPY takes 2 minutes 45 seconds (see attached screenshot #17). 5.A.5. Copying all PST files from a local folder to a file server folder on Server Z (via a gigabit LAN connection) using the Beyond Compare utility takes 3 minutes 28 seconds (see attached screenshot #18). 5.A.6. Copying all PST files from a local folder to a file server folder on Server Z (via a gigabit LAN connection) using Windows Command Prompt COPY takes 3 minutes 9 seconds (see attached screenshot #19). 5.A.7. The fastest target and file copy tool are a folder on file server Y and Windows Command Prompt COPY commands. I have no idea why Beyond Compare is slower than a COPY command in a Windows Command Prompt, but that appears to be the case regardless of target folder location. In any event, I configured the backup add-in to use a target folder location on both file servers, Z and Y, at different times during my series of tests just to make sure that its apparent misbehavior was not somehow related to a specific file server. 5.B. I have run the experiment you suggested. The basic speed displayed as high as 100 MiB/second. 16.2 GiB is 16588.8 MiB. At 100 MiB/second, they should take about 166 seconds to copy (if all that had to happen was just copy bytes). That is essentially identical to the time (165 seconds) that a set of Windows Command Prompt COPY commands required to copy all of my PST files. So the actual data copying proceeds as would be expected. The delay (or elapsed time elongation) is due to the hangs/waits after the "Getting file lock..." message, then issuing 11 "File is locked:" messages, every time, and then immediately "Starting copying..." is exhibited. In other words, the elongation of elapsed time to perform the backups is due to a delay after the "Getting file lock..." messages are issued. Yet, at that time, the PST files do not appear to be locked (according to the system monitor utilities). The previous PST file backup utility I had installed (the one from Microsoft itself) immediately started copying PST files after Outlook shut down (using an ordinary file copy and displaying the same Windows Explorer-style copy pop-up window), so it would appear to me that the PST files are no longer locked as soon as Outlook's process actually terminates. Again, thanks for your quick response.

| Getting a file lock can also fail if there are not enough permissions to this file. That is obviously not the case since it -- all by itself -- eventually gets the lock and proceeds and backs up the PST file. Contacting you on the CodePlex site.

Attempting to contact you on the CodePlex site failed with the following message: Oops! We’re sorry, but an error has occurred. The error has been logged for review by our team. Most likely this was an intermittent issue, please try your task again. If you would like to contact us regarding this error, then you can use our contact us form <https://www.codeplex.com/site/contact?RefNumber=fa9fae00-a490-472a-94db-a846e7c13c8a&Server=CO1MSDNWBCDS04> . Error Reference #fa9fae00-a490-472a-94db-a846e7c13c8a

What is the maximum size of file attachments for GitHub? I can break up the current 4 MiB ZIP archive file into smaller ones. I just need to know how big an attachment can be.

ZIP file has been attached to an e-mail sent to the indicated address.

To what e-mail address did you send it? I don't see it on this e-mail address.

For the record (since other people may be reading this exchange in the future), the developer has corrected all of the problems I encountered and added a couple of features I suggested. Very responsive! The add-in now works exactly as one would expect. I'm not sure when the exact version that has been made available to me will be available here, but I assume soon. The developer may choose to respond to this e-mail with more specific information. | The Enterprise edition has some extra features I don't see the "Enterprise edition." Where is that located?