Re: ODBC to Access seems to stop

Majordomo@essex1.com ( (no email) )
Mon, 22 Dec 1997 13:58:41 -0600

Hi;
Sorry, here is a copy of one the outputs -x15 gave me. Radius is now
acting up in the x-15 mode now. I switched back to running as a service.
The whole process seems to slow down after awhile. Using 'radlogin' I
initally can verifiy in a speed of around 150 but evenually it slows down
to over 4000 before it simply stops verifing at all. It lasted all morning
before it began this slow down, it was the same problem I had on our 3.51
machine.

Resp Time: 110 Auth: 5/0 -> 5 Acct: 5/9/0 -> 14
radrecv: Request from host ce1f01c4 code=4, id=183, length=94

Acct-Session-Id = "6B002611"
User-Name = "hopestar"
NAS-Identifier = 206.31.1.196
NAS-Port = 18
NAS-Port-Type = Async
Acct-Status-Type = Start
Acct-Authentic = RADIUS
User-Service = Framed-User
Framed-Protocol = PPP
Framed-Address = 206.31.1.223
Acct-Delay-Time = 0

SQL Statement: INSERT INTO Calls
(CallDate,AcctSessionId,UserName,NASIdentifier,NASPort,NASPortType,AcctStatu
sType,AcctAuthentic,UserService,FramedProtocol,FramedAddress,AcctDelayTime)
VALUES
(Now(),'6B002611','hopestar','206.31.1.196',18,0,1,1,2,1,'206.31.1.223',0)

Sending Accounting Ack of id 183 to ce1f01c4 (dialup-dixon.essex1.com)

Thanks :)
Russ
webmaster@essex1.com

At 11:28 AM 12/22/97 -0800, you wrote:
>Majordomo@essex1.com wrote:
>>
>> Hi again;
>> Funny thing, it still is running in x-15 mode without interruption.
>> However there is an error that keeps going by.
>>
>> This seem to be created when Radius writes to the Calls table.
Should
>> AcctSessionId be a Primary Key? Our calls table has two AcctSessionId for
>> each client connection (one login, one logout).
>>
>> ODBC: SQLExecDirect Error -1605
>> [Microsoft][ODBC Microsoft Access 97 Driver] The changes you requested
to the
>> table were not successful because they would create duplicate values in the
>> index, primary key,
>
>The Primary key is four fields, not just one. See the sample MS Access
>database included for the details. Also, include the actually INSERT
>statement intself, rather than just the error and it will help us.
>
>
>--
>Dale E. Reed Jr. (daler@iea.com)