They could be related. You could rename your calls table to CallsOld
re-create the calls table. If you don't want your old data, then
it and re-creating it would be fine. Since the calls table doesn't have
any DRIs, its an easy one. Follow these steps:
1. Using SEW, drop the Calls Table.
2. Load insttabs.sql in QA, highlight the Create Table Calls section and
click execute. You can also just execute the entire script without
3. Run in QA these scripts: insttrig.sql, instperm.sql
> In case it makes a difference, the server that SQL resides on, had the
> wrong year in it for about 12 hours. The year was set to 96 instead of 97.
> At 3am every night, SQL performs a diskdump on Emerald, however because of
> the screwy year, that may have caused something to get messed up?? There
> are entries in the Calls table for these calls (with the wrong year), but
> as with the other calls, calls that took place on ports 6-43 are missing.
I doubt the year would cause anything drastic to happen. Remember, the
RadiusNT lets SQL Server (not RadiusNT) set the calldate. This
the needs to have the clocks on all your RadiusNT servers set the same.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com