ArticlesArticles Most Popular ArticlesMost Popular Articles
RSS Feeds
DrillDown Icon Table of Contents Back
 . . . . . . . . . . . . .
DrillDown Icon 2018 Official Holidays & Support Schedule
DrillDown Icon IMPORTANT: End of Life of SHA1 on Windows Server 2003
DrillDown Icon IMPORTANT: Supported Operating Systems
DrillDown Icon PLEASE READ: Our Update Server IPs Have Changed
DrillDown Icon Support
DrillDown Icon modusGate for Microsoft Azure
DrillDown Icon modusCloud
DrillDown Icon Alleviating Spam – Best Practices
DrillDown Icon directQuarantine Technical Information
DrillDown Icon modusMail & modusGate Technical Information
DrillDown Icon Other Product Technical Information
DrillDown Icon VOP Radius
DrillDown Icon Release Information and Patches
DrillDown Icon Troubleshooting
DrillDown Icon Error codes and messages
DrillDown Icon Invalid Packet Processing
DrillDown Icon SQL Server does not exist or access denied
DrillDown Icon “Access check: This user is defined to use a profile and none has been found! [User name: XXX] [0].
DrillDown Icon Arithmetic overflow error converting expression to data type int
DrillDown Icon The service type is missing!
DrillDown Icon Cannot create a remote manager connection point. RPC error 1762.
DrillDown Icon No Password
DrillDown Icon Error: ***1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated..
DrillDown Icon class CAccessCheck : We got zero (0) as numeric value, this MAY be a problem!
DrillDown Icon Problems and Solutions
DrillDown Icon Configuration Assistance
DrillDown Icon Tools approved by Vircom
DrillDown Icon Third Party Products
DrillDown Icon VOPCOM
DrillDown Icon Professional Services
DrillDown Icon Newsletters
  Email This ArticlePrint PreviewPrint Current Article/Category and All Sub-Articles/Categories
 
Radius: Arithmetic overflow error converting expression to data type int
Problem Summary:

Problem: The Event Viewer and VOP Radius error log "VPRError.log" shows the following error:

VPR Radius Server Error: ODBC Error: State:22003, Msg:[Microsoft][ODBC SQL Server Driver][SQL Server]Arithmetic overflow error converting expression to data type int.

 

Cause:

First, it is important to understand that the source of the error is from the SQL Server / ODBC Driver and VOP Radius is only reporting it in the logs. Second, this error is most likely to happen only with accounting data since with authentication only a SELECT statement is performed. Third, the error means that there is a mismatch somewhere in one the fields between what VOP Radius is sending, via an INSERT statement, and what the SQL Server Table Field is set to support. For example, VOP Radius, via an INSERT statement, may be sending an INT value, but the SQL Server Table field accepting that field may be set to only accept TINY INT values. Fourth, in this problem it is important to understand that the data VOP Radius receives, and subsequently sends to the SQL Server Table, is actually originally sent by the Network Access Server (NAS). That is, the Network Access Server sends to VOP Radius the accounting data, VOP Radius in turn takes this accounting data "as is" and sends to the SQL Server Database Table configured under the Accounting --> ODBC Setup section.

 

 

Resolution:

 The difficulty with this error is that it not does narrow down the exact field (or fields) where the mismatch exists. For this reason, the administrator may need perform some guess work to find the problem. Here are some recommended troubleshooting steps:

1) Enable full log tracking in VOP Radius
2) Find the error in the VOP Radius error log "VPRError.log"
3) Examine the query for values that stand out as "large"
4) Using the SQL Query determine the field name where these "large" values are destined to be inserted
5) In the SQL Server Table look at the data type set for the field
6) Increase as necessary the data type size for the field

Note: The above troubleshooting steps take the viewpoint that what the Network Access Server is sending is correct. It may also be the case that a problem with the Network Access Server is causing it to send incorrect and inflated values. In this case the administrator may take troubleshooting steps focused on on the values that the Network Access Server is sending rather than try to compensate for the problem by changing the Data Type in the SQL Server Table field.

Related Information:

 

Modified 12/2/2004
Keywords:
Article ID: 1009