My serial numbers became invalidated over the weekend

[popezilla]

All my users are now getting this message:

Your serial number is not a valid serial number. User logins are currently disabled.

Last Thursday, everything was fine.

What is causing this?

[popezilla]

I am using Vault 2.0.5

One thing to note is that I had begun the process to upgrade to Vault 3.0 over the weekend but thought better of it and backed out of the install. I did not proceed very far in the install, I only got to the first input panel where I would specifiy if Vault would run under the network service id, or some other id.

Could it be that the install changed a setting and did not properly uninstall itself?

I know that the 3.0 serials do not work with a 2.0 Vault.

[dan]

The only way for the serial number to have changed is for the database to have been upgraded. So, either the serial number changed, or the server did actually get upgraded and is not recognizing the old format anymore.

Check Help->Technical Support in the GUI client to verify the version that is running (both client and server). Also, it would be good to restore your database backup from before the upgrade.

[popezilla]

The authenticating domain controller's CMOS date/time is whacked. It thinks the current DT is Feb 2003.

This is causing other problems on my network.

I fixed it and low and behold, Vault is back up.

Sorry for the trouble.

Thanks.

[lbauer]

We've seen this before -- if the server time is earlier than the time the serial number was created, it considers the serial number invalid. Glad you figured it out.