Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Getting the following the error when going to document where there's no sharepoint folder against the record:
An error occurred while loading the page. The URL may not have been mapped in the SharePoint Server. Ask your system administrator to check the Configure alternate access mappings settings in the SharePoint Central Administration.
I have tried the updated List component and still getting the same error. I tried deactivating and deleting the solution. I then uploaded and activate the new version and not change.
I can browser existing folders but cannot create new ones. I get the error in IE. From the console in Chrome this is what I've found so far:
1. createfolder.aspx on the solution has throws: Uncaught ReferenceError: IsNull is not defined in on line 11 [ if (IsNull(crmProxyIframeElement)) ]
2. This function is defined in SPGlobal.js and some how this is no loaded when the CreateFolderOnLoad is called by the ListComponent.
Error from Developer tools:
Not sure if anyone has any solution for this.
Thanks in advance,
Make sure you have the latest list component installed on SharePoint - blogs.msdn.com/.../impact-of-dynamics-crm-december-2012-service-update-and-sharepoint-online-service-update-on-crm-sharepoint-integration.aspx
Also - check that the Sandbox host is running if you are using SharePoint OnPrem.
Hope this helps,
Thanks for the reply.
I've installed the latest version from: www.microsoft.com/.../details.aspx and still getting the same error. I have a QA environment and work fine and not on the production environment. I've even tried the following steps:
1. Deactivated the list component solution
2. Stop / Started the Microsoft SharePoint Foundation Sandboxed Code Service in central administration
3. Re-activated the solution
2. Deleted the solution
3. Downloaded the latest list component from the Microsoft website (version 05.00.9690.4159, published: 2014-07-01)
4. Uploaded the extracted solution file.
5. Activated the uploaded solution.
Have deactivated the solution to confirm that CRM is connect to the right SP site and the SP page is displayed install of the CRM grid.
Not sure what else to try.
By any change do you have .net 4.5.2 installed and if you look in fiddler do you see __VIEWSTATEGENERATOR on the SharePoint server?
Dear Thomas, I have this exact same issue with the __VIEWSTATEGENERATOR. What is causing this? Or do you know a solution?
We too faced the same issue (intermittent) after the installation of Windows6.1-KB2894844-x64 . But we are able create new folder in IE 11.
This issue got fixed in UR17 (refer the below link)
We had the same issue. After we opened a support ticket we were assured that Rollup 17 would fix it. When that didn't work, we were assured that rollup 18 would fix it. When that didn't work they finally addressed the issue which is contained within the list component itself.
You have to use SharePoint Designer to modify the CreateFolder.aspx in the list component. (The SharePoint Designer has to be the same build as your SharePoint environment. i.e. We have SharePoint 2010 SP1, so I had to install SharePoint Designer and upgrade it to SP1).
1. In SharePoint Designer, connect to your SharePoint Site.
2. Click "All Files" within "Site Object"
3. Click CRMGrid in the main panel.
4. Find "CreateFolder.aspx" and right click and select "Edit File in Advanced Mode";
and move it to the line above :
I have also been "assured" that they are releasing a new list component soon that fixes the issue.
It was this morning that I talked to the support specialist that said the new list component would be released soon. I didn't take that to mean 4 days ago.
Business Applications communities