web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

SharePoint List component throws an "Web Part Error: Sandboxed code execution request failed." error

(0) ShareShare
ReportReport
Posted on by 2

Hi all,

We're using the SharePoint 2013 list component to integrate CRM 2013 Online with SharePoint 2013 Online.

At a customer site this list component can't handle the creation of the new SharePoint folder in case of a new CRM entity. The call to the '[our sharepoint site url]/crmgrid/createfolder.aspx' returns an error with a correlation id etc:

    Web Part Error: Sandboxed code execution request failed.

We once had this same error when getting the documents, but that dissappeared after a day.

We are already using the latest version of the "Microsoft Dynamics CRM 2011 List Component for Microsoft SharePoint Server 2010 and Microsoft SharePoint Server 2013 (for multiple browsers)" which can be found here:

www.microsoft.com/.../details.aspx

So what could be causing this?

Any help is appreciated.

Maarten

*This post is locked for comments

I have the same question (0)
  • Rasmus R. Aardal Profile Picture
    on at

    Hello Maarten,

    First of all, Microsoft has released a CRM 2013 List Component for SharePoint 2010/2013. The "Download List Component" link in CRM points to the old one which is for CRM 2011.

    The new List Component can be found at www.microsoft.com/.../details.aspx

    Secondly, there is currently an issue with SharePoint Online that causes the folder creation to fail given certain criteria:

    The document management is set to be "Based on entity" so that the folder structure looks like this (In the case of creating opportunity folders) [...].SharePoint.com/site/[name of site]/account/[Account name]/opportunity/[Opportunity name].

    The List Component then attempts to create the folder named "opportunity" directly under the "Account name"-folder every time you try to create a "Opportunity name"-folder.

    Since the "opportunity" folder is created the first time an opportunity is created for each account, any subsequent opportunity will fail when trying to create a document folder since the folder named "opportunity" already exists.

    This issue is recognized and currently being investigated by Microsoft Support.

    I hope the explaination is understandable, and I hope that this is not the issue you are facing seeing as it needs to be fixed with a rollup/hotfix for SharePoint Online.

    Good luck!

    Regards,

    Rasmus

  • Maarten Docter Profile Picture
    2 on at

    Hi Rasmus,

    Thanks for your reply. You are absolutely right about the download link. In my hurry to get this post online, I copied the wrong URL and refered to the wrong page. We are using the CRM 2013 version though, as you suggest.

    The error occurs when opening a newly created (saved already, so it is not a draft) contact, click 'Documents' in the top nav. The list component detects that there are no Document Locations in CRM for this record, so it pop-ups a messagebox informing me that a new folder will be created in SharePoint. After clicking OK, the list component tries to create the folder, but this fails. So in our case there's no nesting of opportunities etc.

    Listing files works for existing records, so the list component seems to work partially.

    Kind regards,

    Maarten

  • Darren Bayley Profile Picture
    335 on at

    Hi Maarten,

    Did you ever get a solution to this issue as I'm experiencing it as well.

    Many thanks

  • Maarten Docter Profile Picture
    2 on at

    Hi Darren,

    The problem will go away (if you wait long enough). From time to time SharePoint seems to throw this error while using the list component. SharePoint is in my opinion the most buggy/down service of the Office 365 suite.

    You could try re-installing the list component. This will speed up the process.

    If you are using CRM 2013 (Spring Release / SP1) you can switch to server side synchronization which will resolve this issue too, because it doesn't use the list component anymore. But you'll loose the ability to display/edit custom (site) columns :-( (if you are using them now).

    Cheers, Maarten

  • Darren Bayley Profile Picture
    335 on at

    Hi Maarten,

    Thanks for the timely reply - I was coming to that conclusion as it was broken for 5 days, started working for a couple of hours and then broke again, all with nothing being changed on our side.

    Not exactly an ideal solution but at least I now know it will go away

    Thanks again

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans