Where does urchin store its license and serial number?
Peter M. Abraham
I backed up the initial installation of Urchin 5, then did a
migration, and now get an invalid key message.
If I try to reactivate, I am told the "serial code already activated"
without an option to reset it.
I think I can solve the problem by restoring the file(s) that Urchin
uses for the license and serial number.
What files do I need to restore?
Thank you.
Jeremy Aube
The license activation is specific to the machine and location where
Urchin is installed. You can reactivate your license on the new
location once your serial code has been reset. If you fill out the
form located here:
http://www.roirevolution.com/urchin/urchin-reset.htm
we can reset your license for you.
Jeremy Aube
http://www.roirevolution.com/urchin
On Dec 30, 12:14 am, "Peter M. Abraham" <peter.abra...@dynamicnet.net>
wrote:
Peter M. Abraham
Thank you for the form. If the location varies, what are the file
names?
Thank you.
Jeremy Aube
You can't reactivate the Urchin Installation by restoring any files
from the previous installation. The activation is location/machine
specific and can't be transferred from one machine to another or one
location to another without resetting your license. Once your license
has been reset, you will be able to enter your license serial code
from the interface for the new instance just as you did with the old
instance. There's no transferring of files necessary.
If you send us your license serial code, we can reset your license for
you. If you still have access to the old interface, you can find this
number under Settings -> License -> Serial Code under License
Information. If you no longer have access to the interface, you can
get the Serial Number by running inspector from the util directory of
your old installation. Otherwise, this number is also available from
the ucgl_serial field in the globals table of the Urchin MySQL
database. Note that you'll also see a number for ucgl_license here,
but you can't just transfer this number to your new Urchin server as
it is dynamically generated upon activation.
Jeremy Aube
http://www.roirevolution.com/urchin
On Dec 31 2009, 8:36 am, "Peter M. Abraham"
Peter M. Abraham
On the target server, let's say I do a fresh install. Everything
works, but there is no data (no profiles, no reports, etc.). The
license works which is the key.
I then backup the target server making sure every Urchin file is
backed up including the working license files (even though I don't
know the names -- all directories that I know Urchin uses is backed
up).
Then I migrate from the source server to the target server, and now
the license doesn't work.
In theory, I should be able to restore just the license files from the
target server (which has the correct license etc.) if I just knew
their names (if I know the names, I can find the locations).
Can you please share the file name(s) used by Urchin to store the
license key?
Thank you.
Jeremy Aube
The license information is not stored by itself in a single file. If
you took a file from the back up and replaced the same file on the
target server, assuming everything still worked somehow, you would
have changed much more than just the license information. The
configuration data is stored in a proprietary database, so there isn't
a 1-1 correspondence between file and configuration setting.
If you want to get the license information, you can probably run the
following commands on the backup:
/path/to/backup/urchin/util/uconf-driver action=get_parameter recnum=1
parameter=ct_license
/path/to/backup/urchin/util/uconf-driver action=get_parameter recnum=1
parameter=ct_serial
each of these commands will return a value. Let's say the first value
is value1 and the second value is value2. You can then run the
following commands on the target server:
/path/to/urchin/util/uconf-driver action=set_parameter recnum=1
ct_license=value1
/path/to/urchin/util/uconf-driver action=set_parameter recnum=1
ct_serial=value2
Here's another option:
1. Run uconf-export (also in the util directory) as part of your
backup of the target server. Let's say you've saved this export as
File1.
2. As part of your migration from the source server, you'll run uconf-
export to get the source server configuration. Let's say you've saved
this export as File2.
3. Before you import File2 to the target server, edit it and look for
the lines for ct_license and ct_serial.
4. Find the same lines in File1.
5. Replace the values for ct_license and ct_serial in File2 with the
values for ct_license and ct_serial in File1.
6. Save File2 and import.
Jeremy Aube
http://www.roirevolution.com/urchin
On Jan 5, 10:26 am, "Peter M. Abraham" <peter.abra...@dynamicnet.net>
wrote:
Peter M. Abraham
Thank you!