Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 2013 - Goals not calculated RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all,

    we have migrated CRM 2011 on Premise to CRM 2013 RU1 On Premise. Everything was ok, but we have problem with the goals automatic recalculation. They have been calculated 2 times after the migration and since then, they do no get calculated. Can you help me? Where should we look and what should be checked?

    Michal

    Monday, January 13, 2014 2:03 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    We have raised ticket with Microsoft who did some queries to database and deleted duplicate records in rollup query. However, tha cause was not identified.
    • Marked as answer by MABR Tuesday, June 10, 2014 5:10 PM
    Tuesday, June 10, 2014 5:10 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    In the system jobs we have a goal recalculation job in status waiting with this:

    Unhandled Exception: System.ArgumentException: An item with the same key has already been added.
       at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
       at Microsoft.Crm.Asynchronous.GoalRollupOperation.CreateRollupTreeInfo(Entity entity)
       at Microsoft.Crm.ObjectModel.GoalManagement.RollupEngine.RollupGoals()
       at Microsoft.Crm.Asynchronous.GoalRollupOperation.InternalExecute(AsyncEvent asyncEvent)
       at Microsoft.Crm.Asynchronous.AsyncEventHandlerCommand`1.Execute(IAsyncEvent asyncEvent)
       at Microsoft.Crm.Asynchronous.AsyncEventExecutionManager`2.ExecuteHandler(IAsyncEventHandlerFactory handlerFactory)
       at Microsoft.Crm.Asynchronous.PoolHandler.ProcessAsyncEvent(IAsyncEventExecutionManager asyncEventExecutionManager)

    Monday, January 13, 2014 2:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    We have raised ticket with Microsoft who did some queries to database and deleted duplicate records in rollup query. However, tha cause was not identified.
    • Marked as answer by MABR Tuesday, June 10, 2014 5:10 PM
    Tuesday, June 10, 2014 5:10 PM