Table of Contents
- System Requirements
- Assign Service Logon As Credentials
- Server Configuration
- Agent-Based Monitoring
- Azure Relay Hybrid Connection
- Account Lockout Monitoring and Reporting
- Data Providers
- Directory Services
- Template Properties
- Batch Update Templates
- Log Management Templates
- File and Directory Monitor Templates
- Windows Monitor Templates
- Account Lockout Monitor Template
- Logon Monitor Template
- CPU Monitor Template
- Memory Monitor Template
- Disk Space Monitor Template
- SMART Monitor Template
- Process Monitor Template
- Service Monitor Template
- Performance Counter Monitor Template
- Active Directory User Monitor Template
- Active Directory User Integrity Monitor Template
- Task Scheduler Template
- Clock Synchronization Template
- Defragment NTFS Disks Template
- Network and Application Monitor Templates
- SSL Certificate Monitor Templates
- Email Monitor Templates
- SNMP Monitor Templates
- Monitor Hierarchy
- Report Properties
- Security Reports
- Generic Log Reports
- File and Permission Reports
- Summary Reports
- Shared Views
- General Executable Properties
- Assign Actions
- Assign Directories
- Assign Disks
- Assign Shares
- Assign Files
- Assign Consolidated Logs
- Assign Event Logs
- Assign Active Directory Audit Logs
- Target Files and Sub-Directories
- Define Log Entry Columns
- Define Log Entry Columns with Regular Expressions
- Define CSV and W3C Log Entry Columns
- Active Directory User and Group Filters
- Explicitly Assigned Logs
- Report Columns
- Report Date/Time Ranges
- Report Security Event Log Filters
- SSH Shell
- Exporting and Importing Configuration Objects
- Command Line Interface
Arithmetic Overflow Errors
The Arithmetic overflow error converting IDENTITY to data type int. Arithmetic overflow occurred. error is thrown by SQL Server when the Identity column has reached the maximum size of an integer or 2,147,483,647.
Verify the error:
- Execute the log consolidation template on the host that is throwing the error.
How to resolve:
This error is resolved by reseeding the table which fills in the gaps that were created when removing or archiving old entries during the Log Entry Retention Policy execution.
- From the Explorer View, expand the root Hosts node then navigate through the tree to the target host.
- Expand the target host then right click on the Log Consolidation template throwing the error and select Explore. The Monitor Status View displays.
- From the Monitor Status View, select the Data Properties tab.
- From the Data Properties tab
- Use the Log drop-down to select the errant log, typically, the Windows Security Event Log.
Click the Reseed button.
The Reseeding View displays then automatically starts to reseed the table.
The reseed function copies all the rows from the errant table to a new temporary table, then the errant table is deleted. Next, the entries in the temporary table are written back to a new table which automatically reseeds the table. Finally, the temporary table is deleted.