I want to run Vault Mirror 2014 from a script file
The script is suposed to run the Mirror and then delete all non DWF files.
The part where its deleting the non DWF's is working perfect. But I can't seem to get the Vault mirror to run. I can call up the empty dialogue box.
Here is my script file: (it's a.CMD file)
off
"C:\ProgramData\Autodesk\ApplicationPlugins\Autodesk Vault Mirror 2014.bundle\Contents\V2014\VaultMirror.exe" -FullMirror -U Administrator -P XXXX -S Vapp00 -V Vault -F "D:\" -noFail
REM Reset all to read
attrib -r D:\Vault\*.* /s
REM Set all files to read only system except DWF and NWD
attrib +r +s D:\Vault\*.DWF /s
REM Delete all files
ECHO Y | del D:\Vault\*.* /s /q
REM Reset files to normal
attrib -r -s D:\Vault\*.* /s
All help appreciated!
You should always specify a log file by including -L "filename" in the command line. Any errors will be written to the log file. So that will probably tell us why the program is failing.
Hi Doug,
No log file and no difference
"C:\ProgramData\Autodesk\ApplicationPlugins\Autodesk Vault Mirror 2014.bundle\Contents\V2014\VaultMirror.exe" -FullMirror -U Administrator -P XXX -S Vapp00 -V Vault -L "D:\VaultMirror.log" -F "D:\" -noFail
Hmmm.
If you double-click VaultMirror.exe it will lauch the app in UI mode. Does it work through the UI with the same settings?
Is D an disk drive or a network location?
If D is a disk drive, I don't suggest mirroring to the root. FullMirror will delete anything not in Vault, so you want to be careful. Try creating a folder under D and mirror to that folder instead.
Morning,
The App works by double clicking on it.
I can run the UI from a script file by deleting all switches. So there is an issue with the switches. I'm just not seeing it.....
I managed to generate a log file:
014/08/07 05:00:00 AM
System.ArgumentException: Illegal characters in path.
at System.IO.Path.Combine(String path1, String path2)
at VaultMirror.FullMirrorCommand.Execute_Impl()
at VaultMirror.Command.Execute()
at VaultMirror.MainForm.Main()
As for D drive: This is a physical drive on the local machine where the VaultMirror is running
D drive has 2 folders in it:
ADSKFILESTORE This is the Vault Filestore
VAULT This is the name of the Vault where the Mirror is being written to.
I didnt want to create a folder then Mirror creates another folder with the name of the Vault inside of it. The folders inside have allready been mapped to publish to Buzzsaw and I didnt want to redo that set-up as it is finally working.
a Full mirror will only delete the files/folders that does not exits in the actual Vault and it should only do this inside the Vault folder. If it deletes anything outside of that folder then the risk is too great to use this tool as it resides on the Filestore for Vault. Creating another VM to run just the VaultMirror will make the set-up way too complicated. The whole system is currently running on 5 VM's through WAN optimisation servers.
Thanks for looking at the issue for me. Greatly appreciated.
It might be the -noFail switch. That was introduced in Vault Mirror 2015. So it would be an error in the 2014 version.
Hi Doug,
I tried using the IP address and it still doesnt work.
Logfile:
2014/08/08 10:28:00 AM
System.ArgumentException: Illegal characters in path.
at System.IO.Path.Combine(String path1, String path2)
at VaultMirror.FullMirrorCommand.Execute_Impl()
at VaultMirror.Command.Execute()
at VaultMirror.MainForm.Main()
Is it possible that I can have the uncompiled code for the App? I want to see if I can add the server details and compile it from there.
Thanks
Anton
The source code is included in the SDK, which is a separate install. You can find the installer in the SDK folder under your Vault install location.
Once the SDK is installed, you can find Vault Mirror in the "VS10\CSharp\VaultMirror" folder.
Can you please tell me:
what arguments go into these fields VDF.Vault parameters in the Command.cs file:
VDF.Vault.Currency.Connections.AuthenticationFlags.Standard
Thanks!
I'm not understanding your question. However, you can find the documentation for all the API classes in the "docs" folder of the SDK.