Value cannot be null. Parameter name: activationCode

I'm getting this error message after logging in:
Value cannot be null.
Parameter name: activationCode

I recently upgraded from v4.0.6 to 4.0.7, and this message was the only response to my login attempt. I tried uninstalling and reinstalling (leaving the database in place) but I'm still getting the same error. Is it possible something went wrong during some database schema change?

It looks like your license key was never activated - there should have been a warning for that before logging in stops working (if you didn't see one, let me know).

Can you navigate directly to: http://buildmaster-server/administration/licensing to attempt to activate it?

Yes, that seems to be the case. I never did see the warning about activation, but I can get to the activation page.

Here's the root of the problem, though: I can't get BuildMaster to connect to the internet. Our office internet access is through a proxy, and it used to work but lately I haven't been getting any response - "Unable to connect to the remote server" any time it tries. The activation page directs me to do the manual process, which works, but when I copy in the generated activation code, it still can't connect to the server to verify it.

So, to summarise, this issue: solved. Proxy configuration issue: still a problem.

It shouldn't be connecting to the internet to verify the activation code - it is uniquely tied to the machine and license key so it would know without hitting the internet whether it works or not.

We will look into the proxy issue however.

All I know is that, when I click the "Save Activation Code" button, having generated it on the Inedo website, I get that same "Unable to connect to the remote server" error. Although the code should be possible to verify and save without connecting to the internet, it seems to be trying to do so anyway.

Can you enter a value into the Proxy_BypassUrls setting that will never resolve to a server, like "asdf"? This should restore the proxy connection to a functioning state.

It appears there may be a bug in the way that value is deserialized.

I found that setting in the database, but it didn't seem to help with proxy access.

Meanwhile, I got a new activation code which worked. I'm guessing the activation code I had was only for BuildMaster v3.x or something.

That setting is on the "All Settings" page and if you click Save on that page, the web application will be restarted (which is required for a proxy change). You'll also have to restart the BuildMaster service to reset the proxy settings used by deployments as well.

Everything seems to be back in working order now.