Re: [Emerald] consolidation errors - update #1

Dale E. Reed Jr. ( (no email) )
Sun, 07 Feb 1999 09:39:07 -0800

Tom Bilan wrote:
>
> I'm getting "SQL Server Error: 2627 Violation of PRIMARY KEY constraint
> 'pk_CallHistory': Attempt to insert duplicate key in object 'CallHisotry'
> State=1, Severity=14" when running consolidation.
>
> The screen says "Calls Processed So Far: 495" and the blue bar has a long
> way to go.
>
> I hit OK and then in runs for a few minutes and then gives me the same error
> with a different account. When I hit OK it went to "Calls Processed So Far:
> 567"

Is this an Updated Emerald 2.x or a new 2.5 install? What, use the
enterprise manager and tell me what the key on your CalLHistory table
is (double click on the Calls history table and it will show you).

Because you can now have multiple Call History Entries per period,
the Mins and Calls columns must be included in the Key as well.
This is typically only an issue when you have either a costperminute
defined or have normal/primary times defined. 

-- 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

For more information about this list, including removal,please see http://www.iea-software.com/maillist.html