Hi. Yes, my Cache controller for Ensemble is logged on with the root admin user of the machines on which they work. Btw, I should add that throughout the development of this practically functional system (only authentication is incomplete), this error has kept appearing.
Please contact InterSystems Support.
Haven't followed that advice yet. Maybe I should, at this point, but this forum was extremely helpful for another issue I had earlier. Will follow that directive if there is still yet no resolution to this.
Hi. Yes, my instance is on the same machine on which I work. My Subversion repository is, of course, on an external server, however. The relative directory structure is the same and the targets very much exist in the directories which the error says they don't exist. Also, two months work of developer effort have gone into building this, and it's practically complete except for this behaviour. This strange, undocumented, quirky behaviour. Also, Atelier targets only 2016.2 versions onward of Cache (correct me if I am wrong). We have projects running on Cache 2009 as well and we need version control for those projects as well. I tried Deltanji early on, and it crashed my systems pretty badly. Never went back to it after that. The entire instance became unusable. I'll take this unexpected behaviour to InterSystems if necessary, but I got great advice from this forum on creating a dialog box within Cache Studio. And hence I'm holding out for a happy ending to this whole story, hence the posts. Is there another free reliable solution for version control for InterSystems Cache for Cache 2016.1 and backward? As far as I know of, no, but again, correct me if I am wrong. (No Deltanji family of products, please!)
It's very much a local drive. Thanks for your time. :-)