none
SCSM Console error

    Question

  • This is what I get when two users or workflows are updating the a ticket.

    There is a suggestion to fix this out there for Microsoft but wanted to know if anyone else has seen this issue:

    SHOW details-

    Date: 12/7/2012 9:19:46 AM

    Application:

    Application Version: 7.5.1561.0

    Severity: Error

    Message:

    Microsoft.EnterpriseManagement.UI.Core.Shared.InstanceDataCollisionException: This item cannot be updated because it has been changed by another user or process. To update the item, please close the item and open it again. ---> Microsoft.EnterpriseManagement.Common.DiscoveryDataModificationCollisionException: The item has been changed by another user or process. Cancel your action, reopen the item and try again.

       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.ConnectorFramework.IncrementalDiscoveryData.CommitForUserDiscoverySource(EnterpriseManagementGroup managementGroup, Boolean useOptimisticConcurrency)

       at Microsoft.EnterpriseManagement.ConnectorFramework.IncrementalDiscoveryData.Commit(EnterpriseManagementGroup managementGroup)

       at Microsoft.EnterpriseManagement.UI.SdkDataAccess.DataAdapters.EnterpriseManagementObjectProjectionWriteAdapter.WriteSdkObject(EnterpriseManagementGroup managementGroup, IList`1 sdkObjects, IDictionary`2 parameters)

       --- End of inner exception stack trace ---

       at Microsoft.EnterpriseManagement.UI.SdkDataAccess.DataAdapters.EnterpriseManagementObjectProjectionWriteAdapter.WriteSdkObject(EnterpriseManagementGroup managementGroup, IList`1 sdkObjects, IDictionary`2 parameters)

       at Microsoft.EnterpriseManagement.UI.SdkDataAccess.DataAdapters.SdkWriteAdapter`1.DoAction(DataQueryBase query, IList`1 dataSources, IDictionary`2 parameters, IList`1 inputs, String outputCollectionName)

       at Microsoft.EnterpriseManagement.UI.ViewFramework.SingleItemSupportAdapter.DoAction(DataQueryBase query, IList`1 dataSources, IDictionary`2 parameters, IList`1 inputs, String outputCollectionName)

       at Microsoft.EnterpriseManagement.UI.DataModel.QueryQueue.StartExecuteQuery(Object sender, ConsoleJobEventArgs e)

       at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)

    Microsoft.EnterpriseManagement.Common.DiscoveryDataModificationCollisionException: The item has been changed by another user or process. Cancel your action, reopen the item and try again.

       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.ConnectorFramework.IncrementalDiscoveryData.CommitForUserDiscoverySource(EnterpriseManagementGroup managementGroup, Boolean useOptimisticConcurrency)

       at Microsoft.EnterpriseManagement.ConnectorFramework.IncrementalDiscoveryData.Commit(EnterpriseManagementGroup managementGroup)

       at Microsoft.EnterpriseManagement.UI.SdkDataAccess.DataAdapters.EnterpriseManagementObjectProjectionWriteAdapter.WriteSdkObject(EnterpriseManagementGroup managementGroup, IList`1 sdkObjects, IDictionary`2 parameters)


    Help

    Friday, December 07, 2012 3:25 PM

Answers

  • Hi,

    Microsoft is aware of the issue - I do not know any details if they work on a fix.


    Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

    Saturday, December 08, 2012 2:07 PM

All replies

  • Hi,

    there is currently just a work around: If you work on a ticket assign it to you, save this and work on the incident. Others should not work on the same item as it is assigned to you.


    Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

    Friday, December 07, 2012 4:47 PM
  • Thanks Peter in a perfect world telling them that would solve the issue. Unfortunantely some open it....trying updating stuff....then leave it open as another person starts updatinga the same time.

    I guess they will have to deal until someone comes up with a solution. Thanks.


    Help

    Friday, December 07, 2012 4:49 PM
  • Hi,

    Microsoft is aware of the issue - I do not know any details if they work on a fix.


    Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

    Saturday, December 08, 2012 2:07 PM
  • Is there a way to determine which user or process has the object open?  Based on what I've read in a  few posts, it doesn't look like Microsoft developers thought about collaboration when you can have multiple people working on the same incident.  Once I see that "John" has it open I can ask him to close the ticket so I can add my comments, or pass my comments to him so he can add them.


    C5rookie

    Tuesday, April 16, 2013 1:11 PM
  • C5Rookie - Peter might know but I am not sure.

    Help

    Tuesday, April 16, 2013 1:13 PM
  • Hi,

    well - Microsoft finally released a KB article which describes this issue: http://support.microsoft.com/kb/2830814

    But please - do not read the content, you'll get suck...


    Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

    Tuesday, April 23, 2013 8:41 AM
  • Has there been any progress on this?  Hotfix or similar?
    Friday, September 13, 2013 3:25 AM