none
Issues with Quick Find and CRM 2011 Rollup 12

    Question

  • Hi Everyone.

    My client currently has CRM 2011 with Rollup 8 installed on their production environment. We have recently installed Rollup 12 to the DEV box and I've begun to notice problems.

    The main issue is this: For one specific entity, the quick find produces a generic error. When looking into the event viewer, I retrieve this.

    Exception information:
        Exception type: CrmException
        Exception message: Table alias a_db76294a6e09e111a8e7000e0c3bf634 is not unique amongst all top-level table and join aliases
       at Microsoft.Crm.Application.Platform.ServiceCommands.PlatformCommand.XrmExecuteInternal()
       at Microsoft.Crm.Application.Platform.ServiceCommands.RetrieveMultipleCommand.Execute()
       at Microsoft.Crm.ApplicationQuery.RetrieveMultipleCommand.RetrieveData()
       at Microsoft.Crm.ApplicationQuery.ExecuteQuery()
       at Microsoft.Crm.Application.Platform.Grid.GridDataProviderQueryBuilder.GetData(QueryBuilder queryBuilder)
       at Microsoft.Crm.Application.Platform.Grid.GridDataProviderQueryBuilder.LoadQueryData()
       at Microsoft.Crm.Application.Platform.Grid.GridDataProviderQueryBuilder.LoadData()
       at Microsoft.Crm.Application.Platform.Grid.GridDataProviderBase.PrepareGridData()
       at Microsoft.Crm.Application.Platform.Grid.GridDataProviderBase.PrepareData()
       at Microsoft.Crm.Application.Controls.GridUIProvider.Render(HtmlTextWriter output)
       at Microsoft.Crm.Application.Components.UI.Grid.DataGrid.RenderData(HtmlTextWriter output)
       at Microsoft.Crm.Application.Components.UI.Grid.DataGrid.RenderInnerHtml(HtmlTextWriter output)
       at Microsoft.Crm.Application.WebServices.AppGridWebServiceHandler.GetResetResponseHtml(AppGrid appGrid, StringBuilder sbHtml)
       at Microsoft.Crm.Application.WebServices.AppGridWebServiceHandler.Reset(String gridXml, String id, StringBuilder sbXml, StringBuilder sbHtml)
       at Microsoft.Crm.Application.WebServices.AppGridWebServiceHandler.ProcessRequestInternal(HttpContext context)

    From what I have seen, there seems to be additional dependencies being created from rollup 12 that may cause this error.

    Has anyone experienced this? and if so, has anyone found a solution?

    Any advice would be greatly appreciated.
    Thanks in advance.

    Monday, April 22, 2013 8:27 AM

Answers

  • In UR 12 new indexes are used to optimize the quick find on some entities. The entities are:

    Sales Literature, Product, Lead, KB article, Connection Role, Connection, Business Unit, Contact, Competitor, Cases

    Maybe these new indexes caused the problem. Check your DB for these indexes if you are searching on one of these entities.



    My Weblog -- My Website

    Monday, April 22, 2013 10:37 AM
    Moderator
  • Hi Mayank,

    I never heard anything back on this. I eventually took a backup of the production DB and restored it to my Dev box. It fixed the problems. I know that the RU12 has got some hidden agenda when it installs. There are additional indexes it makes to the out of the box entities which is where I think my problem was.

    http://support.microsoft.com/kb/2791312

    Entities included.

    • Cases
    • Opportunities
    • Competitors
    • Contact (the Phone Number fields)
    • Business Unit
    • Connection
    • Connection Role
    • KB Article
    • Lead
    • Product
    • Sales Literature

    So at the end of the day, there was just data that had corrupted, causing the quickfind to fail.

    Thanks,

    Jarrod

    Tuesday, May 21, 2013 6:04 AM
  • Hi,

    The last response in this thread helped me in partially resolving the issue.

    http://social.msdn.microsoft.com/Forums/en-US/crm/thread/e17c9a53-6fe2-435f-a1ec-058899ffb1ef

    We found the view corruption to be entity specific. As per that link, the issue occurs only in entities where the native advanced find view had references to columns from related entities. We removed those references and recreated the custom views. If native views like quick find or associated view were broken, we updated the fetchxml in the database (risky business).

    We did the fix for 2 entities and I'm afraid this could show up on another entity that we customize in the future. We have opened a case with MS so that we are tagged and notified when a fix to this problem is released.

    Thanks,

    Mayank

    Tuesday, May 21, 2013 8:41 PM

All replies

  • In UR 12 new indexes are used to optimize the quick find on some entities. The entities are:

    Sales Literature, Product, Lead, KB article, Connection Role, Connection, Business Unit, Contact, Competitor, Cases

    Maybe these new indexes caused the problem. Check your DB for these indexes if you are searching on one of these entities.



    My Weblog -- My Website

    Monday, April 22, 2013 10:37 AM
    Moderator
  • Hi Payman,

    Thanks for the response. I am not using any of these entities. We created a new one "restaurants" and it seems to only have an effect on this entity. I have also checked the views and the filter criteria to see if something had gotten lost in the upgrade. Everything is as it should be and when using an advanced find with the same views as present on the restaurant's entity, I get the correct results returned.

    Could this be originating from the connections that have been created prior to the update? I thought that it may be something to do with them as the error seems to originate from one of the joins.

    Monday, April 22, 2013 10:58 AM
  • Anyone heard anything on this from Microsoft?

    A number of views in our system got corrupted as people were making changes on Friday. We have had UR12 installed for 3 weeks now and just noticed this issue. We can fix the broken views but making more changes has become dangerous and time consuming.

    Monday, May 20, 2013 4:27 PM
  • Hi Mayank,

    I never heard anything back on this. I eventually took a backup of the production DB and restored it to my Dev box. It fixed the problems. I know that the RU12 has got some hidden agenda when it installs. There are additional indexes it makes to the out of the box entities which is where I think my problem was.

    http://support.microsoft.com/kb/2791312

    Entities included.

    • Cases
    • Opportunities
    • Competitors
    • Contact (the Phone Number fields)
    • Business Unit
    • Connection
    • Connection Role
    • KB Article
    • Lead
    • Product
    • Sales Literature

    So at the end of the day, there was just data that had corrupted, causing the quickfind to fail.

    Thanks,

    Jarrod

    Tuesday, May 21, 2013 6:04 AM
  • Hi,

    The last response in this thread helped me in partially resolving the issue.

    http://social.msdn.microsoft.com/Forums/en-US/crm/thread/e17c9a53-6fe2-435f-a1ec-058899ffb1ef

    We found the view corruption to be entity specific. As per that link, the issue occurs only in entities where the native advanced find view had references to columns from related entities. We removed those references and recreated the custom views. If native views like quick find or associated view were broken, we updated the fetchxml in the database (risky business).

    We did the fix for 2 entities and I'm afraid this could show up on another entity that we customize in the future. We have opened a case with MS so that we are tagged and notified when a fix to this problem is released.

    Thanks,

    Mayank

    Tuesday, May 21, 2013 8:41 PM
  • Hi

    If you are still intrested in the issue above, then maybe have a look at this article, where I think I have a resolution that removes the real issue from the problem related entity.

    http://wikap.dk/2013/08/corruption-of-views-an-table-alias-dublicate-in-crm-2011-after-polaris-update/

    /Henrik

    Monday, August 12, 2013 2:37 PM
  • We have been having this issue a lot recently. The following post describes what I think was causing the issue and what we did to resolve it:

    http://rule30.wordpress.com/2014/04/11/fix-table-alias-xyz-is-not-unique-amongst-all-top-level-table-and-join-aliases/

    Hope that helps someone!
    Friday, April 11, 2014 12:58 PM