There's a good chance that arerror.log has recorded the server attempting to load the rogue active link at startup. If that is the case, and the active link is corrupt, it will not appear in the admin tool, but will still exist in the database. This would subsequently result in the unique index error.
Two options would seem to be: 1) rename the rogue active link through the database (update actlink set name = 'newName001' where name = '##insert your actlink name here##'; or 2) delete the active link from the database (find the active link ID and remove entries from the corresponding database tabels) In both instances, restart ARS. Glen _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
