(Views)Popular Topics
Wish List 177861
Dispatch Web Interface 56749
Anyone having problems wity binary merges in 3.8? 45555
Windows Explorer Support 45276
Anyone implement a CI process in AccuRev? 40249
Beta testers needed for Report Generator 31767
Show all non-backed files 25618
UndoRevert 11628
AccuRev log monitor 11338
Web Inteface for AccuRev 10949
Topic Options
Rate This Topic
#2714 - 12/23/10 02:34 AM Some files were "busy" update failed
AndyR Offline
stranger

Registered: 11/04/10
Posts: 14
Has anybody come across this issue when updating their workspace...

"Some files were "busy". Either they do not have write permission
or they are in use by another program"

This has stumped me! Iíve checked permissions, run process monitor to see what could be using the file, rebooted the machine you name it! The accurev log unfortunately from what i can see only tells me what updated "ok" not the file causing the issue.

Does anyone have any ideas? Any suggestions would be much appreciated.

Cheers,

Andy.

Top
#2715 - 12/23/10 06:37 AM Re: Some files were "busy" update failed [Re: AndyR]
jtalbott Offline
AccuRev Evangelist

Registered: 01/18/06
Posts: 360
Hi Andy,

Try deleting your <path_to_user>/.accurev/ac_tmp_map.txt file, and then re-running your update.

Incidentally, if you aren't on 4.8 or 4.9 yet, we've resolved several key issues relating to update. I'd strongly recommend upgrading your AccuRev instance.

Cheers,
~James

Top
#2716 - 12/24/10 02:52 AM Re: Some files were "busy" update failed [Re: jtalbott]
AndyR Offline
stranger

Registered: 11/04/10
Posts: 14
Hi James,

I tried deleteing ac_tmp_map.txt, unfortunatley this did not fix the issue. Our centralised server is version 4.7 can I upgrade my local client to 4.9 and connect to this a 4.7 server still ?

Thanks,

Andy.

Top
#2717 - 12/24/10 07:56 AM Re: Some files were "busy" update failed [Re: AndyR]
jtalbott Offline
AccuRev Evangelist

Registered: 01/18/06
Posts: 360
No, you'll need to update both client and server to 4.9. I highly recommend this.

In the meantime, as a workaround, you should be able to resolve your update issue with the following:

* check for modified files in the workspace, Keep any that there are
* run "accurev update -9"
* from the root dir of your workspace, run "accurev pop -O -R ."

You should then be in a consistent state. If that doesn't work for you, I'd suggest you open a Support case with our team.

Cheers,
~James

Top
#2718 - 12/24/10 08:02 AM Re: Some files were "busy" update failed [Re: jtalbott]
AndyR Offline
stranger

Registered: 11/04/10
Posts: 14
Thanks James,

A colleague did exactly that for me which resolved the issue.

Many thanks & Happy Christmas :-)

Andy.

Top


Moderator:  Brad, jtalbott