Record Not Available error message on Internet Explorer only

(0) Share

Report

Posted on by Community Member

Hello,

I have come across a few instances where various users have been unable to access certain records when using Internet Explorer.

Other browsers such as Google Chrome worked fine.

Error message:

Record is unavailable. The requested record was not found or you do not have sufficient permission to view it.

Log:

Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #B4876D0ADetail:
<OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">
<ErrorCode>-2147220970</ErrorCode>
<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" />
<Message>System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #B4876D0A</Message>
<Timestamp>2015-10-22T10:15:38.4193316Z</Timestamp>
<InnerFault>
    <ErrorCode>-2147220969</ErrorCode>
    <ErrorDetails xmlns:d3p1="schemas.datacontract.org/.../System.Collections.Generic" />
    <Message>appointment With Id = a29a1769-9a71-e411-9995-005056030ccb Does Not Exist</Message>
    <Timestamp>2015-10-22T10:15:38.4193316Z</Timestamp>
    <InnerFault i:nil="true" />
    <TraceText i:nil="true" />
</InnerFault>
<TraceText i:nil="true" />
</OrganizationServiceFault>

With some users, resetting Internet Explorer and clearing cache (temporary files) would solve the problem. However, I also have some other users who still have problems. Reinstalling Internet Explorer doesn't solve the problem either.

Is there anyone who experienced this problem before?

Many thanks.

Joe

*This post is locked for comments

I have the same question (0)

All responses (21)

Answers (0)

Aileen Gusni 44,524 on at

Like (0)

Report

Joe

Can you check this appointment id

a29a1769-9a71-e411-9995-005056030ccb

Maybe can check using odata query designer whether got or not.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Joe - Our users started to get this intermittently error since Microsoft migrated our instance to 2015 Update 1. We have instructed our users to clear their IE cache and that appears to help but the error will appear again. We have an open incident ticket with Microsoft. We are going to ask our user to try Chrome as well.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yeh, I noticed that sometimes after clearing out the cache it helps, but I have also seen cases where it doesn't.

I wonder what was included in the update that caused all these nightmares.

Joe

Was this reply helpful? Yes No
NicksTuk 1,833 on at

Like (0)

Report

Do you have the organization URL added to trusted sites?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yeh, tried it already.

Was this reply helpful? Yes No
Laura Robinson MSFT on at

Like (0)

Report

Hi there, what is the support ticket number raised for this? Thanks!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello,

My colleague has now logged with Microsoft. Reference number: 115102794306309

Thanks.

Joe

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Joe, did you have any luck with this issue? We are experiencing the same problem.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Not yet, but I will have a meeting with a representative from Microsoft to address the issue this morning.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Joe,

I ran into this problem with my CRM users before. I logged a service request with MSFT. They cleared the caches, delete all local temp files ( run %temp%"), delete all cookies, plugin data. and it worked.

Still a pain in the rear to go through all these steps because MSFT did not get the caches straight.

Was this reply helpful? Yes No