Data files were modified by another application

[BrianDrab]

We keep running into the following scenario. (There are several other scenarios that this happens in however I'll document one)
1. We check out a Word Document using the SOS GUI (5.0.1)
2. Use Microsoft Word to open the file, make a change, save the document and close Microsoft Word.
3. Attempt to check in the file using the SOS GUI.

The following message is given. Is this expected?

Modified.jpg (26.43 KiB) Viewed 10425 times

[lbauer]

I wasn't able to reproduce a problem with checking out/editing/checking in Word files on XP with Word 2003.

What OS is the client on?

What version of Word?

Does this happen to only Word documents? All Word Documents?

[BrianDrab]

Windows Vista Enterprise SP2
Word 2007

It appears to happen randomly but often enough to warrant an inquiry. I'll try to find a reproducible scenario.

[jclausius]

Brian,

The message you showed occurs when another process has modified part of the VSSFLDRS.SOS file on disk. This could occur if the GUI client is open and an IDE executes an Open From Source Control (which assigns working folders) instead of opening a bound solution on disk, or perhaps another instance of the client connects to the same server/database.

This behavior is something new in SOS 5.0 which prevents the databaseX.sos corruptions of the past. Basically, the client detected the change, and pops up the warning regarding the situation. Next the client discards the operation, and loads the NEW tree skeleton with the latest info.

[jclausius]

Another way this would occur would be if multiple instances (or another process) changed the Folder's State File. Each folder has a corresponding "state file" which identifies the contents (files, GET times, checkout status, etc.) of that folder. This is stored under the user's local account data for the SOS Server/VSS Database.

If two instances modified the same file (or another process touched the file), the client would detect the modification, discard the operation, and reload that folder's new state.

[BrianDrab]

Actually, that explanation was VERY helpful. It gives me something to go on to troubleshoot and reproduce the issue. Maybe Antivirus software???

Thanks again. It's always helpful to why the intention of the message.

[jclausius]

Maybe Antivirus software???

If the timestamp on the VSSFLDRS.SOS or a corresponding folder state file is modified by whatever process, then that might be one explanation.