Message 9 of Message 10 of Message 11 of Post Reply. Helpful resources. Check it Out! Click here to read more about the December Updates! Read More. Launching new user group features Learn how to create your own user groups today! Learn More. View All. Top Solution Authors.
User Count. Top Kudoed Authors. That this behavior does not vary based on whether all devices are redirected in the RDG CAP or if everything except the clipboard is disabled. That I specifically want redirection only for the clipboard; that is, I do not want direct drive access via Explorer, printer redirection, or other device redirection. So, although I have fully tested unsuccessfully with that all enabled, it would not be a particularly good option even if it solved the problem.
After all, see 4. That there is a long history with Windows R2 RDG in which clipboard redirection fails entirely, including text, not just files , and that, reliably, all one has to do is to fix it, at least until it fails again at some unpredictable future date, is to enable all device redirection, apply that, then disable all except clipboard redirection, and apply that. Then one can copy and paste text and files.
But that does not solve the specific problem with Windows 10 host file copy. But that is mostly old news, and I was trying to be succint in my post by not including irrelevant information. Well, there turned out to be a red herring here, one that, in retrospect, is making more sense than when it first occurred to me a bit earlier that I might have something masking the issue.
It has to do with how CAP restrictions are applied to a user that is a member of multiple groups. It just never occurred to me until late in this process that the specific CAP, or more properly, group membership, could be masking the issue. So, first of all, I apologize for the wild goose chase, and I infer that CAPs are more or less cumulatively restrictive, rather than cumulatively permissive, but it now leads me to these two questions:.
I would try it the other way since Domain Admins is more "specific", although, since you removed the admin account from Domain Users it doesn't matter now. That was part of what mystified me. The Admin CAP is first on the list, but nothing I did to that one made any difference; file copy simply would not happen.
A nice side effect is that if the old PDB is still locked, it just adds another. The next time you build: MyProject. Finally, restarting Visual Studio and doing a fresh build will get rid of both of these, and continue the process as usual.
Chances are you have a bug that's keeping it alive and are not stopping the debug process correctly - there are options to detach from the process when you click 'stop debugging' instead of actually killing the debugger so maybe you have that set.
But that's the problem - the file you're trying to copy over is locked ie still being used by the OS so its preventing the copy. Ensure that file is free and you'll be able to copy. May be one of them was not disposing connections, bindings, etc. It is now working fine to me. Killing the process w3wp. Generally, you can know the process that has the lock on the file by navigating to the bin folder and trying to delete it. The error message that will pop up, in case another process is using it, will contain the name of the process that needs to be killed.
The problem is gone. The removal of the vshost process accessing the file does not work most of the time since the process isn't accessing the file. The simplest workaround that works and takes the least amount of time is to remove the project from the solution, build another project in the solution and then add the original back.
It's an irritant and waste of time but it's the least expensive of all the other options that I know of. If none of the answers works, try this simple check. Find for any MSbuild. Kill MSBuild. No need to reboot or restart VSx.
With some experience you can add a pre-build script to delete old files or rename then out-of-the-way in case there's a lock. See this other answer.
Basically, you could have MSBuild. But again, see the previous answer for more specific details. I finally how fix it. Why we can't continue debug after the first debug because the first debug exe still running. I have noticed some answers that solved my problem, BUT, just in case anyone is having the same problem I was. Make sure you have closed out any console windows that may have been opened from a previous build.
For instance I was just testing some code in a console application, I didn't realize that the console window from one of the previous times I ran my program was open. During that session I was debugging, the window got pushed to the back and I couldn't see it. Just saying, this could be your problem, so check to make sure that is not the problem.
If you are debugging T4 templates , then this happens all the time. My solution before MS fixes this would be just to kill this process:. After killing the process, was able to rebuild process, without restarting OS or VS What helps then is to check if you can add a Dispose pattern, for example if you're adding a DbFixture and the database contacts isn't disposed properly. That will cause the assembly files being locked even if the tests completed. Then, dispose the related contained propertys and explicitly assign them to null.
That will help to end the tests in a clean way and unlock related locked files as soon as the tests ended. The same pattern you need for the test class itself - it needs its own Dispose method as shown for the DbFixture class above :.
I didn't realize I still had my debugger attached and was trying to build in the same Visual Studio instance. Once I stopped the debugger I was able to build. Killing the vstest. If that doesn't work, then also killing QTAgent How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Visual Studio "Could not copy" Asked 8 years, 5 months ago. Please contact your system administrator for assistance. GenericLog GenericError 1 f1e:0 client. SBL-UIF I'll get this section divided into different parts -- i Normal environment where we are getting this error -- This error message pops up when certain webtemplate files are missing.
A particular webtemplate has been modified and have not been migrated to server. Need to check for any modifications made by Developers for the webtemplate and if those have been properly migrated to the Siebel servers. For further reference, look for Bug: Issue related to obsolete webtemplate has been resolved under this bug.
0コメント