Get latest error

tafountain · Post by **tafountain** » Thu Jun 01, 2006 10:24 am

We have all of our developers now using Vault. Several of them are receiving this error:

Local file update for $/FSA_Legacy/Database/Migration/Data Migration/Upload.pif failed: System.UnauthorizedAccessException: Access to the path "E:\BCISOURCE\FSA_Legacy\Database\Migration\Data Migration\Upload.pif" is denied.

   at System.IO.__Error.WinIOError(Int32 errorCode, String str)

   at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)

   at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(VaultClientFile file, Int64 targetVersion, Int64 displayVersion, MergeType merge, DateTime dt, Boolean makeBackups, OverwritePrompt PromptData)

   at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(VaultClientFile file, Int64 targetVersion, Int64 displayVersion, MergeType merge, DateTime dt, OverwritePrompt PromptData)

Can you shed some light as to what can be causing this? All the other files in the same project folder in Vault were retrieved w/o error, however this one will not. It's a local drive to the user and they have full access to it. The file does not exist on the local file system.

Thanks in advance.

dan · Post by **dan** » Thu Jun 01, 2006 10:47 am

It looks like E:\BCISOURCE\FSA_Legacy\Database\Migration\Data Migration\Upload.pif is currently open or being accessed by another process. Do you have another program running that would have this file open?

tafountain · Post by **tafountain** » Thu Jun 01, 2006 11:19 am

As I stated in the original post, the file does not even exist on the local file system. I have verified this by looking at the status in Vault (Missing) and looking at the folder location. The file is not there.

dan · Post by **dan** » Thu Jun 01, 2006 12:28 pm

Ah, sorry to not read that carefully enough.

It looks like the working folder for $/FSA_Legacy/Database/Migration/Data Migration is E:\BCISOURCE\FSA_Legacy\Database\Migration\Data Migration. Is this path accessible to the local client? If you tried to manually create Upload.pif there, would you be able to?

tafountain · Post by **tafountain** » Thu Jun 01, 2006 1:21 pm

dan, you're the man (I'm sure you never heard that one before). Anyway, it was a problem with the virus scanner, nothing at all with Vault. The suggestion you gave was in the correct direction. Thanks!