Can't use Vault after running DCPROMO

anotherlab · Post by **anotherlab** » Mon May 03, 2004 7:35 am

I have the Vault installed on a Win 200 Server that was a domain controller. We just ran DCPROMO so that the server is no longer a domain controller. Vault no longer allows anyone to login, we get the Cryptography error message. I looked at the message about giving everyone full control to the folder \Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys

That folder no longer exists on the server. How can we repair Vault and have it recreate the folders and permissions that it needs?
thanks,

dan · Post by **dan** » Mon May 03, 2004 8:11 am

It might be easier to simply uninstall the server (keeping the database of course), and then re-install, rather than try to track down the configuration changes needed.

anotherlab · Post by **anotherlab** » Mon May 03, 2004 8:25 am

Can I just run the installer over the existing installation? I didn't see Vault in the list for Add/Remove programs.

dan · Post by **dan** » Mon May 03, 2004 9:27 am

That's strange - did you install it as a different user than you are currently logged in as?

It is worth a try - if the installer can run (without complaining that it is already there), it should be fine.

anotherlab · Post by **anotherlab** » Mon May 03, 2004 9:46 am

I probably installed it under an admin level account that was a domain account. This machine was the DC and only member of a domain. When we ran DCPROMO, we made it a member server of our main domain. This toasted the account that Vault was installed under. It also toasted the ASPNET account and the machinekeys folder.

What I should have done was installed Vault before running DCPROMO and then reinstalled it after I had reinstalled .NET.

CraigNicholson · Post by **CraigNicholson** » Sun May 09, 2004 3:13 pm

I've seen a similar problem discussed with other .NET web applications on Domain Controllers. I think there are a few Knowledge Base articles discussing it. Try the following from a command prompt:
CD %WINDIR%\Microsoft.NET\Framework\v1.1.4322\
Aspnet_regiis -i

That should fix the .NET Framework configuration.