Error: File currently in use....but it's not

Error: File currently in use....but it's not

Anonymous
Not applicable
7,232 Views
21 Replies
Message 1 of 22

Error: File currently in use....but it's not

Anonymous
Not applicable

I've got a user who, in Acad Mech 2019, when attempting to open up a file gets an error that states:

"xxxxx.xxxx.dwg is currently is use by (the user attempting to open said file and the user's machine). Would you like to open the file read-only?"

 

We've cleared his local working folder and his cache, still same issue. He also states he gets this error on Acad files he's never opened, which really puzzles me.

 

Any suggestions on how to clear this? Is there a "reset" option for Acad like there is for Inventor?

0 Likes
Accepted solutions (1)
7,233 Views
21 Replies
Replies (21)
Message 2 of 22

Anonymous
Not applicable

Let me also add that we've deleted the lock files (.dwl & .dwl2) that we could find.

0 Likes
Message 3 of 22

pendean
Community Legend
Community Legend

While in AutoCADMech2019 have the user activate WHOHAS command, then go and select that file: what info is presented as the answer?

And by chance is the user in that same folder, inside Win10's file explorer, with file preview turned on?

Message 4 of 22

Anonymous
Not applicable

When the user performs the "Whohas" command, he gets "User Unknown".

 

0 Likes
Message 5 of 22

RobDraw
Mentor
Mentor

That probably means that the file is not opened by anyone.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 6 of 22

Anonymous
Not applicable

Which is basically the case here.

The user attempts to open the file, but he gets the error saying the file is already open by him, on his machine, but will only allow him to open it as read only. He claims he's getting this error on files he's never opened prior.

Thus the reason for this post.

0 Likes
Message 7 of 22

RobDraw
Mentor
Mentor

Has anyone (IT) checked the permissions for the folders that the files reside in?


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 8 of 22

pendean
Community Legend
Community Legend
"And by chance is the user in that same folder, inside Win10's file explorer, with file preview turned on?"

0 Likes
Message 9 of 22

Anonymous
Not applicable

LOL...I've asked him that 3 times now, no reply. But I doubt it.

I will verify though.

0 Likes
Message 10 of 22

Anonymous
Not applicable

OK, user states he is not viewing the files in such a way.

0 Likes
Message 11 of 22

RobDraw
Mentor
Mentor

@RobDraw wrote:

Has anyone (IT) checked the permissions for the folders that the files reside in?


How about moving the files to a different location?


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 12 of 22

Anonymous
Not applicable

Rob,

 

Permissions are fine and no, can't move the files as they all reside on a specific set of folders for that specific project.

Doing so would mess up a lot of other people all working on the same project. This user is one of roughly about 25 people currently working on this project.

 

All files are in Vault and this error comes up for any file he attempts to check out and open.

Seeing he's the only one getting this error, it has to be something local obviously.

The problem is finding that needle in the haystack.

 

Note: this same use is also seeing issues with his Model Tree browser graphics slowly vanishing the longer he's in the application. Adesk is looking into that as we speak.

What I'm hoping to try today is, have him work on a different machine and see if he experiences the same issues (this and the model tree issue). If so, that would lead me to think his profile has gone corrupt and needs to be recreated.

0 Likes
Message 13 of 22

RobDraw
Mentor
Mentor

I'm not familiar with Vault but doesn't the checkout process involve making a copy of the file to a specified location for the user? If you can't move the files, copy them so as to not interrupt other users. That should have been obvious.

 

I'm suggesting trying a different location, just to rule out any issues with file access.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 14 of 22

Anonymous
Not applicable

Rob,

Vault does as you say, but it also syncs with the users local hard drive as far as a working directory.

Moving files out of it's set location on the users HD would breaks all links to associated files, etc. basically rending the file useless for the user. Think: a drawing with broken links to the models in its views would open up with no models in its views. Hope that makes sense.

 

I understand what you are saying, but we've checked, no issues with permissions, etc for these files or the location.

Again, he gets this error when opening a file whether it's in Vault or if he already has it on his local.

For whatever reason, even on files he's never opened before, Acad sees that the file is already open by him on his machine and throws that error. It's very strange.

0 Likes
Message 15 of 22

RobDraw
Mentor
Mentor

Who cares if the links are broken? We are only trying to open the file to rule out a possible cause. But if you want to put a cross out that one without testing, that's your call.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 16 of 22

Anonymous
Not applicable

Jumping in late here, but just a thought- as suggested in an earlier post, it sounds like the user's account in Windows, or profile in AutoCAD has issues. Can your IT folks create a test account for this user to log in with from the same workstation? New test AutoCAD profile, again on same workstation? Broken user accounts can create all sorts of weirdness...

0 Likes
Message 17 of 22

Anonymous
Not applicable

Rob,

 

As I've stated, it doesn't matter, he has permissions to the folder and all other folders on his HD.

No matter where he opens the Autocad file from (the current project, or any other project/location) he gets the error.

 

In a Vault environment, links do matter. If the user moves the file from one folder to another on his C drive, all links are blown and the user will have to resolve each broken link to continue opening the file. Our assemblies have 10's of thousands of parts in them, you do the math. Yes, I understand it's only temporary, but to do so would be the same as him opening an empty file....and again......he gets the error any time he attempts to open any file in Acad.

 

I don't know how else to break it down for you.

0 Likes
Message 18 of 22

Anonymous
Not applicable

@Anonymous, That's what Adesk Tech and I believe is the cause here.

The request has been put in to IT to rebuild his profile. Hoping they get to it today.

0 Likes
Message 19 of 22

RobDraw
Mentor
Mentor

You don't have to move the file, you can make a copy of it like I said earlier... I don't know how else to explain any simpler for you.

 

Does Vault use the same location for the checked out files or do they go to different directories?

 

If the user cannot open AutoCAD files from any location, I would check out the user profile as others have suggested.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 20 of 22

Anonymous
Not applicable

@RobDraw wrote:

You don't have to move the file, you can make a copy of it like I said earlier... I don't know how else to explain any simpler for you.

 

Does Vault use the same location for the checked out files or do they go to different directories?

 

If the user cannot open AutoCAD files from any location, I would check out the user profile as others have suggested.


=================

OK, Rob, you're just still not understanding things and I'll attribute it to your lack of understanding on how Vault works with files. I will not go into it here.

 

But even making a copy of the file and moving said copy, will still break links for that file. It would be the same as opening an empty file in a different folder. He's done this and gets the same error. If he attempts to open a file that's never been in Vault, it happens. If he opens a file that he's never opened before, it happens.

 

He gets this error whenever attempting to open any Acad file, point blank.

 

Why are we circling around on this, I just don't know.

 

 

0 Likes