The ServerAccess table in Emerald 2.1 is bad. The RadiusNT 2.5
update replaces it. You can ignore this error on a transfer.
> ::Error::
> In file NS.Emerald.DR1 in statement on line 302
> Transfer Status: Creating DRI on destination database
> Unable to create constraint. See previous errors.
This is a result of the above failure.
> ::Error::
> In file NS.Emerald.FKY in statement on line 251
> Transfer Status: Creating Foreign Keys on destination database
> data exists in table 'dbo.Invoices', database 'Emerald', that violates
> FOREIGN KEY constraint 'FK__Invoices__Type__465D7A27' being added. ALTER
> command has been aborted.
This means you have an InvoiceType entry in your InvoicesTable that
doesn't match an entry in the InvoiceTypes table. Its not a show stopper
but should be looked at. I don't think InvoiceTypes are even used
in pre 2.5 releases.
> ::Error::
> In file NS.Emerald.FKY in statement on line 251
> Transfer Status: Creating Foreign Keys on destination database
> Unable to create constraint. See previous errors.
Result of above.
> ::Error::
> In file NS.Emerald.TRG in statement on line 1
> Transfer Status: Creating Triggers on destination database
> Invalid column name 'login'.
> ---------------------------------------------
This is most likely the Calls table trigger. Only the SubAccounts
table has a login field. You can just re-run the insttrig.sql
script on the new box to correct this.
> Anyone knows the 'appropiate' steps to follow to transfer Emerald from one
> machine to another one?
Actually it looks like everything did tranfer OK.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com