Ok well if the stored procedure is what is expecting a numeric rather than char is there a way to tell Radiator to try to convert that field to a number before it passes it? I would assume that I can't simply change the database itself, and a lot of the Rodopi stored procedures are locked as well.
Any suggestions as to what exactly to do would be much appreciated. Tim Jung System Admin Internet Gateway [EMAIL PROTECTED] ----- Original Message ----- From: "Mike McCauley" <[EMAIL PROTECTED]> To: "Hugh Irvine" <[EMAIL PROTECTED]>; "Tim Jung" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, June 25, 2003 7:37 PM Subject: Re: (RADIATOR) Radiator 3.5 & Rodopi 5.2sp3 > Hello Tim, > > On Thu, 26 Jun 2003 09:57 am, Hugh Irvine wrote: > > Hello Tim - > > > > The message appears to be complaining about a data conversion from a > > string to a numeric. > > > > It is not obvious to me from the log which field is causing the > > problem, so you should check your database log to see exactly what is > > happening. You may need to adjust the column definition in the database > > to accomodate the data. > > Hugh is correct: your NAS is sending a string in a field that the Rodopi > stored procedure expects to be an integer. Its hard to be sure which one has > the problem, but I suspect that it might be the Connect-Info field, which in > this example is '45333/26400 V.90/V.42/V.42bis QC'. In my test Rodopi > database, the stored procedure expects a numeric() there, even though it does > nothing with it. > > Cheers. > > > > > > > regards > > > > Hugh > > > > On Thursday, Jun 26, 2003, at 08:33 Australia/Melbourne, Tim Jung wrote: > > > I was wondering if someone could tell me why I am getting these errors > > > from > > > time to time in the Radiator log on my Linux box? It looks like it is > > > getting data from the Remote Access server and isn't able to dump it > > > into > > > the MS-SQL database that Rodopi uses. > > > > > > Wed Jun 25 17:20:43 2003: ERR: do failed for 'exec > > > Interface_VircomDetails > > > '00138AEE', 'Jun 25, 2003 17:16', 'paulhostkoetter', '67.95.10.115', > > > 13777, > > > 'Framed-User', 'PPP', '64.48.129.119', '6367240300', > > > 'stl-01.cvx.algx.net:6000', > > > 'Stop', 0, 141096, 1550059, 1500, 3410, 4373, 'User-Request', 'Async', > > > '45333/26400 V.90/V.42/V.42bis QC', > > > '6367541208'': Server message number=8114 severity=16 state=1 line=0 > > > server=BILLINGprocedure=Interface_VircomDetailstext=Error converting > > > data > > > type varchar to numeric. > > > > > > I don't get this every single time, but I do seem to get it often > > > enough > > > that it is annoying and messes with keeping track of multiple logins > > > and > > > such. > > > > > > Let me know how to fix this or what I can do about it. Thanks. > > > > > > Tim Jung > > > System Admin > > > Internet Gateway > > > [EMAIL PROTECTED] > > > > > > > > > === > > > Archive at http://www.open.com.au/archives/radiator/ > > > Announcements on [EMAIL PROTECTED] > > > To unsubscribe, email '[EMAIL PROTECTED]' with > > > 'unsubscribe radiator' in the body of the message. > > > > NB: have you included a copy of your configuration file (no secrets), > > together with a trace 4 debug showing what is happening? > > -- > Mike McCauley [EMAIL PROTECTED] > Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW > 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au > Phone +61 3 9598-0985 Fax +61 3 9598-0955 > > Radiator: the most portable, flexible and configurable RADIUS server > anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, > Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, > TTLS, PEAP etc on Unix, Windows, MacOS etc. > > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
