Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
> 
CRM 2011 - Unable to Create Duplicate Detection Jobs

問題 CRM 2011 - Unable to Create Duplicate Detection Jobs

  • Monday, July 16, 2012 12:53 PM
     
     
    Sign In to Vote
    0

    For some reason I can no longer run duplicate detection jobs in some of my environments. Apparently, some bugs exist within CRM 2011 where the DB holds on to values from previous environments (the DB was restored from another environment). When I select Duplicate Detection : New, I receive the following JS error: "searchCriteriaFrame.searchCriteriaForm.fetchXml is null or not an object" and the URL referenced in the error is "http://server:5555/Org/Tools/DuplicateDetection/DuplicateDetectionJobWizard/SearchCriteriaContainerPage.aspx"

    However in the event log, the error references another page "http://server/Tools/BulkDelete/BulkDeleteWizard/SearchCriteriaPage.aspx"

    And BTW, no other Orgs exist within this instance of Dynamics so tyring to enable another Org is not an option.

    Thanks in advance,

    Dave

     

All Replies

  • Monday, July 23, 2012 5:45 PM
     
     
    Sign In to Vote
    0

    Install latest roll up update and then try.

    also can you please put up the trace log if possible.

    If you see answers and helpful posts, please click Vote as Helpful, Propose as Answer, and/or Mark as answer._____________________________________________________Ahmed - CRM APPLICATION MANAGEMENT ______________________ These replies/answers are my own and doesn’t relate to any company or organization.

     
  • Tuesday, July 24, 2012 7:43 AM
    Answerer
     
     
    Sign In to Vote
    0

    Hi,

    Install or update th latest rollup and check still you facing same problem.

    Thanks & Regards, MS CRM Consultant, V.Surya.

     
  • Tuesday, July 24, 2012 12:40 PM
     
     
    Sign In to Vote
    0

    Thanks for the suggestion but reapplying the rollup did not fix the issue and I find nothing in the trace logs related to this.

    As an update, this behavior does not exist in every instance of Dynamics to which the org DB was restored. So, that leads me to believe the issue exists with the MSCRM_CONFIG DB, not the org DB.

     
  • Tuesday, July 24, 2012 1:05 PM
     
     
    Sign In to Vote
    0

    hi,

    thanks for the update on this, if trace log showed some thing we would have been able to solve that.

    we need to think for any other work around for this..

    If you see answers and helpful posts, please click Vote as Helpful, Propose as Answer, and/or Mark as answer._____________________________________________________Ahmed - CRM APPLICATION MANAGEMENT ______________________ These replies/answers are my own and doesn’t relate to any company or organization.