Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

“[Microsoft][ODBC SQL Server Driver]Numeric value out of range” logged in catError.log during backups/duplicates.

Created: 04 Mar 2011 • Updated: 30 Jun 2011 | 4 comments
dedupe-works's picture
3
Votes
Login to vote
Me Too!I have the same issue
Product(s): Backup Exec - 2010, Backup Exec
Severity: Non-data threatening / major functionality
Status: Public fix available
Tech Note: More Information

[Microsoft][ODBC SQL Server Driver]Numeric value out of range is logged in the CatError.log file in the backup Exec logs directory. This can occur during backups or duplicate

An associated application event log error will also be present on the backup server that may look like the example below.

Application Event Log error:
Type :              Error
Event :             34326
Source :                       Backup Exec CatErrorHandler Server
Category :       None
User :               N/A
Computer :      SERVERNAME
Description:
Access to catalog index (Catalog index database) failed.
Reason: [Microsoft][ODBC SQL Server Driver]Numeric value out of range cat_RecordSet::Open()
e:\leros\4164r\becat\segodbc\seg_odbc.cpp(2435)
 Update CatImage SET CatImage.Status = ? , CatImage.ExtStatus = ? , CatImage.OffsetInFile = ? WHERE CatImage.ImageID = ?

Information is still be gathered for this issue.

Customers experiencing this issue are encouraged to contact Symantec Technical Support.

Comments 4 CommentsJump to latest comment

Jan Lankowski's picture

Since a couple of days we are experiencing this error. After searching for possible solutions we also verified that Hotfix 161270 is installed. So any help or advice would be great.

0
Login to vote
Simon B.'s picture

Just wanted to confirm that this error does occur with HF161270 installed.

PMCS GmbH & Co. KG - Consulting und Support für BE/NBU/EV und andere Symantec Produkte.
Please take the time and mark this post as solution if it solved your problem - thanks!

0
Login to vote
3consult's picture

We are using Backup Exec 2010 R3 and already had applied the corresponding Hotfix 161270. Still, since a couple of days we have been experiencing the issue described in the initial post by dedup-works. Any suggestions on how to resolve it would be deeply appreciated!

0
Login to vote
dedupe-works's picture

This issue is resovled in Backup Exec 2010 R2 Hotfix (TECH159293).

Regards.

Randey

0
Login to vote