Renaming -"An existing connection was forcibly closed by the remote host."

[edarlak]

I am attempting to rename a vault, as well as the main project folder.  I was able to rename the vault by detaching and reattaching, however when I try to rename the project folder I get the above error.

At first I was trying to rename from a client machine, after about 2 hours of a dialog box reading "renaming folder", the error showed up.

I then installed the Vault Pro 2019 client on the same physical computer that is running Vault Pro server 2019, thinking it might have been a network packet issue.   Nope, after about 2 -3 hours of Vault trying to rename the folder, I get the same error.

The project folder I am trying to rename consists of about 260,000 CAD files, a good majority of them being versions files.  I did do a purge of the versions files before attempting the folder renaming.

Any solutions to this issue?  Is my vault too large (260,000 files, 280 GB) to where the renaming command is timing out?

[cbenner]

@JamesMcMullen any thoughts on this one?

[JamesMcMullen]

Hello,

I am not aware of a way to do this on that large of a directory.  Here is some background on what is happening.  When you rename the top-level folder, Vault will go through and open all the files in the directory and files related to files in that directory in order modify the relationships to the new folder name.  With over 260,000 files this will take a lot of time to do.  I am unsure if increasing the SQL timeouts would help in this situation since you would probably need the run the command for a weekend (it could take even longer).  

Thanks,

[edarlak]

I did try to change the timeouts to the max, being 14.2 hours.  However, I still get the error around ~2 hours after I try the rename command. 

I'm going to try again and keep an eye on the system memory, I only have 16 GB in this server, SQL might be using too much memory and killing the web services.

[edarlak]

Well so far it does not seem like a system memory issue.  The timeouts I changed were in the web.config file and the IIS default website.  Are there timeouts in SQL that I need to adjust as well?

[JamesMcMullen]

I would only modify the SQL timeouts in the web.config file.  Here is an article (for those following the thread):

https://knowledge.autodesk.com/support/vault-products/learn-explore/caas/sfdcarticles/sfdcarticles/H...

That is odd that it keeps stopping at the 2 hour mark.  Is there anything inside the ADMS Console logs that could shed some light onto the problem?  I am guessing it just says a generic timeout but I figured I would ask.

Thanks,

[edarlak]

Ok, those are the settings I already changed.  I will look at the logs to see what I can find.

I don't pay for Vault support, however I did contact my reseller, and they mentioned a Vault Data Transfer utility. However Autodesk does not supply that to end users, only to certified consultants.  Is there any way I can get this Utility?  I am working in a test environment at the moment.  I was told the cost to have a certified consultant come in to use DTU for just a folder name change would be cost prohibitive, I would agree.

If I cannot get my hands on DTU, as a workaround can I "GET" the entire vault project folder to a client machine, and use Autodesk Autoloader to upload the old vault data to a new vault with the desired folder structure and naming convention?

And from this thread: https://forums.autodesk.com/t5/vault-forum/vault-dtu-problem/td-p/7119646

I see that DTU even gets stuck after a couple hours of runtime...

[JamesMcMullen]

The problem with using Autoloader is that you will only get tip.  If that is acceptable, that is the best approach to take since it will gather the relationships and place everything into Vault accordingly.  DTU will not help in your situation.  The point of DTU is to allow someone to take everything from a "vault" and place it into another "vault".  It doesn't allow you to manipulate directories or anything which is what you are trying to do.  Also, it has the potential to really mess up your vault if you are not careful on what you are you doing.

Thanks,

[edarlak]

I'm not exactly sure what "tip" means, but I can explain what I am doing.

I have an old vault I setup ~14 years ago.  We only used it for .ipt and .iam files (as well as embedded analysis files), no .idw or .dwg files.  We now want to transition to making 2D drawings with Inventor, as opposed to generating with AutoCAD (drawings were not linked to models).  Currently we store our .dwg files in a network folder (these will be added to the vault at a later date with autoloader).  We also are transitioning from vault basic to vault pro, as we want to use items and apply life cycles to the items and have them propagate down to the model and drawing files. This is only for new content, the old vault content will be locked down and only be used for referencing, copy design, save as etc, no life cycles will be applied to the old content, no items will be generated for the old vault content.

What I have done is created a full backup of our vault basic vault.  I restored it to a test environment running vault pro. 

-I then detached the vault

-I renamed the filestore folder pathing in windows explorer (wondering if I should have used "move filestore instead?)

-I reattached the vault using the new desired name, and entered in the new filestore path

-I now am attempting to rename the project folder, and this is where I am stuck

The goal in the end, is to only have one project (hence the desire to rename the project folder), and not require users to switch between projects.  I really only need to rename the old top level project folder, I do not need to rename any sub folders. 

[JamesMcMullen]

Ah... it makes a little more sense now.  So, when I said "tip", that about the latest version of the file inside Vault.  Now, for what you are doing, I would do a get latest on everything you care about from the original Vault.  This will put everything local in the old folder structure.  I would rename the top-level folder to what you want the name to be.  I would clear out your new Vault of the data that you are trying to move from folder A to B.  Run Autoloader on the directory that you just renamed and move everything into your new Vault.  This will allow you to use the other functionality that you are looking at doing while maintaining history in your original Vault.  

Thanks,
Jim

[edarlak]

Well, I have tried for 1.5 days now to get Autoloader to do what I want, but I'm making no progress at all.  Even if I edit the Buu.xml file for the folder structure I want, it still requests some mapping that is not making any sense to me.

Also, after I "get" the entire vault, it seems I can't just change folders in windows explorer, because when the Autoloader scans the vault, it finds tons of errors that would take me weeks to manually fix.

Just about to give up...

[JamesMcMullen]

Do the files already exist inside the new Vault that you are writing too?  My understanding about Autoloader is that it looks and attempts to fixes references prior to pushing them into the Vault.   I am unsure how many errors you are seeing or how many files you are trying to submit.  If you are doing the whole folder, is it possible to break that down into smaller chunks?  

[edarlak]

No, at the moment there are no files in this new vault, just a new folder structure.

See the attached images.  What I am trying to do atm is autoload our library files into the new vault.  Now unfortunately, a lot of library .iam files have children that reside in the project folder due to users downloading step models, making derived .ipt's of step assemblies but not breaking the link to all the children before adding to the vault as a library component.

So Autoloader is asking me to map a second library folder, and I get the error shown below when I try to map that to the project folder.  This is where I am stuck atm.  I believe I would have to manually open up and check out all those derived library components and break the links, save and check them back into the old vault, then get them again before trying to add these files to the new vault via autoloader.

I'm just not finding an easy solution here.

[edarlak]

Well my theory of having some children in the project folder causing the double library folder pathing doesn't hold up.  I tried Autoloader with a small folder with just a handful of bolts and I get the same problem...

[JamesMcMullen]

Your attachment AL3.png looks promising.   Did you see errors at that point when you ran the scan?  In looking at AL1.png, I want to say that you need 2 library folders and a non-library folder.  Inside vault explorer you should see something like "projects" (non-library folder) and "Obsolete Library" and  "Content Center Files" (library folders) inside Vault Explorer.  On AL1.png, you would just map the folders you created inside Vault Explorer to the "Target Location" inside Autoloader.  Is it possible to get a screen shot of your root folder inside Vault Explorer?

Thanks,

[edarlak]

I tried making an another library folder.  However, when I select the "extra" "Inventor Libraries" folder that shows up in Autoloader to path it, it only shows me the Root $ with a Projects sub folder to select from.  It is not giving me an option to select any of the library folders.  I can't figure out why...

And yes, I have fixed all the errors.

[edarlak]

I've given up on Autoloader, in my opinion the tool is worthless for anything other than moving some small non-vault project into a brand new vault where you are ok with the vanilla Work\Designs path.  I don't see it as a valuable tool in a real world application where you have a substantial amount of vault data you're trying to load into a new vault.