Access to the path "554.24171" is denied.

Thomas Linder Puls · Post by **Thomas Linder Puls** » Tue Mar 23, 2004 2:24 am

My collegue gets a message box saying:

Access to the path "554.24171" is denied.

The "path" is different from time to time.

We do not have any files or directories with names like that.

What does this mean?

Post by **jclausius** » Tue Mar 23, 2004 8:42 am

thomas:

what type/version of vault client is your colleague using?

Thomas Linder Puls · Post by **Thomas Linder Puls** » Tue Mar 23, 2004 9:21 am

Sorry I forgot to say this: Version 2.0 (i.e. 2.0.0)

Post by **jclausius** » Tue Mar 23, 2004 10:58 am

what is the type of client?

vault ide, vault gui, vault command line? if vault ide, what are you using? ( vs.net, vs.net 2003, etc. )

Thomas Linder Puls · Post by **Thomas Linder Puls** » Wed Mar 24, 2004 4:49 am

Client: Vault GUI

Post by **jclausius** » Wed Mar 24, 2004 8:56 am

thomas:

does this always happen during any certain operation? such as "get latest", checkin, rename, pin, etc.

or is it random?

Thomas Linder Puls · Post by **Thomas Linder Puls** » Wed Mar 24, 2004 5:00 pm

During "get latest"

Post by **jeremy_sg** » Wed Mar 24, 2004 5:29 pm

Thomas,

To answer your question, files named in that format are Vault's baseline files. The error means that during a get, when Vault is trying to do something to the baseline file (open it to do the three-way-merge to update the working folder, copy it when no merge is needed, etc). Most likely, we just need to put in code that opens the baseline file to catch that exception, wait a second and then retry opening the file.

I'm assuming that this error happens infrequently and unpredictably.

Thomas Linder Puls · Post by **Thomas Linder Puls** » Wed Mar 24, 2004 7:19 pm

Yes, at least we have not spotted any pattern (expect that it is only one person that has encountered the problem).

Thanks for the help.

mattFleming · Post by **mattFleming** » Wed Apr 07, 2004 7:08 am

I have seen the same problem, and I just checked the logs and there is no entry detailing what went wrong on the server side. Are there client side logs?

I am using the Vault Client version 2.0.1(2137)

Matt Fleming

Post by **jeremy_sg** » Wed Apr 07, 2004 9:03 am

If anyone consistently gets this error, email me and I'll send a build of 2.0.2, which we think will fix the problem. We can't reproduce it here, so it would be good if you could try it out and let us know if it's still happening.

mattFleming · Post by **mattFleming** » Wed Apr 07, 2004 9:17 am

Jeremy I have gotten it to happen pretty regularly this morning. So go ahead and email it to me.

Matt Fleming

Post by **jeremy_sg** » Wed Apr 07, 2004 1:30 pm

We've tracked this down with mattFleming's help. The cause of the problem was in performing repository deletions, when a folder had been deleted. The problem should be corrected in Vault 2.0.2.