Susan of the Malahat Review was frequently (but not always) getting "sharing violation" errors when she tried to save changes to the website in dreamweaver. This problem arose only since they purchased a new computer and put Payment Card Industry security software on it, as part of the move to online payment processing.

This was frustrating for her, and so JB wrote to the finance people on the theory that the problem must have something to do with the PCI software. I got a copy.

RE of finance came over for an hour + (I observed from the corner). Susan was able to reproduce the problem. RE used a similar, but obviously slightly different procedure as he wasn't able to reproduce the problem using his natural workflow, but was if he followed step by step instructions from Susan. So, by end of that meeting it looked like there was a way that one could avoid the sharing violation, but Susan wasn't sure what it was. Nobody had a good idea why those sharing violations were appearing in the first place - focus was on a workaround.

I went back a week or so later and Susan was still tending to get the problem. We went through a number of procedures slowly and pinned down a procedure that seemed to work and the variants that threw the sharing violation. By the end of that meeting Susan seemed more confident that she could avoid the problem - though of course we still hadn't solved the issue of why the errors were appearing in the first place.