Re: [Emerald] Violation of PRIMARY KEY constraint 'pk_RadLogs'. Cannot insert duplicate key in obje

Mourad Dahoumane ( (no email) )
Wed, 22 Sep 1999 17:18:45 +0200

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Previous message: Dale E. Reed Jr.: "Re: [Emerald] Violation of PRIMARY KEY constraint 'pk_RadLogs'. Cannot"
Next message: Mourad Dahoumane: "Re: [Emerald] Violation of PRIMARY KEY constraint 'pk_RadLogs'. Cannot insert duplicate key in obje"

I suspected that, but I couldn' see any logged connection. Usually when this
happen I go the Admin and uncheck the port where the ghost connection
appeared.
>
> Could it be that the calls online was not reset after the transfer to
> the
> new database? Is you calls online working at all on the next database?
>
> > Any thoughts what can be causing this?
> >
> Most likely the clinet tried to auth twice in a row with the wrong
> password. The second one doesn't get logged (its a duplicate).
>

No I don't think because it happens to all the customers not only this one,
when I set
the concurrency control no one can connect. I know I messed it up but I
don't know where -:((

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart

Previous message: Dale E. Reed Jr.: "Re: [Emerald] Violation of PRIMARY KEY constraint 'pk_RadLogs'. Cannot"
Next message: Mourad Dahoumane: "Re: [Emerald] Violation of PRIMARY KEY constraint 'pk_RadLogs'. Cannot insert duplicate key in obje"