Integrating Dynamics crm 2011 with sharepoint 2010 error ‘List component is not installed on the SharePoint URL…’

Hi,

I had a problem integrating Dynamics CRM 2011 and Sharepoint 2010 that got me crazy and want to share the resolution with you just in case you experience it too.

Scenario

  • Dynamics CRM 2011 RTM
  • Sharepoint Server 2010.
  • Sharepoint list components installed as site feature [it does not work as a farm solution] in a new site collection within a completely new web application.
  • All on-premise.
  • Both on same domain.
  • None of them is a DC.

Problem

Under Settings->Document Management->Sharepoint Sites when I open my Sharepoint site and  click on the checkbox ‘List components installed’ I always get the following message:

List component is not installed on the SharePoint URL that you specified but you have selected the List component is installed check box. Click OK to save your settings. Click Cancel to got back and change your settings.

image

Url is OK and already Valid. Dynamics CRM List component feature is successfully activated.

The solution is deployed at site collection level as supposed.

Solution

Some things I tried (with no success) but appears to be necessary, so I recommend you to double check are:

  • Put the ‘/’ at the end of the url
  • Turn off firewalls.
  • Add Url mappings in Sharepoint (really I can’t see the point on this but was suggested in the forums)
  • Set browsing file ‘Permissive’ at web application level in Sharepoint

After all of the above I still had the same problem.

The actual cause was the identity the CRM WebAppPool was running with. It was running with NETWORK SERVICE and this appears to be the credential that CRM uses to try to reach Sharepoint and check if list component is installed. So, it fails due to insufficient permissions.

So, to solve the problem you should:

  • Create/have a domain account with the following privileges:
    • Domain user
    • Member of Performance Log Users
    • Member of Local Administrators group on SQL Server machine
    • Member of Local Administrators on the CRM web server
    • Read and write privileges on \Trace folder, by default located at \Program Files\Microsoft Dynamics CRM\Trace, and within the user folder under %AppData% in the local machine.
    • Read and write privileges for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM and sub-keys under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\MSCRMSandboxService
    • Member of CRM_WPG group. This group is created automatically during the installation of Dynamics CRM.
    • Administrator of the Sharepoint site collection where the list components are installed [maybe could have less privileges, but I used administrator]

Important:  remember this account cannot be the same used for Dynamics CRM installation neither SQL Server service can be running with the same account.

  • Change Dynamics CRM WebAppPool identity in IIS to use the new domain account created above.
  • Restart IIS.
  • Open Dynamics CRM Web and try again going to Settings->Document Management->Sharepoint Sites.
  • Open your Sharepoint site and click again on the checkbox ‘List components installed’
  • It should work now :)

Hope it helps to save you some time :)

PP

19 Comments

  • Also, remember the domain account for running AppPool must be different from the one used for installation and must NOT be a dynamimcs CRM user..

  • Domain admin account is enough ?

  • Domain admin is enough for installing Dynamics CRM and sharepoint components.
    The issue is that you cannot run the CRMWebAppPool with that identity not only for security reasons but also because if you used that account for installation, it could cause mis-behaviors.
    I suggest you use an identity with the privileges described in the post.
    Make sense?
    thanks,
    PP

  • This is great if your CRM is installed on-premise. I am running into this exact problem with RM Online. So, I obviously have no idea what the CRM App Pool is set to, and no way to change it if I did.

    I am using CRM 2011 Online and have SharePoint 2010 installed on a hosted server. I have complete access to SharePoint and that server. The list component is installed correctly and it is activated. Just like above the URL is valid and working. I can reach both the SharePoint site and CRM with no issues.

    I suspect there has to be some other way to resolve this problem. I have opened access on SharePoint for members to have full control. Also tried switching the site to anonymous. Tried alternate access mapping. Still fails with the same errors.

    So, if anyone else has fixed the problem of CRM 2011 Online and a hosted SharePoint 2010 (meaning not on your own domain) please let me know.

  • @Mike,
    Have you watched this video from Girish Raja?
    http://blogs.msdn.com/b/girishr/archive/2011/06/16/teched-na-2011-session-recording-crm-and-sharepoint.aspx

    Maybe it gives you an idea or maybe you could also write to him for some suggestions. Clearly, he seems to be the man with broad experience on this subject.

    Hope you tell us here the news,
    PP

  • Hi All,

    We recently changed the SharePoint port from 80 to 8080. Now i am not able to validate the port change in CRM Document Management settings.

    It says
    "Validation could not succeed because the list component could not be detected"

    We have claims and IFD configured on CRM.

    I tried to change the CRM AppPool account to domain account, but crm failed to load with error "An error occurred"

    Any one has any suggestions for me??

    Thanks in advance
    Dhruva

  • Hi @Dhruva
    What about firewall settings?

  • Hi,

    How can I perform same solution for such issue with considering that CRM in domain and SharePoint in another domain.

    Regards,

    Maged Said

  • Hi @Maged,
    Honestly I don't remember but don't think so..
    I presume that Sharepoint has to be in the same domain as CRM too, again, not sure, but that's my guess..

  • Hi,

    Have anyone tried integrating CRM Online and SharePoint on premise? I've read some comments on Girish Raja's post that this is possible, but I tried and was not successful. I have tried the integration successfully on both-on-premise deployment (one of the requirements there was for the CRM AppPool to have access to SharePoint, so i have no idea how am I going to do this for CRM online..) any idea would surely help. Thanks in advance.. :)

    Mary Ann

  • Hi @Mary,
    Honestly, haven't tried it but it sounds to me that you would need to set up ADFS + Azure AC. Not sure, honestly, but make sense to me and it sounds to me it would be the approach.
    Please let me know your comments as well as some finding that would help others.
    Thanks
    PP

  • I take great issue with the solution that Pablo has blogged here. I read through this page because I have run into the same nasty error on a number of occasions, and I have never been able to nail down exactly what the fix was (on one occasion, I went for lunch and when I came back it worked). I am still looking for the proper solution my self, but what I can say is that the CRM Application Pool account is never configured as a local administrator of any computer in any of my environments (as I would think it should never be) and yet I have always been able to get the SharePoint link working. I would still love to know exactly what causes this error. I think Pablo is right that it is a permissions error, but giving local admin rights is just an easy way out. Some times you need the easy way out, but that seems like a big security no no to me.

  • Thanks Jeff for your comments,

    BTW..I mean administrator of the site collection in sharepoint, not necessarily local admin of the server, makes more sense?

    thanks
    PP

  • I tried everything in this post but still ended up with the "List component is not installed on the SharePoint url" error.

    So I carefully read all the instructions again and realised that, knowing SharePoint, I'd seen a .wsp solution file and deployed it using stsadm -o addsolution lion, then used Central Administration to make it available to my web application and finally activated it as a Site Collection feature.

    What the instructions supplied with the download say is to upload the wsp file to the solution gallery in a site collection and to activate it once uploaded. So, after deactivating the site collection feature and cleaning up the deployment made via Central Admin. I added the solution file (.wsp) using the way documented it worked!!!

  • Thank you @nrodri,

    I think you came to a useful conclusion: privileges required are Read, Contribute and Design.

    BTW, one nice tip that @Aben gives is to add SharePoint site to your Trusted Sites.

    On the other hand, in your post you mention a request back from CRM List Component to CRM. Honestly, it's the first time I hear that. Could you please share where or how you found that out?. Sounds really curious. Also, by reading your post, I get the impression that you didn't need another domain account because you have SharePoint and CRM on the same box. Am I right? Here we are talking about both products on separate servers.

    Any further thoughts that may help others? I appreciate your comments.

    Thanks again for commenting here,
    PP

  • A conclusion regarding to set up Permissive Browsing: this is only for SharePoint on-premise, as an alternative instead of running the PowerShell script that allows .htc extension on the server.

    This is only helpful to enable buttons in the Document grid.

    Hope it helps.
    PP

  • Hi pablop,

    Regarding the resquest back from the CRM List Component, the findings are related with my troubleshooting. In CRM 4 setting up DNS load balanced addresses, specific database keys need to be changed that control what URLs the discovery and other services are held. In CRM 2011 this is the same, but we now have the nicer deployment tool which gives us the option to do this from the tool. So based on this my troubleshooting revealed that manually changing IIS port to 81 the List Component was failing, when changing the CRM 2011 ports in the deployment tools to also 81, this has fixed the issue. The conclusion is that the tool does this call-back to collect the correct key configuration from the configuration database to store for reference.
    This is also very common when you deploy the CRM Outlook client which it also refers to this database keys to collect the correct information to store in the windows registry.


    Regards
    Nuno

  • sharepoin2010: on-premise

    CRM: Online 2011

    still give me error :

    validation could not succeed because the list component could not be detected

  • In my case the issue was my user not having access permissions on SP

    Pointed me in the right direction thanks

Comments have been disabled for this content.