NETWORK SERVICE account required when using domain account

joshyeager · Post by **joshyeager** » Fri Jan 07, 2005 8:27 pm

I chose the DOMAIN\MACHINE$ option when I upgraded to Vault 3.0.1, but the Vault Web Service kept throwing errors about being unable to access the directories under Temporary ASP.NET files.

Finally, I figured out that I had to give the NETWORK SERVICE account full control over the directory, in addition to the domain account.

I was running Vault 2.0.5 using the NETWORK SERVICE account, but I switched to the domain account for AD integration. Is that why I still needed to give the NETWORK SERVICE account access?

In general, I love Vault. But, I think that your install could be a little more helpful when it comes to configuring permissions. (-:

Josh

Post by **jeremy_sg** » Sat Jan 08, 2005 3:30 pm

Getting these kinds of install and setup issues straightened out is one of our top priorities for the 3.0.2 release.

joshyeager · Post by **joshyeager** » Sat Jan 08, 2005 10:37 pm

Sounds good. I already got 3.0.1 running on my server, but I'm sure that there are other people who will appreciate your efforts. (-:

Vault is awesome, a smooth install process will make it even better!

Keep up the good work, guys.

Josh