When Checking in a file that exists on local file system as an updated version but has an R-tag in the repository reserved by me, then I get a very generic "E03020176: No file agent to check in <filename>" while in previous versions, I could do this.
Article ID: 50588
Updated On:
Products
Issue/Introduction
Description:
I check out a item with "check out for update" --> SCM Workbench MODE = reserve only
I have a newer/changed version of this file on my Hard Disk that I want to check in.
CA SCM Workbench gives very generic error "E03020176: No file agent to check in <filename>". I am not using any agent so why am I getting this error and how can I overcome this?
Solution:
When a file is checked out for reserve only, then no actual checkout to the file system is done so there is no client path information recorded for this file. By design the file is just set to R-tag in the database in order to avoid anybody updating it while it is reserved. Therefore by design, the file should be checked in with release and then checked out for update in order to make the modifications (this will actually checkout the file to file system and therefore client path information is available).
However, there customers can use the following workaround in order to avoid having to do these interim steps:
- In the Explorer View in Workbench, right mouse click on the STATE name and choose Check in process (update and release) for New or Existing items.
- Select the modified file from the client side location.
- Perform checkin.
Notice that the R-tag version is updated with a N-tag version of the changed item.
Environment
Component:
Feedback
