Here’s a new Knowledge Base article we published today. This one talks about troubleshooting an issue where you get an Arithmetic overflow error converting IDENTITY to data type int error in the Intercept Log on a server hosting an AVIcode SEViewer instance:
You receive a message in the Intercept Log on a server hosting an AVIcode SEViewer instance that is similar to the following:
Message: Arithmetic overflow occurred. Arithmetic overflow error converting IDENTITY to data type int. Source: Microsoft OLE DB Provider for SQL Server Target Site: System.Data.OleDb.OleDbDataReader ExecuteReaderInternal(System.Data.CommandBehavior, System.String) Stack Trace: at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method) at System.Data.OleDb.OleDbCommand.ExecuteNonQuery() at Avicode.AX5.Data.OleDb.OleDb.ExecuteNonQuery(OleDbCommand oleDbCommand) Message: Arithmetic overflow occurred. Arithmetic overflow error converting IDENTITY to data type int. Command text: INSERT INTO PCOUNTER ( VALUE_BASE, VALUE_DATE, VALUE_STRING, ID, PID, UTCDATE, SOURCEID, PCTYPEID, PCPROCESSID, PCMACHINEID, ISSTATE ) SELECT 37790.5251,NULL,NULL,46,NULL,'20120127 21:15:38',NULL,3,NULL, 186, 1 UNION ALL SELECT 6425471.753443,NULL,NULL,39,NULL,'20120127 21:15:38',NULL,34,NULL, 186, 10
This issue can occur when the PCOUNTERID column reaches the value 2,147,483,647. This is due to the limitation of the data type INT being 4 bytes and unable to hold any larger values.
The PCOUNTERID value is incremented each time a new data item is written to the PCOUNTER table and is never reset, so even with regular grooming this issue can occur.
To resolve this issue, the PCOUNTERID column must be reseeded. To check the current identity value, run the following SQL command in SQL Management Studio:
DBCC CHECKIDENT (“dbo.PCOUNTER”, noreseed)
If the current identity value is 2147483647, reseed the identity column using the following SQL Command:
DBCC CHECKIDENT (“dbo.PCOUNTER”, reseed)
For the most current version of this article please see the following:
2686673 : Arithmetic Overflow Occurred error is generated in the AVIcode Intercept Log
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
I know that there are other topics like this open but I want to ask once again.
We have servers that are in gray in Windows computer view. Unfortunately we were unable to uninstall the agents and just deleted them from the console. And the result is gray servers. I've tried using the SQL query that set agents to IsDeleted but the result was not very good. After the restart of the health service it was not working. I guess some dependencies with the deleted object caused the health service to not work properly. Is there some other way I can remove them in safer way?
I couldn't post this comment on the previous article - blogs.technet.com/.../how-to-delete-an-operations-manager-2007-managed-object-from-a-management-group-using-powershell.aspx
Can you please help?
The supported method to manually remove stale objects is to find the discovery that added it, create an override to disable the discovery for that object and then run the Remove-DisabledMonitoringObject cmdlet using the Operations Manager Command Shell. There is some more info on this here: blogs.technet.com/.../remove-disabledmonitoringobject.aspx
Thanks for the reply J. I currently trying this method. For now without success but I will try some more. If you can it will be good if there is a fix for this issue in some CU.