[New! Vault Basic 2019 Keygen Again Zip Full
Betty Neyhart
I had Vault Basic loaded on my machine at the start, then I had to have my machine reloaded. I was not able to backup the vault thru ADMS (speaks to another thread I had). I have since reloaded Vault and since that time, I have gotten it to the point where Vault and Inventor are connected and seeing each other, but the issue while I am able to check items in (except drawings for some reason), I cannot check them out.
I will offer a few opinions. Please do not take these as absolutes, but I would like to think they might be helpful. First, the Inventor project file message seems to indicate that Inventor is set to use a single project file, or one that is not in the vault. Switching it may help. In Vault, in the Tools - Administration - Vault Settings, on the Files tab, if you open the Working Folders Define, do you see a place toward the bottom to set the consistent Inventor project file? I find that helpful, although it won't keep Inventor from accidentally changing the default project file (that is still the user's responsibility to maintain).
Looking at your filestore errors, I don't know that this will help, but it seems to be a good practice to simplify your location. I generally set up a folder, C:\ADMS\Filestores, and set my vault filestore under there. Obviously, you will have to have permission to write there, but I would keep it out of your 'My Documents' area to simply things. You can change this in the ADMS console. Expand the navigation panel until your vault is displayed. Right-click the vault and use the 'Move File Store' command to move it to a new location. My two cents.
Based on the error message, It sounds like someone may have deleted the filestore directory on the server . The filestore directory is where all the vaulted files are physically stored and losing it would cause quite a few problems - including backup issues. If the folder is indeed missing then you may have to restore from a previous backup to get back into a good state. As previous commenter also mentioned, having this directory under a user's documents is very unusual - that would make it prone to being deleted if that user didn't know what it was for.
The setup here where I work is unusual. The reason I have the Vault working folder in "My Documents" is because here they setup an external HD sitting on my desk that backs up local docs and settings. Because I am the only one in the company currently using Vault, and because permissions have not allowed it to be loaded on a network, it has to be setup this way if I want my vaulted files to be regularly backed up. Without me having to manually copy/paste to a different location.
If I didn't mention this before, I had Vault loaded when I first started here about 6 months ago. So, some of these files were vaulted files previously that were in a different vault working folder. Since I was having issues with my PC, everything got wiped off of my PC and the system was reloaded. Prior to the reloading, I posted a series of issues (in a different thread) that did not allow me to use the backup functionality within the ADMS. So, I did a manual copy/paste (to back them up prior to the reloading) from a network drive and to the "My Documents" folder as you currently see it after Vault was reloaded. The issue I am describing in this thread is happening to brand new files only associated to this vault go around as well. Hard to believe that a brand new loaded vault as you described Paul, would be looking for the vault from prior to the reload.
I did go into the setting within Vault as you outlined Mark, and did set the project file there (never had to do this one before in using Vault in the past). It is no longer giving me the "000" project error, but rather this error. Still not allowing checking out of files. I will add that the copy design now seems to be working, but if I can't check them out or open them up out of the Vault, not sure how I would get them. Also still cannot check drawings into the vault as I described in my original post. Baby steps.
Thanks for your help guys. Hopefully I can get this resolved. Having used Vault Workgroup at my previous employer and liking the functionality of it, I am trying to sell the usage of this software to my current employer in showing the benifits.
After doing some further experimenting, I can now get/checkout files, which at least puts a copy on my local. That at least solves the how to get copy design files. Still can't open from the vault as per the error message I posted in my last posting.
I have a few suggestions. First, Autodesk recommends that you save your Inventor project within the vault at the root ($) level. If you need to reposition it, make sure you first close Inventor, and if you move it, get a new local copy and make sure you repoint Inventor to use the new file. Secondly, make sure Inventor's project file is set to the right file. That second error typically means that Inventor is set to the wrong project file. The third message indicates that you need to make a connection between your local folder structure and the vault folder structure for you content center library folders. Generally speaking, we create a library folder 'Content Center Files' in the vault just below the ($) root. In your local workspace create a corresponding folder. Check out your project file in the vault, then open Inventor, log into vault, and use the Map Folders command to specify the relationship between them. This command can be found on the Vault ribbon, in an 'Access' pulldown on the left side.
With all due respect, it would seem that you could benefit from a service call by your reseller's technical staff to help you get all this setup correctly. I fear that you will run into other settings that are not in place. Just my two cents.
I can so appreciate your point about calling the VAR. I have had formal Vault training, but purly from a client and administrator perspective. At the time of that training our Vault was already setup. So, I never worked with the ADMS up until this point. I have set this up strictly on my own. As far as calling my VAR? That is a little strange as well. In all of my years (20) of using 3D modeling softwares, I have never (up to this point) been in a circumstance where I have no VAR to call. Meaning, my company is owned by a larger company that approves all software used. Because this larger company is based out of Germany, they purchase the software over there and push the licenses down to us here in the USA. So I am stuck going through these channels to try and resolve these issues. To be quite honest, I have found these forums to be a heck of a lot more useful then VAR's at times. Not to mention, I could put in for this level of Vault training, but the problem is, I am the only one using it in the company because I am trying to convice the powers at be that this software should be used corporately. Which is a battle in and of itself.
Thank you again for your help. I look forward to further suggestions to get this resolved. If you read my original post, I did have this Vault setup on my machine as a stand alone prior to my machine being reloaded. Weird that I did have to go through all of these hoops the first go around and everything checked in and out just fine.
When I posted my previous response, I never noticed this, but when you look at the Vault folder image in my last posting, it shows "Content Center Files" and "WBA Projects" at the same level. In my working folder on my system, "Content Center Files" is inside of "WBA Vault". All the folders you see in that image inside of "WBA Projects" are actually inside of a folder called "WBA Vault" on my system. There is no "WBA Projects". Thinking this is the issue that I am having. So, you were partially right in your first points. I think as soon as I figure this out all will be well. Not sure how this ended up this way.
Still having these issues. Can't check in drawings into Vault. Shows as I posed in my first posting as not saved, but does not show the checkin screen when initiating a checkin. Copy design works for some but not others. Can't open files from the Vault. The only difference between this go around and last is that my Vault working folder is in "My Documents" For the reason I stated earlier. Really frustrated in the current way Vault is performing. I will continue to research, but if there is anymore insite I would greatly appreciate it.
Look forward to heariong back from you. I still can't check in drawings into the vault. Well, most I am not able to. Some I am. Weird. Not sure if this is date related. Meaning drawings that were created prior to the reinstallation of the vault some are able to check in, where as ones created after are not. But what is weird about that is I can check in the new drawings prior to adding model views to ie, but as soon as the model views are added I get and see what I described in my initial posting. Copy design will sometimes work and other times it will show the interface dialog in the vault but give me this error after selecting "OK"
This may be a tangent, but: How did you restore your Vault after the rebuild? I know you were not able to run a proper vault backup, so you copied the files out of the filestore to your external drive. Did you stop the vault server processes and copy the SQL database files at the same time as you copied the filestore files? If not, I wonder if Vault made changes to the database that were not synced to the filestore correctly? I don't know that Vault can be damaged this way, but I understand that with our Windchill system both the database files and the filestore have to be captured concurrently.
I have attached a screenshot showing my vault working directory setup. Mine starts at the directory C:\Customer Name. The only .ipj file in my vault is in this directory. The standard content center files are in a sub-directory called CONTENT CENTER DATA and the inventor design files are in the *WORKSPACE file. I scrubbed customer id info from the screenshot. Do all your inventor files fit in a structure like this? Please post a shot that shows where you save your inventor files, not where Vault puts its filestore.
795a8134c1