Vault 3.0 : "could not get public key from server"

Post by **jeremy_sg** » Tue Dec 14, 2004 2:08 pm

The installer for Vault 3.0.1 fixes this issue, as it correctly looks up the local name of the NETWORK SERVICE account. Also, it gives the correct permissions to the MachineKeys directory.

mabster · Post by **mabster** » Wed Dec 15, 2004 9:22 pm

It does? I just uninstalled 3.0.0 after getting the 'public key' error, and installed 3.0.1, and I still get it when I try to connect with the admin client.

Guest · Post by **Guest** » Wed Dec 15, 2004 9:47 pm

Ok - 'NETWORK SERVICE' definitely has full rights to that folder now - I just added it manually.

So I uninstalled and dropped the database from my SQL server (a different box). I also removed the sgvaultuser SQL user.

Reinstalled, no dice. Still get the public key error.

Uninstalled again, and reinstalled, this time selecting 'Machine' as my login type on the 'IIS Process Model'. Still no luck - same error.

This is a Windows 2003 machine, running English (Australia) as its language. Everything should be fine! Help!

Matt

mabster · Post by **mabster** » Wed Dec 15, 2004 10:19 pm

Me again (registered now

).

Would it matter that I'm installing via Remote Desktop (ie Terminal Services)?

And does it matter who I'm logged in as when I install? I'm logging in as my domain user, and I'm a Domain Admin.

Matt

mabster · Post by **mabster** » Wed Dec 15, 2004 11:13 pm

Think I've got it!

There was a file in that MachineKeys folder with a timestamp right on when I first installed, except it was only 50 bytes compared with the other files which were around 2kB!!!

So I deleted that file and reinstalled, and now the admin client can connect!

Post by **jclausius** » Wed Dec 15, 2004 11:15 pm

Was it the file identified in step 2 in this KB article http://support.sourcegear.com/viewtopic.php?t=231 ?

mabster · Post by **mabster** » Wed Dec 15, 2004 11:17 pm

Yep, that was it! Never saw the error described in that kb article, though.