locked
CRM 2011 Update Rollup 10 issues Discussion RRS feed

  • General discussion

  • I figured we could use a place to track any issues that crop up as people start testing UR10 in their systems. 

    I haven't found anything yet other than the already documented limitations with the Office 2013 beta: http://support.microsoft.com/kb/2744957

    So, anyone else find anything?  Let's use this thread as a clearinghouse, especially if anyone finds regressions.


    The postings on this site are solely my own and do not represent or constitute Hitachi Solutions' positions, views, strategies or opinions.

    Tuesday, August 21, 2012 12:04 PM

All replies

  • We are having issues we believe are related to UR10, Account lookups throw a Generic SQL Error. This is any time we try to tab out auto resolve and from the search window. 

    David J

    Wednesday, August 22, 2012 10:52 PM
  • Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Generic SQL error.Detail:

    <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">

      <ErrorCode>-2147204784</ErrorCode>

      <ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic">

        <KeyValuePairOfstringanyType>

          <d2p1:key>CallStack</d2p1:key>

          <d2p1:value xmlns:d4p1="http://www.w3.org/2001/XMLSchema" i:type="d4p1:string">   at Microsoft.Crm.Extensibility.VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)

       at Microsoft.Crm.Extensibility.Pipeline.Execute(PipelineExecutionContext context)

       at Microsoft.Crm.Extensibility.MessageProcessor.Execute(PipelineExecutionContext context)

       at Microsoft.Crm.Extensibility.InternalMessageDispatcher.Execute(PipelineExecutionContext context)

       at Microsoft.Crm.Extensibility.ExternalMessageDispatcher.ExecuteInternal(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode, Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid transactionContextId, Int32 invocationSource, Nullable`1 requestId, Version endpointVersion)

       at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType)

       at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.Execute(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType)</d2p1:value>

        </KeyValuePairOfstringanyType>

      </ErrorDetails>

      <Message>Generic SQL error.</Message>

      <Timestamp>2012-08-22T21:51:40.678614Z</Timestamp>

      <InnerFault i:nil="true" />

      <TraceText i:nil="true" />

    </OrganizationServiceFault>


    David J

    Wednesday, August 22, 2012 10:53 PM
  • Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Generic SQL error.Detail:

    <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">

      <ErrorCode>-2147204784</ErrorCode>

      <ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic">

        <KeyValuePairOfstringanyType>

          <d2p1:key>CallStack</d2p1:key>

          <d2p1:value xmlns:d4p1="http://www.w3.org/2001/XMLSchema" i:type="d4p1:string">   at Microsoft.Crm.Extensibility.VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)

       at Microsoft.Crm.Extensibility.Pipeline.Execute(PipelineExecutionContext context)

       at Microsoft.Crm.Extensibility.MessageProcessor.Execute(PipelineExecutionContext context)

       at Microsoft.Crm.Extensibility.InternalMessageDispatcher.Execute(PipelineExecutionContext context)

       at Microsoft.Crm.Extensibility.ExternalMessageDispatcher.ExecuteInternal(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode, Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid transactionContextId, Int32 invocationSource, Nullable`1 requestId, Version endpointVersion)

       at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType)

       at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.Execute(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType)</d2p1:value>

        </KeyValuePairOfstringanyType>

      </ErrorDetails>

      <Message>Generic SQL error.</Message>

      <Timestamp>2012-08-22T21:51:40.678614Z</Timestamp>

      <InnerFault i:nil="true" />

      <TraceText i:nil="true" />

    </OrganizationServiceFault>


    David J

    We figured it out via a SQL trace.  On the Account Quickfind we had added zipcode, removing that field has resolved the immediate problem.


    David J

    Friday, August 24, 2012 12:05 AM
  • David

    I have a site which since UR10 all users get a Generic SQL Error on Quick Find on Lead

    Removing Zip/Postal Code from the Quick Find List of Find Fields and the error has gone away but this cannot be a permanent solution.

    Account and Contact which also have Zip/Postal Code in Quick Find are working OK.

    Julian


    Microsoft Dynamics CRM Specialist www.vigence.co.uk

    Tuesday, August 28, 2012 11:00 AM
  • If you believe you have found an issue with UR 10, I encourage you to open a support ticket with Microsoft.  This will ensure that Microsoft is aware of the issue or help you understand if it is an issue that is specific to your environment and give you a path to resolution.  Unfortunately, it it doesn't provide much value to post these isssue in the Forums as there is nothing we can do to help resolve the issue if there is a fix required from Microsoft.


    Regards, Donna

    Tuesday, August 28, 2012 1:11 PM
  • I am planning on doing some more investigation out of hours when no one is one the system. If there still is an error I plan to log in with Microsoft.


    Microsoft Dynamics CRM Specialist and MCT www.vigence.co.uk

    Tuesday, August 28, 2012 1:52 PM
  • Looks like the Quick Find problem is more widespread - see http://community.dynamics.com/product/crm/crmtechnical/b/microsoftdynamicscrmco/archive/2012/08/27/microsoft-dyanmics-crm-2011-update-rollup-10-bugs.aspx - you may need to translate

    Microsoft Dynamics CRM Specialist and MCT www.vigence.co.uk

    Tuesday, August 28, 2012 3:28 PM
  • This Rollup 10 issue stopped me in my tracks today:

    http://social.microsoft.com/Forums/en-US/crmdeployment/thread/19adc0c0-b888-499d-aa3a-d922e0c691da?prof=required

    In short, try to import a solution containing entities into an upgraded CRM organisation that has rollup 10 applied and you'll find that you can't. Not without hacking xml anyway.. but I'm not going to do that. I've created a support ticket but suspect others may have beaten me to it. I'll post the hotfix KB article as soon as I have one.

    Rob


    Microsoft Certified Technology Specialist (CRM) GAP Consulting Ltd Microsoft Community Contributor Award 2011

    Wednesday, August 29, 2012 1:10 PM
    Answerer
  • It would be very practical if we would have one sticky thread for the latest Update Rollup issues on the forums, to help everyone evaluate whether there are potential issues ahead when the plan the latest UR deployment, but I guess that wouldn't look so good on the front page of a forum run by MS.

    Anyway, I collected some of the most notable benefits and issues of Update Rollup 10 on my blog and tried to link back to the forum threads I found: http://niiranen.eu/crm/2012/08/to-update-or-not-to-update-rollup-that-is-the-question/


    Jukka Niiranen - My blog: Surviving CRM - Follow @jukkan on Twitter

    Thursday, August 30, 2012 5:46 PM
  • I think that's a great idea Jukka. What do you think Donna? would it be possible to add a pinned 'Latest Rollup Issues' discussion thread? Let's face it, no software release is perfect, I see no shame in pinning something like this. Having a single place to monitor the latest issues would help us all immensely.

    Microsoft Certified Technology Specialist (CRM) GAP Consulting Ltd Microsoft Community Contributor Award 2011

    Thursday, August 30, 2012 7:11 PM
    Answerer
  • While I do agree that someone needs to open the MS support tickets to get the hotfix process underway, I think there's quite a lot of value in having people collectively share their findings of both the errors and the workarounds/fixes. If we didn't have any social platforms for information exchange, Microsoft would just get a thousand support tickets on the same topic.

    Jukka Niiranen - My blog: Surviving CRM - Follow @jukkan on Twitter

    Thursday, August 30, 2012 7:37 PM
  • A few thoughts for consideration;

    • I agree, having a place to log issues we are encountering and sharing that information with the community adds value.
    • The challenge in using the forum to do that is that people often misunderstand the use of the Forum and get aggravated when their issues are not addressed as expected.  They confuse the Forum with a Support Forum.
    • I continually try to educate people regarding the right venue to report 'issues' or bugs and suggestions for product improvement to minimize frustration due to misunderstandings. 
    • Create a support ticket if you have a bug to report, go to Connect and vote for or create new product suggestions, ask How To type questions or help with unexpected errors in the Forums.
    • It is fine if Microsoft receives thousands of support cases.  That's good, it lets them know they have a high priority issue and it also ensures that the people who are experiencing the issue will be communicated with as soon as a fix is available.

    Maybe a better place to post the UR issues is the Microsoft CRM facebook page?  That ensures that Microsoft and the community have full visibility and minimizes the potential for misunderstandings in the forum.  (We can't fix bugs or issues in the Forums)

    https://www.facebook.com/#!/groups/21809302488/

    Another very good possibility is the CRM Wiki. We could build a page for each Update Rollup, tweet it, put it on Facebook, etc. and everyone can edit the page to add the issues they discover. 

    http://social.technet.microsoft.com/wiki/contents/articles/2486.microsoft-dynamics-crm-overview.aspx

    I hope this is helpful.

    Thanks all,


    Regards, Donna


    Thursday, August 30, 2012 9:26 PM
  • I think having a wiki page for Update Rollups would be a good option, as updates in streams like Facebook are not persistent information you can easily link back to or search. The challenge with the CRM Wiki currently is the lack of references between pages, but perhaps it would work if we'd put the following structure in place:

    * CRM Wiki main page: link to Update Rollups page

    *    Update Rollups page: links to each individual UR page

    *       Update Rollup 10: sections for official content + user reported issues / workarounds

    *       Update Rollup 11 etc.

    There's some excellent content published on the CRM in the Field blog, but what would be needed on top of that is some kind of a landing page with a proper index to the content, to give it more structure. The forums are a good place for discussing and analyzing individual issues around UR's, but I think the Technet Wiki might be a nice solution for collecting references to these threads. 

    So, the scenario could be something like this:

    • User A forum post: "Javascript web resource truncated after UR10 install"
    • User B reply: "I have the same problem. Did you open a ticket w/ MS already?"
    • User C appends wiki page Update Rollup 10, adds reference to forum thread with error description
    • User A reply: "got a hotfix from MS, they say it will be included in UR12"
    • User X appends UR10 wiki page with latest details

    Do you think this would work / provide value compared to the current practice of just posting various UR related threads on the forum?


    Jukka Niiranen - My blog: Surviving CRM - Follow @jukkan on Twitter


    Friday, August 31, 2012 12:48 PM
  • I say, go for it, and use the Wiki.  We can then point people to it in the forums, blog posts, etc.

    Regards, Donna

    Friday, August 31, 2012 1:19 PM
  • I think a wiki would be helpful as well.

    It seems like these CRM releases are degrading in quality with every new rollup or release. I've been working with Dynamics CRM from the beginning and I can't remember a time when it was so unstable. We haven't been able to apply a rollup in months because everything we try introduces new breaking issues. Is it just me or are others experiencing the same quality problems?

    Tuesday, September 4, 2012 1:33 PM
  • OK, I've now created a wiki page for Update Rollup 10: http://social.technet.microsoft.com/wiki/contents/articles/13437.update-rollup-10-for-microsoft-dynamics-crm-2011.aspx

    I added some pointers to the official MS content for download links & KB articles in the top section. At the end there's a Potential Issues section where I've listed ten errors reported by users after they've installed UR10. It's a short description of the error message, to help people find it through their search engine queries, followed by links to either forum threads or blog posts describing the issue and possible workarounds.

    If you think there's some changes needed to the structure/wording or have links to other potential UR10 related issues that you think the CRM community should be aware of, please go ahead and edit the page! I didn't create any general landing page Update Rollup information in the CRM Wiki yet, as there are existing articles like the build numbers page that probably could be leveraged in creating that.


    Jukka Niiranen - My blog: Surviving CRM - Follow @jukkan on Twitter

    Sunday, September 9, 2012 6:41 PM