2017-07-04 51 views
2

Dynamics CRM 365默认情况下仅在实体窗体的注释块上演示有限数量的注释。在我的情况下,它是10个音符。当用户滚动记录时,剩下的笔记应该是'延迟加载'。不知怎的,这个功能被打破了,笔记没有加载。CRM:在窗体上显示所有注释而不是延迟加载

enter image description here

没有什么有趣的既不在控制台,也没有在服务器的事件日志。这是完全的怪病。

是否有任何选项可以同时装载所有纸币,如在旧的CRM 2011中一样?

或者,也许任何人都可以建议如何调查此问题?


UPDATE: 刚才检查这一问题上的“警告”级别追踪工具,这里就是它表明,当我尝试加载注释:

[2017-07-06 08:39:43.344] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread: 39 |Category: Exception |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 055f8ace-5e77-4c01-b980-0e97088ed4aa |ActivityId: 055f8ace-5e77-4c01-b980-0e97088ed4aa | CrmHttpException..ctor ilOffset = 0x22 
    at CrmHttpException..ctor(HttpStatusCode statusCode, String message, Object[] args) ilOffset = 0x22 
    at CrmODataOptimisticConcurrencyHelper.HandleGetMatchETags(CrmODataExecutionContext context, Entity entity) ilOffset = 0x129 
    at CrmODataServiceDataProvider.RetrieveEntityWithRelatedRecords(CrmODataExecutionContext context, EntityReference primaryEntityReference, QueryExpression qe, RelationshipQueryCollection relatedEntitiesQuery) ilOffset = 0x19 
    at CrmODataServiceDataProvider.RetrieveEdmEntity(CrmODataExecutionContext context, String edmEntityName, String entityKeyValue, ODataQueryOptions queryOptions) ilOffset = 0x2D 
    at EntityController.GetEntity(String entityName, String key) ilOffset = 0x32 
    at ilOffset = 0xFFFFFFFF 
    at <>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters) ilOffset = 0x0 
    at ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken) ilOffset = 0x34 
    at <InvokeActionAsyncCore>d__0.MoveNext() ilOffset = 0x52 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at ApiControllerActionInvoker.InvokeActionAsyncCore(HttpActionContext actionContext, CancellationToken cancellationToken) ilOffset = 0x35 
    at ApiControllerActionInvoker.InvokeActionAsync(HttpActionContext actionContext, CancellationToken cancellationToken) ilOffset = 0x3 
    at <ExecuteAsync>d__2.MoveNext() ilOffset = 0xD9 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at ActionFilterResult.ExecuteAsync(CancellationToken cancellationToken) ilOffset = 0x35 
    at ApiController.ExecuteAsync(HttpControllerContext controllerContext, CancellationToken cancellationToken) ilOffset = 0x138 
    at <SendAsync>d__1.MoveNext() ilOffset = 0x123 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at HttpControllerDispatcher.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at HttpMessageInvoker.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3C 
    at HttpRoutingDispatcher.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0xBF 
    at DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x19 
    at <SendAsync>d__0.MoveNext() ilOffset = 0x17D 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at CorsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x19 
    at <SendAsync>d__0.MoveNext() ilOffset = 0x50 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at CrmETagMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x19 
    at <SendAsync>d__0.MoveNext() ilOffset = 0xF 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at CrmDelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x19 
    at <SendAsync>d__0.MoveNext() ilOffset = 0x11D 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at HttpServer.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at HttpMessageInvoker.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3C 
    at <ProcessRequestAsyncCore>d__0.MoveNext() ilOffset = 0x96 
    at AsyncTaskMethodBuilder.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at HttpControllerHandler.ProcessRequestAsyncCore(HttpContextBase contextBase) ilOffset = 0x2C 
    at TaskAsyncHelper.BeginTask(Func`1 taskFunc, AsyncCallback callback, Object state) ilOffset = 0xD 
    at CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() ilOffset = 0xE6 
    at HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) ilOffset = 0x3C 
    at PipelineStepManager.ResumeSteps(Exception error) ilOffset = 0x27A 
    at HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) ilOffset = 0x31 
    at HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) ilOffset = 0xB0 
    at PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) ilOffset = 0x131 
    at PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) ilOffset = 0x0 
    at UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) ilOffset = 0xFFFFFFFF 
    at UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) ilOffset = 0xFFFFFFFF 
    at PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) ilOffset = 0x1E7 
    at PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) ilOffset = 0x0 
>Crm Exception: Message: The requested record matches a specified If-None-Match version., ErrorCode: -2147088246 
[2017-07-06 08:39:43.344] Process: w3wp |Organization:3eb43172-29f4-dd11-80b4-0015178dc928 |Thread: 39 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 055f8ace-5e77-4c01-b980-0e97088ed4aa |ActivityId: 055f8ace-5e77-4c01-b980-0e97088ed4aa | CrmODataUtilities.Trace ilOffset = 0x24 
>{"Error":{"InnerError":null,"Message":"CrmHttpException: The requested record matches a specified If-None-Match version."}} 
+0

我会尝试在香草组织中重新创建问题,以查看它是否只发生在您的组织或平台错误中(在这种情况下,我会将它提交给MS支持团队)。 –

+0

@FedericoJousset我已经运行了跟踪工具,它显示了我的例外情况,请参阅更新。 –

+1

对不起,不幸的是我以前没有遇到过这个错误,并且关于它的信息不是很好。 Web服务错误代码将其描述为“Dynamics 365中的Wep Api发生故障”。并且它可能与CRM创建的请求(使用If-None-Match标头)来查询注释有关。您可以尝试使用Fiddler获取正在生成的请求,以查看是否发现错误,但我会将其作为MS支持团队的错误提出。 –

回答

1

@Dot_NETPro,现在的问题是解决了。

根目录位于Activity Feeds系统renderOlderPosts函数中,因为我们在以前的更新包中禁用了它,因为它在页面上为所有用户引发了空引用异常(因为MS bug)。该功能似乎没有被CRM使用,但在下一个更新包中,它开始渲染评论。此外,现在在最新的更新包中修复了空引用异常。