Hi
We are trying to add some users to our new vault 2 server - unfortunately I dont seem able to activate licences on the new server.
If I use autoactivation I still get "The request failed with HTTp status 407: Proxy authentication required" and therefore cant use this.
If I press the here hyperlink to generate the email I get
"An unhandled exception has occured....... (edit) .... The system cannot fid the file specified". Ive tried this on another box that has the admin client installed and get "An unhandled exception..... (edit) ..... Access Denied". I cant seem to find a way to get the key that I need to send to source gear, although I'm going to try a few more boxes.
Version wise were on 2.0.0.0 - and although the proxy authentication is an old problem the click here thing seems to be new to version 2.0.0.0.
Thanks lots for any help
Jim
Activating new licences problem ver 2.0.0.0
Moderator: SourceGear
For the proxy issue:
In version 2.0, the proxy credentials for getting through to the license server are coded to just copy the credentials from the proxy used to connect to the Vault Server. I can see that it would have problems if you didn't have to go through the proxy to get to the Vault server, but you did need to go through the proxy to get outside. If there is a way that you can trigger proxy authentication when logging in to the Vault Server, then that auth data should be used for the license server connection as well.
In version 2.0, the proxy credentials for getting through to the license server are coded to just copy the credentials from the proxy used to connect to the Vault Server. I can see that it would have problems if you didn't have to go through the proxy to get to the Vault server, but you did need to go through the proxy to get outside. If there is a way that you can trigger proxy authentication when logging in to the Vault Server, then that auth data should be used for the license server connection as well.
502 / Proxy error activating licences now.
jeremy,
Im not sure that i understood your reply. I thought that you were saying that it uses the same connection that is used to connect to the vault server, but then i saw you mentioned the credentials from the proxy en route to the vault server.
Anyhow I tried unticking bypass proxy server for lan addresses and I have changed the error to : http status 502: Proxy Error (Host Not Found).
How is this supposed to work and where is it that I can specify the proxy credentials that are to be used ? I thought initially it was using the IE default settings, but from your post i now think i was wrong.
thanks
Jim
Im not sure that i understood your reply. I thought that you were saying that it uses the same connection that is used to connect to the vault server, but then i saw you mentioned the credentials from the proxy en route to the vault server.
Anyhow I tried unticking bypass proxy server for lan addresses and I have changed the error to : http status 502: Proxy Error (Host Not Found).
How is this supposed to work and where is it that I can specify the proxy credentials that are to be used ? I thought initially it was using the IE default settings, but from your post i now think i was wrong.
thanks
Jim
We do use IE's proxy settings, but they can be overridden by editing the VaultAdmin.exe.config file in the Vault admin tool install folder.
Have you had any luck in getting the email button to work on different machines with the Admin Tool installed? Note that the admin tool version number has to match exactly to the server version number for activation to work.
If you already has activated licenses, and are trying to activate new ones, you may need to de-activate all of them before re-activating all of them. This can be a scary thing, since if it fails, everyone is locked out. Before you try this, send me email and I can give you a demo serial number that will cover any downtime you might have due to unactivated licenses.
Have you had any luck in getting the email button to work on different machines with the Admin Tool installed? Note that the admin tool version number has to match exactly to the server version number for activation to work.
If you already has activated licenses, and are trying to activate new ones, you may need to de-activate all of them before re-activating all of them. This can be a scary thing, since if it fails, everyone is locked out. Before you try this, send me email and I can give you a demo serial number that will cover any downtime you might have due to unactivated licenses.
Still no luck
Ive tried several machines now (6) and I either get access denied or file not found on all of them. Is there any way I can get the information that it sticks in the email without clicking on that link ?
My guess is that the problem here is that we are supposed to be using NT4 and we only have email support on NT4. Our XP development machines dont have email on them and its likely that steps have been taken to disable the use of email on the XP boxes, hence why the admin tool cant popup the email. whats wierd is 3 of the boxes i tried worked with the pre version 2 admin clients.
I just had a look at the vaultadminconfig file and had a brief look at MSDN, however it looks as though I cant specify credentials in the config file so I'll have the same problem no matter which of the settings it uses.
I dont understand the temporary key solution - how do I activate the temporary key and how do i deactivate the licences if I cant reactivate them - to me it just looks as though I'm going to annoy 70 developers by removing their access if I try this.
Jim
My guess is that the problem here is that we are supposed to be using NT4 and we only have email support on NT4. Our XP development machines dont have email on them and its likely that steps have been taken to disable the use of email on the XP boxes, hence why the admin tool cant popup the email. whats wierd is 3 of the boxes i tried worked with the pre version 2 admin clients.
I just had a look at the vaultadminconfig file and had a brief look at MSDN, however it looks as though I cant specify credentials in the config file so I'll have the same problem no matter which of the settings it uses.
I dont understand the temporary key solution - how do I activate the temporary key and how do i deactivate the licences if I cant reactivate them - to me it just looks as though I'm going to annoy 70 developers by removing their access if I try this.
Jim