Set up and troubleshoot Vault ADMS

00:09

Getting started with the "Vault" section,

00:11

we're going to start by validating the Vault ADMS Console and beginning that configuration.

00:19

There's some validation and some additional steps that need to be taken from the ADMS Console to utilize factory design utilities.

00:28

So I'm going to go ahead and launch my ADMS Console.

00:32

If you are running on a UAC enabled system,

00:35

you will get the message that I just received that says you do not have permission or access denied.

00:42

I'm going to go ahead and "OK" that, right click and I'm going to do "Run as administrator" to explicitly run this as an administrator.

00:50

This application does need administrative rights to start, due to database access among other things.

00:60

So, this has opened in the background. I'm going to click back.

01:05

I have no password defined because this is a demo environment, but go ahead and let that finish loading.

01:16

And the size of your "Vault" database does dictate how long this will take to load,

01:21

because while it is loading, it is querying database and getting statistical information,

01:28

which you will see shortly after the "Vault" loads.

01:33

Okay, so my "Vault's" just finished loading,

01:37

and you can see a bit of the statistical information that I was talking about it calculating.

01:43

I do have a large database on here at the moment. So you'll see that my database size is fairly sizable.

01:53

And I'm going to go ahead and I'm going to start by creating a "Vault."

02:00

Now, when you are utilizing factory design utilities, you need to utilize a factory design configuration file.

02:10

So to do that, I am going to create a "Vault."

02:15

If I right click on "Vaults" and I choose "Create," I am going to just call this one "Test" for demonstration purposes.

02:24

And then I am going to just leave the "Default File Store Location" because I am not going to be utilizing this "Vault."

02:31

I'm just creating it for demonstration purposes.

02:35

Normally, you would want to select a File Store Location that is different than a system drive such as the C drive.

02:45

And ideally a location that has some kind of hard drive redundancy as well.

02:53

I'm going to choose "Use Configuration." This is the important piece of this validation step or set up.

03:02

And then under "Configuration," I am going to choose "Factory."

03:09

From there, it is going to load this factory configuration file, which comes along with the installation of "Vault."

03:19

And you can see -- basically if you installed "Vault" on "C," it would be "C\ProgramFiles,"

03:25

and a very similar string.

03:29

With all of that in place the factory configuration, you can go ahead and hit "OK."

03:35

If you're curious about this file, you can go to that location, and it contains the configuration information.

03:44

I'm going to hit "OK" there.

03:50

And the creation does take a little bit longer, the more sizable databases you have as well,

03:56

but you should hopefully see, "Vault" "Test" was created successfully.

04:01

Obviously, you don't want to call yours necessarily "Test," unless you are doing some testing on it and intend to discard at a later date,

04:10

because there's not really an easy function to change the "Vault" name.

04:20

All right. And that is how you can set up the ADMS Console or the Vault itself.

04:31

This is a troubleshooting "Vault" step and can be skipped for the most part.

04:35

But for those that are interested, I have launched my "Vault" application, my ADMS Console, and it does not seem to be responding.

04:45

I run "Vault" on my laptop, for demonstration purposes and whatnot.

04:51

So, what I have done is I have pulled up my services because I suspected my sequel service was not running.

04:60

And if you bring up services, you can go down into the SQL section in that,

05:09

and you want to look for the "AUTODESKVAULT" instance.

05:13

This is "AUTODESKVAULT" instance.

05:15

If you have a additional instance or other instances, they may have a name or there's such a thing as a default instance,

05:23

which does not have a name.

05:25

"Vault" always needs to run in the "AUTODESKVAULT" instance. So I'm going to go ahead and hit "Start" there.

05:32

But before I do that, I'm going to kill off my ADMS Console.

05:39

So bring up "Task Manager" and I'm going to locate ADMS Console, which is "Autodesk Data Management Server."

05:48

And I'm going to "End Task" on it, that'll disappear.

05:54

Now, I can go ahead and hit "Play" on that service.

05:59

For the moment, I'm going to go ahead and bring up the agent as well and the browser is not running.

06:06

I'm going to start that myself as well.

06:10

The one that is most important is this "SQL Server."

06:14

I should not necessarily need to do an IIS reset, but as an additional troubleshooting step, I'm going to go ahead and do that.

06:24

So if I type in "CMD" from my "Start" menu,

06:30

I can right click and do a "Run as administrator" from the command prompt.

06:36

It's going to give me a "User Account Control" message, or UAC message. I'm going to hit "Yes" to that.

06:43

I'm going to hit "IIS reset," just like that. Hit "Enter." It'll try to do a stop and then a start.

06:51

If you need to stop IIS for any reason, such as you're going to be doing an upgrade and you don't want anybody accessing the system,

06:60

you could do an iisreset /stop.

07:04

So iisreset /stop and you can do that, that will stop your IIS services.

07:16

And, in reverse, hitting up arrow will bring up my last command here.

07:22

I can change this to start and explicitly just do a start and stop that way.

07:30

IIS reset will bring the IIS services down if they're running and it will start them up if they're not.

07:36

So typically that is the easiest path.

07:40

Hopefully, you found this informative.

Video transcript

00:09

Getting started with the "Vault" section,

00:11

we're going to start by validating the Vault ADMS Console and beginning that configuration.

00:19

There's some validation and some additional steps that need to be taken from the ADMS Console to utilize factory design utilities.

00:28

So I'm going to go ahead and launch my ADMS Console.

00:32

If you are running on a UAC enabled system,

00:35

you will get the message that I just received that says you do not have permission or access denied.

00:42

I'm going to go ahead and "OK" that, right click and I'm going to do "Run as administrator" to explicitly run this as an administrator.

00:50

This application does need administrative rights to start, due to database access among other things.

00:60

So, this has opened in the background. I'm going to click back.

01:05

I have no password defined because this is a demo environment, but go ahead and let that finish loading.

01:16

And the size of your "Vault" database does dictate how long this will take to load,

01:21

because while it is loading, it is querying database and getting statistical information,

01:28

which you will see shortly after the "Vault" loads.

01:33

Okay, so my "Vault's" just finished loading,

01:37

and you can see a bit of the statistical information that I was talking about it calculating.

01:43

I do have a large database on here at the moment. So you'll see that my database size is fairly sizable.

01:53

And I'm going to go ahead and I'm going to start by creating a "Vault."

02:00

Now, when you are utilizing factory design utilities, you need to utilize a factory design configuration file.

02:10

So to do that, I am going to create a "Vault."

02:15

If I right click on "Vaults" and I choose "Create," I am going to just call this one "Test" for demonstration purposes.

02:24

And then I am going to just leave the "Default File Store Location" because I am not going to be utilizing this "Vault."

02:31

I'm just creating it for demonstration purposes.

02:35

Normally, you would want to select a File Store Location that is different than a system drive such as the C drive.

02:45

And ideally a location that has some kind of hard drive redundancy as well.

02:53

I'm going to choose "Use Configuration." This is the important piece of this validation step or set up.

03:02

And then under "Configuration," I am going to choose "Factory."

03:09

From there, it is going to load this factory configuration file, which comes along with the installation of "Vault."

03:19

And you can see -- basically if you installed "Vault" on "C," it would be "C\ProgramFiles,"

03:25

and a very similar string.

03:29

With all of that in place the factory configuration, you can go ahead and hit "OK."

03:35

If you're curious about this file, you can go to that location, and it contains the configuration information.

03:44

I'm going to hit "OK" there.

03:50

And the creation does take a little bit longer, the more sizable databases you have as well,

03:56

but you should hopefully see, "Vault" "Test" was created successfully.

04:01

Obviously, you don't want to call yours necessarily "Test," unless you are doing some testing on it and intend to discard at a later date,

04:10

because there's not really an easy function to change the "Vault" name.

04:20

All right. And that is how you can set up the ADMS Console or the Vault itself.

04:31

This is a troubleshooting "Vault" step and can be skipped for the most part.

04:35

But for those that are interested, I have launched my "Vault" application, my ADMS Console, and it does not seem to be responding.

04:45

I run "Vault" on my laptop, for demonstration purposes and whatnot.

04:51

So, what I have done is I have pulled up my services because I suspected my sequel service was not running.

04:60

And if you bring up services, you can go down into the SQL section in that,

05:09

and you want to look for the "AUTODESKVAULT" instance.

05:13

This is "AUTODESKVAULT" instance.

05:15

If you have a additional instance or other instances, they may have a name or there's such a thing as a default instance,

05:23

which does not have a name.

05:25

"Vault" always needs to run in the "AUTODESKVAULT" instance. So I'm going to go ahead and hit "Start" there.

05:32

But before I do that, I'm going to kill off my ADMS Console.

05:39

So bring up "Task Manager" and I'm going to locate ADMS Console, which is "Autodesk Data Management Server."

05:48

And I'm going to "End Task" on it, that'll disappear.

05:54

Now, I can go ahead and hit "Play" on that service.

05:59

For the moment, I'm going to go ahead and bring up the agent as well and the browser is not running.

06:06

I'm going to start that myself as well.

06:10

The one that is most important is this "SQL Server."

06:14

I should not necessarily need to do an IIS reset, but as an additional troubleshooting step, I'm going to go ahead and do that.

06:24

So if I type in "CMD" from my "Start" menu,

06:30

I can right click and do a "Run as administrator" from the command prompt.

06:36

It's going to give me a "User Account Control" message, or UAC message. I'm going to hit "Yes" to that.

06:43

I'm going to hit "IIS reset," just like that. Hit "Enter." It'll try to do a stop and then a start.

06:51

If you need to stop IIS for any reason, such as you're going to be doing an upgrade and you don't want anybody accessing the system,

06:60

you could do an iisreset /stop.

07:04

So iisreset /stop and you can do that, that will stop your IIS services.

07:16

And, in reverse, hitting up arrow will bring up my last command here.

07:22

I can change this to start and explicitly just do a start and stop that way.

07:30

IIS reset will bring the IIS services down if they're running and it will start them up if they're not.

07:36

So typically that is the easiest path.

07:40

Hopefully, you found this informative.

Was this information helpful?