I'm having merely same issue as in Team Build cannot copy diagnostic activity log to the drop location, but couldn't resolve the issue.
TFS is installed in our server and build agents are created over there. And i'm accessing TFS in my dev machine as an admin, and created a new Build Definition. I created a Drop folder(Shared to Everyone) in my dev machine(DEV1) Path: \DEV1\Drops.
The Build is getting succeeded when the drop folder path is not specified. But it fails when i provide the drop folder's path \DEV1\Drops. and i'm getting the following error.
Exception Message: TF270016: An error occurred publishing log files from
'C:\Builds\1\TFS_Process\Project_for_TFS_Build\src\Main\Project_for_TFS.log' to
'\\DEV1\Drops\Project_for_TFS_Build\Project_for_TFS_Build_20131112.2\logs'. Details: The
network path was not found.
I found a way to get it work, but not exactly. Why is,
I created the drop folder in the server where TFS is installed and it works.
There is some network issue connecting Client machine to server, due to which i didn't manage to create the drop folder to get it work.
Related
I published my code from local to Terminal Server (Prod). I have everything set on Orchestrator like Robot, Environment, Processes and NuGet package uploaded. I started running the job and it fails after 1 minute of running.
I am getting error saying "Read range error on Orchestrator". I have valid config file on Terminal Server. I even checked Excel activity on Studio it is up to date. Don’t know where the issue is. Could anyone help me here. It would be very helpful in running my bot on Production.
Note: I am using Studio 2018.2.3 and Orchestrator 2018.4.1
On Local machine it is running fine and I am getting this issue only on Orchestrator on Terminal Server
The issue I am facing earlier was related to Dependency files which were missing on Terminal server’s local drive. I copied all dependency files like Excel activities, RestSharp, csvhelper and Newtonsoft.Json from Local machine to Terminal Server under .nuget folder.
Moreover we have to sure we have the same path for %AppData% in both Local and Terminal server.
I have one automation project which does the job of building the setup using NSIS wrapper. The project is built with the VB6 code. During the execution of the project I am getting the error for deleting a file as “Method 'DeleteFile' of object 'IFileSystem3' failed” for the method ‘FileSystemObject.DeleteFile’ with force option set to true.
Scenario:
Server (Windows server 2012) drive is mapped to the local windows 7 system and whole operation is run in this mapped drive in client machine. And the project is run on the client machine.
Now when I run my project to build the setup, it copies all the application files to a folder called Temp under build1 and build2 directory and then it builds 2 separate setup exe using the NSIS (makeNSIS). After the creation of NSIS setups, it will delete all the source files from temp folder. While deleting the MDAC_TYP.exe file, I get the error as mentioned above. The above said error comes for both the Build1 & Build2 folders and the error comes occasionally (not every time) for the same exe.
I cannot rename/delete/move the file in any of the PC through UNC or even in server it cannot be deleted. If I try to rename/delete the file or its parent folder, the system from where I try to delete/rename gets stuck.
Other methods I tried are as below.
Tried my project under testing environment and there was no such error.
Checked for file handle using process explorer in both client as well as server – No handles were found
Checked for Open files in the Shared folders of the server. - No open file connection found for the file.
Tried rebooting the client machine – Not solved.
Tried to delete/Rename the file using command in server – Not possible.
Tried to delete/rename the file in server – No error and no message. Instead, server gets stuck.
Checked for disk problems using chkdisk in server. No problems reported.
Folder permission – The user ha full permission and there is no issue.
Tried running the same build process after reboot – Everything works fine. But, again repeats after some time/day.
Tried disconnecting the mapped drive at the time of error exists. But, still not able to rename.
No antivirus/Event viewer log in both client as well as server
After all these still I could not able to explain why exactly the error occurring.
Update:
I recently noticed that the same error also occurs when deleting the file msstdfmt.dll
Update 2:
I also got error for the ms word file, error is same. In all the 3 cases i found that there is only a common thing that is all 3 files has read-only attribute.
VSTS build suddenly has errors when Get source.
Always the same error occurs after I delete the _work folder. Even after delete the agent and create a new one, it still fails but with a different identity number...
What happened?
So I have reviewed the link to solve this problem, as referenced below.
Team build error: the path already mapped to workspace
But my problem is that EVERY time i queue that Build Definition i get the same problem. Ok, i go delete the tfs workspace it's complaining about. Great it works! Then run the build again... ok now it doesn't and i have to go delete the TFS service workspace all over again.
How come TFS build service is stepping on itself every time it does a build. The error is " Unable to create the workspace 'xxx' due to mapping conflict... the path xxx is already mapped in workspace 'xxx'" but the mapping is to a workspace that the previous BUILD created. Not anything from a specific user.
ok, this seemed to occur because (i hadn't noticed) that i changed the "Build Agent Folder" specification by accident to a fixed path. rather than keeping it with $(SourceDir). I changed the entry in the build definition to this and it worked fine, after multiple builds using same build definition.
I'm trying to utilize SVNBridge so that my team can use our existing TFS server as our Xcode repository.
SVNBridge appears to be set up correctly on the TFS server, and I can connect to it from Xcode as an SVN repository to grab everything and commit changes.
However, when I have another member of my team update to grab a file I just committed, they receive the following error:
svn: REPORT of '/!svn/bc/36163/-TFS folder structure-': 200 OK (http://-tfs server url-:8081)
The also happens when they update a file, and I then try to update.
We both have full read/write access to the TFS structure.
There is nothing in the SVNBride logs folder on the TFS server.
Any thoughts on the error, or is there a better solution I should use for this?
y0-1, happens all the time for me.
Possible causes are
1) urlscan, check the logs
2) ..svnbridge folders, I usually connect to TFS with native client and delete them, it's a pain cause there are a lot of them usually. After deleting ..svnbridge folders you might want to re-checkout parts of your project where you deleted them and sometimes svnbridge restart is required.
Also svnbridge log usually conatains very usefull info ;)
p.s.
Just realized, that you said that your svnbridge log is clean, that's odd, maybe it is not configured properly(usually folder permissions)
f.e. mine svnbridge log with the similar error on update -
Message : The item 'blah-blah-blah' does not exist at the specified version.
User :
Request : REPORT /!svn/vcc/default HTTP/1.1