locked
Cannot activate Crm List component RRS feed

  • Question

  • Trying to investigate the built-in solution for connecting CRM and Sharepoint...and trying to install the list component.

    I have a problem when activating the list component. SharePoint comes back with a 403 Forbidden reply - and a message similar to "This page requires you to log in". The user is site collection administrator and is also able to upload the solution, so he should have sufficient rights...

    Has anybody experienced this error, or know what causes this?

     

    Wednesday, May 25, 2011 2:06 PM

All replies

  • Hi,

    Have you installed and activated the list component "crmlistcomponent.wsp" in SharePoint site solution gallery?


    Thank You, Jehanzeb Javeed, http://worldofdynamics.blogspot.com Linked-In Profile | CodePlex Profile
    Wednesday, May 25, 2011 2:22 PM
  • The problem is activating the solution in SharePoint. It just says "403 Forbidden" - and then nothing happens.
    Thursday, May 26, 2011 6:46 AM
  • Hi,

    I hope you have performed these steps before activating the component into SharePoint solution gallery but i am writing for these steps for your verification:
    Preparing SharePoint for the Microsoft Dynamics CRM List Component

    1. Start the Microsoft SharePoint Foundation User Code Service from SharePoint site Administration
    2. Allow htc files in SharePoint (PowerShell script included with components will do this)
    a. Open PowerShell and navigate to the location that you downloaded and extracted the Microsoft Dynamics CRM List Component.
    b. In the CRMList folder, you will find a file named AllowHtcExtn.ps1.
    c. Execute the script while specifying the Web Application or Site Collection that you want to utilize for Microsoft Dynamics CRM.
    d. PS C:\Users\Administrator\Desktop> .\AllowHtcExtn.ps1 http://crm1srv:83

    Please mark as answer if you find the reply useful.

    Thank You,
    Jehanzeb Javeed,

    http://worldofdynamics.blogspot.com
    Linked-In Profile |CodePlex Profile



     


    Thank You, Jehanzeb Javeed, http://worldofdynamics.blogspot.com Linked-In Profile | CodePlex Profile
    • Proposed as answer by rkDTT Monday, March 18, 2013 9:45 PM
    Thursday, May 26, 2011 7:49 AM
  • 1. is running

    2. Has been restarted, but SharePoint does not want to activate the solution.

    Tried deploying it as a farm solution, which works, but it seems like CRM does not like that when going through the document management configuration.

     

    Friday, May 27, 2011 6:15 AM
  • Hi,
    If solution is not activating then you need to allow Htc files in SharePoint. Please follow the steps below for solution:
    1.Open PowerShell and navigate to the location that you downloaded and extracted the Microsoft Dynamics CRM List Component.
    2.In the CRMList folder, you will find a file named AllowHtcExtn.ps1.
    3.Execute the script while specifying the Web Application or Site Collection that you want to utilize for Microsoft Dynamics CRM.
    4.Set current directory to CRM SharePoint connecter folder i.e. if CRM SharePoint Connecter folder location is “E:\ Microsoft Dynamics CRM 2011\RTM\SharePoint Connecter” then in PowerShell command prompt type:
    Cd “E:\ Microsoft Dynamics CRM 2011\RTM\SharePoint Connecter”
    5.Now type the following command or copy the command and right click on PowerShell to paste it
    .\AllowHtcExtn.ps1 http://sharepointurl:83
    *Make sure to replace http://sharepointurl:83 with your SharePoint web application URL.
    Please mark as answer if you find the reply useful.

    Thank You,
    Jehanzeb Javeed,
    http://worldofdynamics.blogspot.com
    Linked-In Profile |CodePlex Profile


    • Proposed as answer by carrema Saturday, March 30, 2013 7:26 PM
    Friday, May 27, 2011 1:42 PM
  • I faced problems as well, try something listed in my post, http://crminpractice.blogspot.com/2011/05/crm-2011-list-component-does-not-work.html
    never give up.



    Wednesday, June 1, 2011 7:10 AM
  • I am having the same issue. Did you get this to work?
    Wednesday, June 8, 2011 6:22 PM
  • Did get this to work, but I didn't fix it so I don't have all the details, but it involved changing the account the sandbox service is executed by. Not sure what it was executed before the change, and not sure what it is executed after the change, but going from lets say the "Network Service" account to a domain user account (SPService??) did fix it.
    Thursday, June 9, 2011 7:09 AM