The following steps are involved in installing Workflow Manager:
- Download the Web Platform Installer from this location Download Link
Run the downloaded installer and the workflow Manager installer should be available on the next screen
Proceed through the wizard to begin installation
Once the installation has completed, the Configuration Wizard will open as shown below
- For the sake of the post, Custom Settings will be used.
Fill the necessary information regarding your SQL server. Customize the name of the database so that you can easily identify them.
Once the wizard has been filled, copy the PowerShell commands so that it can be reused when required and start the configuration deployment,
Verification that all the installation has been completed properly.
Under All Programs, browse to Workflow manager and open Workflow manager PowerShell,
Get-WFFarm | ft HttpPort and Get-WFFarm | ft HttpPorts
to check that ports have been deployed properly,
Connecting Workflow Server to SharePoint 2013 Farm
- From a SharePoint 2013 server within the farm, open SharePoint Management Shell as an administrator
Deploy the following command to register the SharePoint site with the workflow server
Register-SPWorkflowService -SPSite http://name_Site" -WorkflowHostUri "https://name_workflow_server:12290/"-AllowOAuthHttp
Open SharePoint 2013 Designer and you should be able to create either 2013 or 2010 workflows
The above error occurred from the Main App server. The workflow server was installed on one of the Web Front Ends. To resolve this, download Workflow Client from this location
This was purely because my DNS was pointed at that point for the site to the APP server and not to the web server. So after installing the client tool and a restart, everything was “A” ok.
The farm is a fresh SharePoint 2010 SP1 server farm. I got a database for a Site Collection that we use for Demo’s. I presume the content database has its origins from SharePoint 2010 as well. Anyways, the search page had issues for some reason and I needed to delete it and recreate a search centre within the Site. Unfortunately I was not able to delete the search site from within this Site with the following error being thrown
Since the farm was on SP1 the content Database which I presumed during the attach method should have upgraded itself, for some reason didn’t. I used the following two commands as shown below
This gave me the ID for the database that I was looking for. This command is then followed by the usage of
Upgrade-SPContentDatabase -Identity YourDatabaseIDGoesHere
Press Y to continue and once completed , you should be able to delete your site now J
References and Credits:
http://www.ryanonrails.com/2011/02/25/hooking-crm-2011-and-share-point-2010-together/ and follow him on Twitter http://twitter.com/#!/ryanonrails
Download the CRM 2011 List component for SharePoint 2010 solution from here
Extraction of the folder will reveal the following items
Open Central Administration and click on Application Management. Then Browse to Web Applications and this will open the web applications currently installed on SharePoint. Highlight the web application that will host the Site Collection to be integrated with CRM as shown below. On the ribbon the icon for General Settings will no longer be greyed out as shown below
Under the Web Applications general settings window that has now opened, browse to the end of the window to the section containing Browser File Handling permissions and click on “Permissive”.
Open your site collection and under site actions, click on Site Settings.
Select Solutions from the Gallery and the following window called Solutions gallery will pop open. Choose upload and browse to the folder that contains the extracted files from step 2
Press upload and the following box will pop up. “CLICK CLOSE”
At this stage, the solution has been uploaded onto the Site Collection properly. The CRM list component requires Microsoft SharePoint Foundation Code Service to be running before you can activate the solution.
For the sake of example, I used Search Server Express 2010 with a SQL 2008 R2 DB server.
The following services were started in order during the installation of SharePoint,
- State Service
- Usage and Health Service
- Search Foundation Search
- Search Service
- Sandbox Solution Service – Foundation Code Service
- Web Analytics Service
So to continue with the CRM integration post,
Before activating the solution, verify that the appropriate service is running
Open either PowerShell or SharePoint Management Shell and browse to the folder that contains the extracted files. Within this folder is a PowerShell file called AllowHtcExtn.ps1. The execution of this file is only necessary if SharePoint is installed on a Domain Controller, for example in a development environment. But I have also found if the VM that has SharePoint installed on it, was previously a domain controller and was “dcpromed” , then run the script. There is no harm in running the script even if you are not sure.
Remember to add the URL – http://servername at the end as shown
Head back to the site collection and open Solution Gallery under Site Settings again. Click Activate this time , to activate the solution,
Within a few seconds, the solution will display activated as shown
Open CRM and under Settings , click on Document Management,
- Solution not activating :-
- Installation of SharePoint has been corrupted for some reason.
- Running of the AllowHtcExtn.ps1 Script wasn’t done with the proper arguments.
- Didn’t add the Brower File Handling permission for the Web Application.
- CRM keeps complaining the List Component is not activated even though the site is valid URL
Download the latest SharePoint LogViewer to view the logs for SharePoint in a much more readable format.
SharePoint LogViewer – View ULS logs the easy and efficient way.