none
scsm cmdb grooming fails and all changes to incidents and exchange connectors running fails with system overflow exception "failing to convert an value from int64 to int32."

    Question

  • Hi all,

    Having a new issue where scsm console and the exchange connectors keep throwing errors "failing to convert an Int64 to Int32 value"

    errors are thrown as follows. Any help pls?


    A Windows Workflow Foundation workflow failed during execution.

    Workflow Type: Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow 

    Workflow Identifier: 7a99b48e-95f0-3160-c911-fad300de9111 

    Exception Type: System.OverflowException 

    Exception Message: Failed to convert parameter value from a Int64 to a Int32. 

    Exception Stack:    at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
       at Microsoft.EnterpriseManagement.Common.Internal.ConnectorFrameworkConfigurationServiceProxy.ProcessDiscoveryData(Guid discoverySourceId, IList`1 entityInstances, IDictionary`2 streams, ObjectChangelist`1 extensions)
       at Microsoft.EnterpriseManagement.ConnectorFramework.IncrementalDiscoveryData.CommitInternal(EnterpriseManagementGroup managementGroup, Guid discoverySourceId, Boolean useOptimisticConcurrency)
       at Microsoft.EnterpriseManagement.ConnectorFramework.IncrementalDiscoveryData.Commit(EnterpriseManagementGroup managementGroup, Guid discoverySourceId, Boolean useOptimisticConcurrency)
       at Microsoft.EnterpriseManagement.Common.EnterpriseManagementObject.CommitInternal(Guid discoverySourceId, Boolean useOptimisticConcurrency)
       at Microsoft.EnterpriseManagement.Common.EnterpriseManagementObject.CommitInternal(Boolean useOptimisticConcurrency)
       at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.UpdateConnectorFinishTime(ManagementPackEnumeration connectorStatus)
       at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.ProcessMail()
       at Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow.Execute(ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.FaultAndCancellationHandlingFilter.Execute(Activity activity, ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
       at System.Workflow.Runtime.Scheduler.Run()

    An exception was thrown while processing ProcessDiscoveryData for session ID uuid:b944290a-f587-46b4-8ff1-b2be2cc48a9c;id=6.
     Exception message: Failed to convert parameter value from a Int64 to a Int32.
     Full Exception: System.OverflowException: Failed to convert parameter value from a Int64 to a Int32. ---> System.OverflowException: Value was either too large or too small for an Int32.
       at System.Convert.ToInt32(Int64 value)
       at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
       at System.Data.SqlClient.SqlParameter.CoerceValue(Object value, MetaType destinationType)
       --- End of inner exception stack trace ---
       at System.Data.SqlClient.SqlParameter.CoerceValue(Object value, MetaType destinationType)
       at System.Data.SqlClient.SqlParameter.GetCoercedValue()
       at System.Data.SqlClient.SqlParameter.Validate(Int32 index, Boolean isCommandProc)
       at System.Data.SqlClient.SqlCommand.BuildParamList(TdsParser parser, SqlParameterCollection parameters)
       at System.Data.SqlClient.SqlCommand.BuildExecuteSql(CommandBehavior behavior, String commandText, SqlParameterCollection parameters, _SqlRPC& rpc)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.EnterpriseManagement.DataAccessLayer.SqlRetryHandler.ExecuteNonQuery(ExecuteArguments executeArguments, Int32& result)
       at Microsoft.EnterpriseManagement.DataAccessLayer.SqlRetryHandler.Execute[T](ExecuteArguments executeArguments, RetryPolicy retryPolicy, GenericExecute`1 genericExecute)
       at Microsoft.EnterpriseManagement.DataAccessLayer.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, RetryPolicy retryPolicy)
       at Microsoft.EnterpriseManagement.DataAccessLayer.InsertRequest.ExecuteInsert()
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryDatabaseApi.SetEntityPropertyValues(Guid baseManagedEntityId, PropertyNameValuePair[] propertyValues, Guid managedTypeId, String name, Boolean entityWasInserted, Nullable`1 changeId, TypeSpaceData typeSpaceData, DateTime& entityLastModified)
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryDatabaseApi.UpsertEntityProperties(Guid baseManagedEntityId, String name, PropertyNameValuePair[] propertyValues, Guid managedTypeId, Boolean entityWasInserted, Nullable`1 changeId, TypeSpaceData typeSpaceData, DateTime& currentLastModified)
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.SingleUpsertInstance(DiscoveryDatabaseApi dbApi, DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData)
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.SingleAddUpdate(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.Write(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithNoRetryUnauthorized(DiscoveryDatabaseApi dbApi, Boolean useProcessContext)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.ProcessIncrementalDiscoveryData(DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.Process()
       at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithRetry(HandleProcessing handleProcessing, RetryPolicy retryPolicy)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.ProcessDiscoveryDataWithRetry(DatabaseConnection dbconnection, Guid discoverySourceId, IList`1 sdkEntityInstances, IDictionary`2 streams, IContext context)
       at Microsoft.EnterpriseManagement.ServiceDataLayer.ConnectorFrameworkConfigurationService.ProcessDiscoveryData(Guid discoverySourceId, IList`1 entityInstances, IDictionary`2 streams, ObjectChangelist`1 extensions)


    Subaru



    • Edited by subarusyd Monday, May 28, 2018 1:44 PM
    Monday, May 28, 2018 1:42 PM

All replies

  • Hi,

    What's your SCSM/OS version?

    Based on my experience , the issue happened on SCSM 2012 SP1 and SCSM 2012 RTM. The issue is fixed in SCSM 2012 R2. I recommend you upgrade your SCSM to the latest version.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, May 29, 2018 9:58 AM
    Moderator
  • Hi All,

    Thanks Xin and Andreas.

    The SCSM version we were running was SCSM 2012 SP1. Installed UR6 on it. Didnt Fix it. 

    Raised a case with MS and they said that this is a known bug.  The ONLY way this was fixed was when we upgraded to SCSM 2012 R2. 

    So anybody getting affected by the same bug. I would immediately recommend to do a planned urgent upgrade to SCSM 2012 R2 as that upgrade definitely fixed the issue.



    Subaru

    Wednesday, June 13, 2018 12:01 AM