It's very much a local drive. Thanks for your time. :-)

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.

Client/Server type mismatch.
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!)

First of all thank you for your prompt reply. Yes cmd at the run dialog very much works on my system. The windows command processor opens. What I don't understand is why $ZF(-1) and $ZF(-2) sometimes work and sometimes don't work. Even though I have the privileges and ownership as required by the Win 10 OS. I can't believe that this is unique to me, because my Cache team had this irregularity with these two commands sometime back during a migration to 2016 version. I understand you can't replicate it or study it. I appreciate your effort to do so, but what I want to know is has anyone else faced a similar problem with Ensemble 2016 / Cache 2016, Windows 10 / Server 2012 / Server 2008 / 64 bit configuration? Thanks in advance for your responses. :-)

Thanks a ton! UserAction is working perfectly now. I needed to give Quit $$$OK immediately after setting the values of the  variables like Action that are passed by reference. Thank you so much. You've been very helpful and very kind. Appreciate it!

First of all, thanks for your prompt response. Makes a lot of difference in situations like this.

W.R.T. the issue:

Yes, I tried commenting out the line. That resolves the problem instantly - no error message. This is definitely caused by the system call $ZF(-1) and $ZF(-2). This started happening when I tried to execute an executable I compiled with Visual Studio .NET Community Edition 2015. I did not use .NET binding - I simply placed the executable in a convenient location and made a $ZF(-2) call from within Cache Studio. For it's a GUI application - a call to $ZF(-1) makes it wait for the response indefinitely - hangs up the system. The executable was coded in C#.NET, with the use of a lambda. I understand that you will not be able to reproduce this issue. Can you send me an email ID in my email account registered with the forum? I'll send as much of the source code to you as I can. It's less than 300 lines - a minor fix.

I just set the method ^Test as Debug Target and execute by clicking Debug Menu->Go (Ctrl + F5)... from within the Studio. I've made applications in Cache, but this behavior is new to me. Need a response...

Configuration: Dell Inspiron 3542 Core i5 8 GB Cache 2016.1 and 2016.2 Windows 10 Anniversary Update