Hi did you try something like : xcopy d:\builds \\server\sharename
do not use a mapped drive letter, just the UNC name if the service is running with the correct credentials, this should work with kind regards Ruben Willems On 30 April 2012 16:49, KenBobPDX <[email protected]> wrote: > I have setup a CC.NET installation and had it working great until > recently. Since about a week or two ago my CC.NET installation cannot > see any of the network shares. It manifested itself in a failure in a post > build step using XCOPY. I Googled CC.NET and XCOPY and found a few > references and tried those solutions without success. I also noted that > the shares were SAMBA shares so I Googled some more with CC.NET and SAMBA > and tried those solutions, also with no success. I have the service > running under a user account with the proper privleges on the target > machine that is hosting the share. I can see the shares and write to them > from a logged in user session using that account, but when running as a > service, the service cannot see the shared drives. I have issued a NET USE > command in the post build step to confirm my diagnosis and the NET USE > command shows that the network shares are not available. I don't > understand why it was running fine for weeks and then suddenly stopped > working. I noticed another posting recently talking about a similar issue, > so I'm wondering if MS issued a security fix recently that is causing this > issue. Any help would be greatly appreciated. Thanks.
