Look at the early post in this thread posted on 9/1/2011.
Basically the older vault version strated to show the user info as it received it from the query and allowed the user to scroll through as it was being loaded. Autodesk changed it so that now it will not show the user anything until ALL of the data is downloaded from the vault server including preview icons, etc. My guess is that you have a fair number of entries in each folder. So if you do have a large number of entries in each folder this is a killer.
Not sure why Autodesk would make such a change however their testing obviously did not test for the case of having a flat file directory, which is what our original dealer suggested we do when we first installed back in 2009.
I do not think this is the issue entirely. There is a setting within the ADMS Console which allows you to change the number of items to show on a page in the Vault client within a range from 25-1000. I have set this to 25, so displaying 25 items on a page is not a large task at all. The other difference with 2012 is that it does show folders in the grid view as well as files. I am going to change the filter to only show files to see if this helps.
If I improve this at all I will report back. Thank you for your response.
I dont think that is your problem either. There would have to be thousands of files in the one directory for it to take that long. Just curious though, how many files are in the directory you are trying to display?
One on my largest folders has about 2000 files and it takes only a few seconds to load all the data the first time I click on it. If I go to a different folder and come back to this one, it loads much quicker the next time.
Time it takes once clicking on the Root or a folder:
Project Explorer ($) - 3 Folders - 1 File - 36 Seconds
Project (Folder) - 11 Folders - 1 File - 2 Mins 38 Seconds
The weird thing is, if I do a search on that folder or on the Root, it displays quick like it should. It's just when it's populating the main grid just by clicking on a folder.
Also, the Web Client takes a long time to login intially and about the same time (maybe a little less) when you click on the same Project folder above.
I'm working with Autodesk right now to try and get this resolved. Initially we thought it was an IIS issue, but we created another dummy Vault, (of course it didn't have any data in it except a few files and folders) and logging in via the Web Client and clicking on the folder in the thick client displayed like normal. We are now thinking it's a database issue. I'm uploading the database to them tonight for further investigation. I pray I get this fixed. This is going to be unacceptable if we cannot resolve it.
I am experiencing the same annoying problem with one of our customers.
They have a pretty big Vault database, 12.5Gb . With Vault 2011 they didn't experience any problem at all, everything worked like a charm and it was really fast.
After upgrading to Vault 2012+SQL 2008 Full SP2, same hardware of the server, same hardware on the clients, same configuration, same antiviruses, etc etc...everything went down the hill: the grid takes ages to popullate and show up, even for little folders, the normal operations of checkin/checkout are incredibly slow, and until now I haven't found a solution yet.
I have already tried almost all the solutions provided in the other posts in this thread, without any luck.
The only thing I haven't tried yet is the SQL maintenance plan, but I read that others tried it with no success.
I will let you know if we find a solution: in the meanwhile, the customer is very angry with Autodesk and is already checking how to migrate everything to a competitor software...
What I have found to fix this issue is to modify the memory usage inside SQL. By default SQL will use as much memory as it can get it hands on. If you set a limit, the performance seems to increase.
Log into SQL Management Studio
Right-Click the AutodeskVault Instance
I have found success with using a value of 8192 (8GB).
I have also found using anything above this value brought the issue back. Autodesk claims this is an issue with Microsoft SQL and 64 Bit OS.
Let me know if you see success by modifying this value.
Along with the suggestion posted by Matt (SQL x64 only), also look into setting up / verifying the SQL maintenance plan. Additionally, any exceptions that were set in the AV software will need to be updated to reflect the 2012 product line - IE, if you have an exception set for C:\Program Files\Autodesk\ADMS 2011\ADMS Console\Connectivity.admsconsole.exe, it will need to be updated to reflect the 2012 console executible.
Yes, it does. Set it accordingly to how much you have on the system The system I had been working with had 56GB of RAM. It was disappointing to know I could only use 8GB of that for SQL.
I solved my problem.
This is what I did; it could lead to solution also with your similar problems:
- I checked in the IIS, and I noticed that the Default Website was using the ASP.NET 1.0 instead of the 2.0, and corrected the mistake
- I stopped and restarted the MSSQL$AUTODESKVAULT service
- I configured the list of researchable properties of the files, diminishing their number ( I didn't deactivate them, just made them not searchable)
- Defragged the DB
- Scheduled an SQL maintenance plan, following the instructions in the Advanced Configuration Guide of Autodesk Vault
Of all the above things what really helped in improving the performances was the stopping and restart of the SQL service. The SQL tends to grow in size inside the RAM of the server, and when it reaches around 2 Gb it begun to slow down the whole service. In my case, it took at least 8 hours to reach that size, even with no customers working (i.e. at night).
The solution was scheduling this 2 lines of code which run every MORNING at 07:00am before the customers get in office. In this way, they aways begin to work with a clean SQL service, fresh and just started and everything works like a charm.
Those are the 2 lines to stop and restart the service (put them in a .BAT and use the scheduled operations of windows to run it every morning):
net stop MSSQL$AUTODESKVAULT /Y
net start MSSQL$AUTODESKVAULT
the /Y is needed to run it in silent mode; otherwise it would ask if you are sure.
I hope it will help you solve some of your performance problems too.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.