SharePoint integration - Record Is Unavailable

(4) Share

Report

Posted on by MLarsen

508

Logged into CRM as System Administrator and trying to access 'Configure Server-Based SharePoint Integration' but I get a message saying 'Record Is Unavailable'.

I have the same question (0)

All responses (6)

Answers (1)

Adrian Begovich 1,027 Moderator on at

Like (0)

Report

RE: SharePoint integration - Record Is Unavailable

Hi MLarsen,

This error can occur due to a caching issue. Try closing your browser windows or clearing your cache before logging back into Dynamics CRM. Alternatively, use a different browser or access Dynamics CRM in private mode.

Was this reply helpful? Yes No
MLarsen 508 on at

Like (0)

Report

RE: SharePoint integration - Record Is Unavailable

Hello and thank you for the answer. I have tried to do this from another server, pc, in-private and other browser, same issue.

Was this reply helpful? Yes No
MLarsen 508 on at

Like (0)

Report

RE: SharePoint integration - Record Is Unavailable

Enabled Tracing and in the trace log I get the following error message:

>Crm Exception: Message: partnerapplication With Id = 38616d01-8e81-42dd-82fb-b68f2cecac3a Does Not Exist, ErrorCode: -2147220969, InnerException: Microsoft.Crm.BusinessEntities.CrmObjectNotFoundException: partnerapplication With Id = 38616d01-8e81-42dd-82fb-b68f2cecac3a Does Not Exist

at Microsoft.Crm.Caching.PartnerApplicationCacheLoader.LoadCacheData(Guid key, ExecutionContext context)

at Microsoft.Crm.Caching.ObjectModelCacheLoader`2.LoadCacheDataInternal(TKey key, Object existingDataContainer, IOrganizationContext context)

at Microsoft.Crm.Caching.ObjectModelCacheLoader`2.LoadCacheData(TKey key, IOrganizationContext context)

at Microsoft.Crm.Caching.CrmMultiOrgCacheBase`2.CreateEntry(TKey key, IOrganizationContext context)

at Microsoft.Crm.Caching.CrmMultiOrgCacheBase`2.<>c__DisplayClass19_0.<LookupEntry>b__2()

at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action)

at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)

at Microsoft.Crm.Caching.CrmMultiOrgCacheBase`2.LookupEntry(TKey key, IOrganizationContext context)

at Microsoft.Crm.ObjectModel.SharePointProvisioningHelperService.RetrieveSharePointGlobalSettings(ExecutionContext context)

[2020-11-20 12:30:08.424] Process: w3wp |Organization:f09d451e-ebd1-4eb4-964c-d70cd58d7663 |Thread: 36 |Category: Platform |User: 70054d77-9a10-e811-80d1-0050569c4ec3 |Level: Error |ReqId: d4ab6ea2-66be-4fd0-b183-b6e689e8c9b1 |ActivityId: 96524506-545e-44e2-a78f-38e38ca8a001 | MessageProcessor.Execute ilOffset = 0x237

>MessageProcessor fail to process message 'RetrieveSharePointGlobalSettings' for 'sharepointdocument'.

Was this reply helpful? Yes No
Suggested answer

Bipin D365 28,983 Moderator on at

Like (0)

Report

RE: SharePoint integration - Record Is Unavailable

Hi,

Try below options and see if it works.

1. do IISRESET

2. Restart Ansyc services

Please mark my answer verified if i were helpful

Was this reply helpful? Yes No
Verified answer

MLarsen 508 on at

Like (0)

Report

RE: SharePoint integration - Record Is Unavailable

I found out that I could hit the OK button, then hit the Next button, then I got to the normal wizard screen. After integration activated everything normal.

Was this reply helpful? Yes No
Inogic 682 on at

Like (0)

Report
SharePoint integration - Record Is Unavailable

Hi,

When attempting to configure Server-Based SharePoint Integration in Dynamics 365 CE and encountering the “Record is Unavailable” error, even as a System Administrator, it usually points to missing privileges or record-level access issues within the CRM environment itself.
1. Understand the Error:
Error Message: “The requested record was not found or you do not have sufficient permissions to view it.”
This typically indicates:

The user does not have access to the SharePoint Site record in CRM.

Or, the SharePoint Site record was deleted or is corrupted.

Or, there are missing privileges related to document management settings.

Even if you're logged in as a System Administrator, the CRM security model requires that you have explicit access to any records you interact with.
2. Possible Root Causes
Here’s what to check and troubleshoot:
Record Ownership and Access

Go to Advanced Find > SharePoint Sites, and confirm the record exists.

Make sure the System Administrator has read access to the SharePoint Site record.

If no record exists, you may need to create a new SharePoint Site record before attempting integration.

Security Role Privileges

Ensure your System Administrator role has full privileges under:

Customizations > Document Management

Business Management > SharePoint Site

Customization > Entity-level access

Missing read/write privileges on these entities can cause this behavior.

Corrupt or Orphaned Records

Sometimes, if a previously configured SharePoint site record was deleted improperly, the configuration reference may break.

In this case, you can try removing existing site references from the backend (only if you're familiar with database-level operations) or contact Microsoft support for a clean-up.

3. Workaround or Recovery

Try accessing the “SharePoint Sites” section first, and manually validate or create the site record.

After ensuring the record is present and accessible, revisit the “Configure Server-Based SharePoint Integration” wizard.

4. For Seamless Configuration
If you plan to enforce security alignment with CRM privileges and access rights in SharePoint (e.g., BUs, teams), consider using a solution like SharePoint Security Sync by Inogic after resolving this issue.
It allows you to:

Securely map user-level access to SharePoint folders

Automate folder creation and permission sync from Dynamics CRM to SharePoint

Prevent unauthorized access based on Dynamics privileges

Summary Checklist
Verify the existence and accessibility of the SharePoint Site record
Ensure proper security role privileges
Check for deleted or orphaned references
Create/repair the site record before configuring the integration
Once corrected, you should be able to run the configuration wizard without this error.

Thanks,

Sam

Was this reply helpful? Yes No