Springtime Changes! Upgrading to Autodesk Vault 2016

It's time to start my springtime upgrade to my Autodesk 2016 based products.  And I've decided to share my upgrade process again.  I hope that this helps you along your way as you consider your own upgrades.

I'm running Autodesk Factory Design Suite 2015, with Autodesk Vault Professional 2016.

Because of that configuration, I'm going to start with upgrading my server to Vault Professional 2016.

Why?  Vault Professional 2016 can run my 2015 and 2014 based products. So my new Vault server can support my 2014 and 2015 base products.  So if I can't upgrade Factory Design Suite right away, I can still access my Vault files.

You might think the next step is to click on that pretty, shiny, setup.exe file, but I would suggest considering a few things first.

• Check the server's system requirements.  Do you need up upgrade SQL?  Is there enough hard drive space?  Is the server's hostname "Wheezy", because that's an accurate description of it's current condition? 
• Do you have your Vault backed up?  And just because it was running fine the last time you checked, before going to the company Christmas party doesn't mean it still is.  Check again! 
• Consider running a test upgrade off line, if you have the capabilty.  And just because you've got a new server you've named NCC-1701 (you clever geek, you!), you might give Wheezy one last shot at glory before consigning to the Great Beyond.  Use it to test your migration off line! 
• Finally, if you have any network licensed products, like Vault Professional, for example, get those licenses ahead of time!  You're going to need them! 

I know preparation steps aren't fun, and they seem like a lot of extra work.  I rarely see a Vault migration go wrong, but the Titanic was making great time when it hit the iceberg.  You never want to be remembered as "the CAD manager who shut down engineering".

So now, the preparation steps are done. The backups are checked, verified.  Finally, it's time to run that backup.  

Now, click on the Setup.exe file that you've been getting excited about. 

Launching the Setup.exe

Once the setup initializes, run the precheck.  This is going to identify if there are any issues that need to be resolved before proceeding.

If you're used to 2015, the precheck has it's own button now

In my case, I did have an AutodeskDM directory already existing.  But if you get any error, click on the link.

Looks like we have a little fixing to do!

A list of possible solutions will appear.  I was able to resolve my issue by following the instructions listed.

Deleting the AutodeskDM directory per  the solution fixed my issue.

Run the precheck again to make sure that all issues are resolved.  Once the precheck is clean, click Install.

Now, we install! 

Next up is the End User License Agreement, or EULA.  Accept it and move on.  That's pretty much all there is here! 

Read this carefully (I know you do!), accept and continue!

After accepting the EULA, it's time to enter your serial number, product key, and if you're using  Vault Workgroup, or Vault Professional, your license server. 

Entering the information you need,. 

Clicking the next button will now ask you if you want to install with a new configuration, or with the previous configuration from your existing Vault. 

In my case, I'm using my previous configuration, so I choose that. 

Do you want to use the new configuration or default? 

Now, Vault will ask you which components to install, as well as what location your going to install to.  In my case, I'm using my D drive, so I change the install location. 

Now we get to hit the button we've been waiting for, Install.  (Cue music to 2001)

All I need to do is change my location here.

There's one more advisory that appears.  Vault tells us that it's detected an existing database, and in order to be useable, we're going to have to migrate it. 

This is just advising you that you'll need to\
igrate your existing database to make it useable. 

In this case, the point is to migrate it, so we'll say yes.

The install goes for a few minutes, depending on your machine.  The installer will run prechecks again, removed the old Autodesk Data Management Console, and install the 2016 version. 

Now we wait for the install.

Once the installer completes, you'll see your "Success" screen.  Take a second and pat yourself on the back!

If you're migrating an existing Vault, as I am here, You'll see another message to open your ADMS Console to migrate your databases.  It's a good idea to do that now. 

Starting the console to star the database migration.

The Autodesk Data Management Console will open and ask you to log in, and begin migrating the necessary databases. 

This is the process of migrating.  This can sometimes take a while for
large datasets.

 One more message is going to come through.  Vault is going to ask if I want to migrate my Vaults and custom libraries.  Which in this example, is what I want do to, so I'll answer yes. 

Choosing which databases to migrate.

One more question comes up, and it's one worth noting. Vault is going to ask which versions of Inventor you want to have your custom Content Center  Libraries available for.  In my case, I work with Inventor 2014, 2015, and 2016, so I'll  keep all three.

This is a good time to get rid of any unused libraries, it will make backups run a little quicker, and will save a little hard drive space.

Which versions of Inventor do you want your custom libraries available for? 

Once this is accepted, the final migrations are complete, and everything is done.

Now, just reconfigure, and validate your backups, and you're ready to go on to the next step!

In my case, installing my 2016 based client software!

Stay tuned!

P.S. I'm hoping to build a video for this as well, but videos take a while to create, particularly this one!

Look for it to be added in a future date! 

KETIV Introduces the Autodesk Vault "DIY Kit"

I think Autodesk Vault is a great tool.  I've use in in my personal "just joy of CAD" projects, and it's helped me be more effective when working in a production environment.

My Craftsman style coffee table.  It's been in Vault for years. 

Just the ability to go back and retrieve a previous version can be a lifesaver when a mistake is made (not that we ever do that!), or when a design changes, and it's important to retrieve a previous iteration.

But no matter how you slice it, properly installing, configuring, and using Vault effectively takes time, and planning.

And even thought "a journey of a thousand miles begins with a single step", the fast paced world of design can sometimes keep us dancing and we never take that all important first step.

In light of that reality, my colleagues at KETIV decided to "give you a lift", if you forgive me continuing the pun, and introduced a "Do it Yourself" kit for getting started with Vault.

Based on Vault Basic 2015, the DIY kit includes everything you need to get started with Autodesk Vault.

It includes videos to help you understand the components that form the framework of Vault, as well as describe the installation and basic functions of Vault.

It even gives you access to a Vault backup including sample data and preconfigured users and roles to get you started on the journey.

A screen capture from the Autodesk "Vault DIY Kit".

So if your interested in starting your journey, but weren't quite sure if you were ready to take that first step, here's the link to to the KETIV DIY Vault kit to get you started.

Maybe the thousand mile journey starts with a single step, but nobody said that the first step couldn't be into a classy ride with air conditioning, a comfortable ride, and a sweet sound system!

Lessons from a Simple Task - Using the Pause Command in a Batch File

Just today, I made myself work a lot harder than was ever necessary.  It started with a little bit of overconfidence, transitioned to about thirty minutes of frustration and swearing, and ended with success and a self deprecating laugh.

It started when I need to create a sample script to defragment an Autodesk Vault database.

How hard can it be, after all?  It's a short script.  It's only a few lines long anyway!

First, I grab the sample script from the Vault Help system.  You can find that in the defragment section at this link.

So now I have my command!

 Connectivity.ADMSConsole.exe -Odefragmentvault -NVault -VUAdministrator -VPadmin -S

This will fire up the command, but I still need to add my path information as well as my Vault name, I also need to add my administrator username and password.

REM - This Script Defrags the VAult Database
REM - Switch Legend
REM - Odefragmentvault ==> Command to defrag database
REM - -N Designates Vault name (this will vary machine to machine)
REM - -VU Vault user (must have administrator rights)
REM - -VP Vault password
REM - -S runs the script silently

D:\Program Files\Autodesk\ADMS Professional 2015\ADMS Console\Connectivity.ADMSConsole.exe -Odefragmentvault -NArduinna -VUadministrator -VP -S

IISRESET

So a little cutting and pasting I have the script I need.

Now, time for the test.

I run it once, it flashes on the screen and immediately disappears.

I check for syntax error, and I do find one.  Which I quickly fix.

But the script doesn't run.

I check my vault name, my administrator name.  My vault doesn't even have a password!

And for those of you with your mouse key on the comment button... I know it's bad practice not to have a password for the administrator!  But this is a personal Vault, on my laptop, which only I access.  So Thpppt! 

Finally, I have an idea.  One that I should have had a lot earlier than I did..

I add the word Pause at the end of my script.  So the script won't disappear when it finishes.

Let's take a second and think about this.

As soon as I run the script.  I see two words immediately. "Not Recognized".

I say phrases commonly found in garages, aircraft hangars, and factories everywhere.

The double quotes at the each end of the path are missing!

Wait! What? This is the problem! 

I look at my reflection in my computer screen.  "You Idiot!"  I shout, channeling my inner Ren.

It felt a little like this.
(From the Ren & Stimpy Show)

I should have known!  When running a command with spaces in it, you have to put the command inside of quotes.

If you don't , the script reaches the first space it sees, and tries to execute that.

So my batch file got to D:\Programs, tried to run that, and didn't know what to do.

In order to fix the script, I had to change the command line to look like what is below:

"D:\Program Files\Autodesk\ADMS Professional 2015\ADMS Console\Connectivity.ADMSConsole.exe" -Odefragmentvault -NArduinna -VUadministrator -VP -S

The quotes (in red) placed before D:\Program and after ADMSConsole.exe make all the difference in the world.

One more shot, and it runs fine!

So the final script looks like this.

REM - This Script Defrags the Vault Database
REM - Switch Legend
REM - Odefragmentvault ==> Command to defrag database
REM - -N Designates Vault name (this will vary machine to machine)
REM - -VU Vault user (must have administrator rights)
REM - -VP Vault password
REM - -S runs the script silently

"D:\Program Files\Autodesk\ADMS Professional 2015\ADMS Console

\Connectivity.ADMSConsole.exe" -Odefragmentvault -NArduinna -VUadministrator -VP -S

IISRESET

And that's it! It's ready to go.

Ultimately, what did I take a way from this one?

• Use the PAUSE command to help analyze scripts.  Because it was a short script, I figured if I studied it, I could find my error.  But I didn't see the missing quotes. I missed the trees because of the forest, if you will. By adding the PAUSE command, I found my error in seconds.  Literally seconds! 
• Slow down, you'll go faster.  Since this was an easy script, I thought I'd "bust it out quick".  Had I taken a little more time, and thought about my approach when I hit a snag, I may have solved it easier. 
• Pay it forward.  I made a mistake.  One I should  have been able to avoid.  Here it is for you to learn from.  Hopefully, you can use this to avoid the pitfalls I found! 

On a final note, there are several administrative commands that can be scripted using batch files in Autodesk Vault. 

Learn more about them by following the link to the Autodesk site here! 

How to Attach Content Center to Vault 2015 through the ADMS Console!

Recently, I found myself installing Content Center Libraries into Autodesk Vault 2015.  It was standard operating procedure; I've done it a dozen times.

One thing new to the 2015 version of Vault, is that the Content Center Libraries are downloaded from the link here, instead of being provided on the media or in explicitly in the download.

The installer even states that when you're select it from the Install Tools & Utilities screen. 

No Content Here!  But there is a link to download it.

If you follow the instructions in the readme file, the steps aren't too difficult.  Just download the libraries you want, extract them, click on the batch file, and wait for the libraries to install. 
And if that’s how you wish to install the Content Center Libraries, go right ahead.   It works nicely!

Compressed Content Center on the left.
Extracted and ready to go on the right! 

But if you desire, there is an alternative way as well, if you prefer.

Start out by extracting the files down to the point where you can see the libraries in question, they end in the *.mdf and *.ldf extensions.  For example.  AI2015_Inventor ANSI.mdf, and AI2015_Inventor ANSI_log.ldf if you’re using the ANSI standard.

The ANSI libraries extracted.

Take these files, and copy them into the location with the other libraries for Vault, this location can vary, as an example, the location on my own machine is. D:\Program Files\Microsoft SQL Server\MSSQL11.AUTODESKVAULT\MSSQL\DATA.

In my example here, I've copied the ANSI, ISO, and Feature libraries.  But you can copy as many or as few as you want. 

The libraries copied into the Vault library locations

This will make the files available Vault, but Vault does need to be told to use them.
In order to tell Vault that it’s going to be using these files, open the ADMS Console, locate the Library folder. 

 Once you have that, right click on the folder and choose Attach.

Attaching the libraries you want. 

The libraries that have been placed directory appear, and you can add them to Vault by selcting them and clicking OK. 

You'll have to choose each individually, but this only takes a few minutes for a big library, or just a few seconds for a small library. 

You can add as many, or as few libraries as you need. I'd suggest skipping any libraries you don't want.

The libraries are loaded. 

There it is! An alternate way of loading the Content Center Libraries into Vault. 

But that does beg the question "So what?".  Why would you load the libraries using the alternate way, instead of the other way? 

The truth is, you can use whichever way you want.  It matters little in the grand scheme of things.

But if you've already have the extracted libraries, or you don't have the handy dandy batch file available, this can be a quick way to get where you need to be. 

I've even seen some clever Vault Admins use the Detach option as a way of "deleting without commitment" . They detach the library and make it unavailable to Vault, so users don't have access to it.

If at some point it turns out the users *do* need it, they just reattach it, without having to go through the process of downloading and extracting. 

So keep it in mind as just another tool you can use to make your life a little easier. . 

The Vault Service is Alive and Well! Why Can't I find the Data Management Services?!?!

Not that long ago, I ran into a Vault issue that I can only describe as truly puzzling, and more than a bit nerve wracking.

It all started out with the phrase that will strike fear into the heart of any Vault Admin.

"Vault's down.  Engineering is at a standstill." 

In Vault world, this is the same as hearing "Shields are down, weapons offline, and the dilithium crystals are nearly dead."

If you haven't heard this phrase, you're lucky.  If you have, trust me, it'll make you want to grab a red shirt and join the away team.

Left with no choice, I plunged in.  With Vault off line, many scenarios become a possibility, most of them not good.

After all, there's nothing more dangerous than engineers with free time.  It's like the A-Team, MacGyver and the MythBusters merged Voltron style, and then downed a gallon of espresso before going to work

The error being displayed by every single client was.

I reset IIS, the IT Admin rebooted the computer.  The same error appeared.  

I checked the standard issue things.

• IIS?                           Running like a top
• SQL Server?             Serving SQL just fine. 
• Firewalls?                 Allowing traffic to pass. 
• Log files?                  Nothing out of the norm... so it seemed....

Meanwhile, engineering has accepted a dare to use old office supplies, stale chocolate, and a 63 VW Beetle chassis to create an upgraded version of Rock 'em Sock 'em Robots.

Finally, after a bit of searching, the solution presented itself in the form of the link on the Autodesk support site here. 

A document came up, the first thing it said was check for the following in the Vault logs.  You'll commonly hear them called "Vlogs", and can be found using the instructions at this link.

Error: Soap Exception ( mesg-id = 635298001452597277 ) 

Exception: WebServiceError [800]
 

Exception(Inner): There was no endpoint listening at https://avia-srv3/AutodeskDM/Services/_impl/SiteService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. 

Stacktrace(Inner): 

Apparently, for reasons unknown, there was an SSL error that was preventing the connection to Vault.  I don't know all the ones and zeros that would cause this, and now with engineering trying to attach flamethrowers to their super-sized boxing game, we were focused on fixing the issue.

I try the first steps in the solution, which are:

1. Start the Autodesk Data Management Server Console (ADMS) and go to Menu tools > Global Settings > Advanced Settings > Email.
2. Remove the selection from the "Enable Compatibility with SSL" option.

But that doesn't solve my issue.  When I try to go to the Tools pulldown, I get the following error.

Fortunately, the solution at the link contains instructions for that case too!

1. Use Notepad to open the web.config file from C:\Program Files\Autodesk\ADMS Professional 2014\Server\Web\Services .
2. Change the sslRequired key from "true" to "false." 

I run these solutions, and for good measure, type IISRESET at the windows command prompt to bounce the service.

Now, both the IT admin and I hold our breaths and cross our fingers.

And then.....

It works! 

The first user logs in, then the second, and so on!  Cue epic symphonic music!

The IT admin and I congratulate each other.  If we had been in the same room, instead of working remotely, we might have hugged.

It felt like we had just successfully disarmed a bomb! 

But in the end, what's the point?  Why am I sharing this?  Will another user out in there find this helpful?

I don't know, you may never encounter this error.  And I'm the first to hope you don't.

But if this little tip resurrects just one users' Vault minutes before engineering completes their time traveling DeLorean.  If one user is able to take this and say "I was able to minimize downtime...."

If one frazzled CAD manager is just a little less frazzled, then this post did it's job!

Autodesk Vault 2015 Service Pack 1 is Out!

It's that time again, a new Service Pack for Autodesk Vault.

It can be downloaded by clicking here!

So what are the steps to install it?

Without going any further, it's all spelled out in the readme files that are included with the service pack.  And no matter what you do with this blog post, you should be reading those!

This is particularly true if you're working in a replicated environment.  The steps in this post are the steps for a single site update!

These are the files you should reference!

With that being said, let's begin.

There are some steps that you should always do, when updating Vault, particularly with the server. It's just good standard operating procedures, and good practice

1) First make sure you have a backup.  

In reality, you should be checking this already, but this is a good time to make recheck and make sure.  There's always the chance of something unforeseen going wrong!

I've never had a service pack fail to install, but I've talked to people who've had power outages occur right in the middle of an install.  How is that for bad luck?

Be a hero, have a backup

Stranger things have happened
photo credit: Rogan via photopin cc

2) The system will be down for a while.

Don't plan on running this upgrade on the server in the afternoon just before a project is due.  The service pack migrates the database, during which time the Vault will be closed for business.

Don't be the guy calling tech support and end up being told "Yeah, dude.  You're just gonna have to wait for that to finish.".

These are common steps in planning, but they're often overlooked, and I think they're important to mention.

Now, we get to start the service pack process!

First, open up a command prompt by typing CMD at the windows start window

Once the command prompt opens.  Type IISRESET.  This bounces the IIS service.

Now, you can finally click on the *.msp file to start the Vault Server service pack.

You may launch when ready

Now it's just a matter of clicking through and waiting.  It's a good idea to follow the recommendations

Ready, set...

Now the service pack will install.  Give it time to finish.

Go! 

After a bit, the service pack will tell you it's done!

All done!  Or is it? 

Once the service pack is installed, open the ADMS Console, and make sure the databases are migrated.

Vault will ask you several questions during this series of steps. First, it begins a before you log in.

Migrating before logging in

Next, Vault will ask you to log in, and which Vaults to migrate.  I've never done anything but pick all.

What libraries to migrate

Now, there's more migration!

You might think you're done, but if you have custom content libraries stored in Vault, you're going to see a few more questions.  Vault is asking you if you want to keep copies of libraries for multiple versions of Inventor.  If you're not using old versions of Inventor, this is your chance to get rid of old libraries.

What libraries do you want to keep

Clicking OK on this dialog box brings up yet one MORE dialog box.  What I call, the "are you sure?" dialog.  It's a final confirmation to make sure that the clicks you've made are correct.

Are you sure that you're settings are right? 

Now, at long last, the screen we're hoping for.   Success!

So those are the basic steps.  Vault updates aren't that difficult with a little planning.

The next step is to move onto the clients installs.  Those are pretty easy, and while you should update the clients as soon as possible.  Those can be done at a much more leisurely pace.

Help! My Autodesk Vault Icons Are Having an Monochromatic Attack!

“Simple solutions seldom are. It takes a very unusual mind to undertake analysis of the obvious.”
 Alfred North Whitehead

I know I sound like a broken record, but still, I manage to remain busy, so creating videos has been forced to the back burner.  I am hoping to change that soon!

However, I'm still going to try keeping up with some simple tips.  And here is another one for those of us using Vault.  I ran into it just today.

I fire up my trusty seat of Autodesk Inventor, and go to grab a file from Autodesk Vault using the "Open from Vault" option.  And what do I see?

Nearly all my icons are grayed out!  I can log out, and log back in, but trying that doesn't do a thing!

Wait?  What?  Noooooo! 

What causes this?  Why would my Vault suddenly prevent me from getting to my files?

The solution is often, fairly simple.  Many times, and when I say many, I mean nearly every time, it's that the project in use isn't a Vault Project.

First, close all files.  Strictly speaking, this isn't necessary, but this will save you a step or two as we journey down this particular path.

Once all files are closed, go to the Get Started tab inside of Inventor, and choose Projects.

Time to pull the cover off. 

This step opens the project screen.  Check the active project. This is the one with the check mark by it.  Look in the lower pain, and see if it says "Vault" or "Single User".

If it says "Single User", you've found your smoking gun.

The project setting of "Single User" tells Inventor that Vault isn't being used by this project.  As a result, Inventor turns off the Vault mapping and tools relating to Check In and Check Out while this project is active.

Okay.  Now that the problem is known, how is it fixed?

There's two ways, and the solution depends on what's gone wrong.

Fix 1:  If this project is indeed the Vault project.  Right click on the "Single User" setting and choose "Vault".  If the project is checked into Vault, it's going to have to be checked out.

Switching the project

Fix 2: This is probably the most common cause that I've seen.  Make sure that the project hasn't been accidentally switched to a "Single User" project.  For example, if you've recently migrated to a newer Inventor version, the project may be switched to "Default", which is by nature, a "Single User" project.

If this is the case, double click on the correct project to activate it.  If you don't see it in the Project Editor screen, you may have to browse to it in your Vault working folder.

Resetting the project.

Believe it or not, that's it.  It can really be that simple.  But I have seen it happen more than a few times, and it's befuddled more than one user.

So if you see that your Vault icons are acting in shades of gray, check the project first.  It could be as simple as one little selection!

A Little Poll. Copy Folders in Autodesk Vault? Would you like that?

It's been another busy weekend!  So I'm afraid I'm still playing a bit of catch up!

But in my travels, a "curiosity" of mine was sparked.  A thought, a question, a musing...

What is it?  Is there a need for a "Copy Folder" function in Autodesk Vault?

In other words, if I have a folder of files that aren't linked to each other via linking or assemblies, (so Copy Design won't grab them all, would a one click copy be helpful?

Would a Copy Folder command be nice? 

In my personal use, it's a "meh" question.  I've never had the need.

But perhaps someone else has?

Answer the survey below!  What are your thoughts?

I'll keep this survey open until Wednesday, 20-Aug-2014!

Create your free online surveys with SurveyMonkey , the world's leading questionnaire tool.

**********************EDIT 2-Sept-2014 The Results!************************

The results are in.  The responses weren't huge.  Only 18 responses.  But thank you to those who took the few minutes!

And what was the conclusion?  A 50/50 split.  Right down the middle!

It looks like for some, it's quite important, for others, not at all.  

Curiously enough, during this time, the folks at Cadline Community created a blog post on what *could* be new features in Autodesk Vault 2015 R2.

Check that post out here.  Specifically, look at the Copy Design enhancements, one of which is Copy Multiple Data Sets.

It sounds intriguing!

***************************************************************************