Anup Shah Support Engineer Microsoft Customer Services and Support. 14/February/2011. (Draft) Team Blog:

Transcription

1 Installing & Configuring SharePoint Foundation 2010 on Windows Server 2008 R2 in Preparation to Host Microsoft Dynamics AX 2009 Role Centers and Enterprise Portal Feature Anup Shah Support Engineer Microsoft Customer Services and Support Team Blog: 14/February/2011 (Draft) This document is for illustration purposes only. Microsoft disclaims all warranties and conditions with regard to use of the programming example for other purposes. Microsoft shall not, at any time, be liable for any special, direct, indirect or consequential damages, whether in an action of contract, negligence or other action arising out of or in connection with the use or performance of the programming example. Nothing herein should be construed as constituting any kind of warranty. See terms at 1

2 Table of Contents Installing & Configuring SharePoint Foundation 2010 on Windows Server 2008 R2 in Preparation to Host Microsoft Dynamics AX 2009 Role Centers and Enterprise Portal Feature... 1 Summary:... 3 Topology:... 3 Software Installation Summary:... 3 Detailed installation steps for Configuring SharePoint to host Dynamics AX Enterprise Portal Server... 3 Step 1: Download and Install the pre-requisites for SharePoint 2010 and Microsoft Dynamics AX 2009 Role Centers and Enterprise Portal... 4 Step 2: Download, Install and Configure SharePoint Foundation Step 3: Patching Microsoft Dynamics AX 2009 Setup files with hotfix KB Step 4: Installing AX 2009 Kernel and Application updates that add compatibility support for Microsoft SharePoint Step 5: Deploying Microsoft Dynamics AX 2009 Role Centers and Enterprise Portal List of Known Issues and Resolutions: Appendix A Configuring Application Pool User Account Appendix B Unable to detect the correct version of SharePoint Appendix C List of Application Pools created by SharePoint Foundation

3 Summary: The following document details my user experience of installing and configuring Microsoft SharePoint Foundation 2010, in preparation to deploy Microsoft Dynamics AX Role Centers and Enterprise Portal (RC+EP) feature. Topology: I have the following server topology - One Active Directory Server One Server hosting AX 2009 AOS and SQL Server 2008 SP1 + CU9 One Server that will host SharePoint Foundation 2010, and will be host for AX 2009 Role Centers and Enterprise Portal All 3 Servers are running Windows Server 2008 R2 Enterprise Edition Software Installation Summary: AOS Server The AOS server hosts the contoso demo database, and is running AX 2009 SP1 + RU4 (AX Kernel and Application build ) SQL Server It is recommended that you run SQL Server 2008 R2 Database Engine to host the SharePoint 2010 database. However at the time I created this document I was running SQL Server 2008 SP1 + CU9 ( ) Database Engine. Enterprise Portal Server Running SharePoint Foundation 2010, with Microsoft Dynamics AX 2009 Role Centers and Enterprise Portal feature installed Detailed installation steps for Configuring SharePoint to host Dynamics AX Enterprise Portal Server I have a Windows 2008 R2 Enterprise Edition server installed with no Roles or Features deployed. It is a member of the same Active Directory Domain as my SQL and AOS servers. I am logged in as a Local Admin user account which is also my AX Admin user account, and the user account has the following rights and privileges as described in: Administrative and service accounts required for initial deployment (SharePoint Foundation 2010) : I prepared my Windows 2008 R2 server by following the guide on TechNet on how to Deploy a single server with SQL Server (SharePoint Foundation 2010) - You must read the guide and the following step by no means replace what the guide suggests. 3

4 Step 1: Download and Install the pre-requisites for SharePoint 2010 and Microsoft Dynamics AX 2009 Role Centers and Enterprise Portal When you run the SharePoint Foundation 2010 setup, on the splash screen there is an option to Install Software Pre-Requisites and running this would check if you have all the required software and windows roles and if not it will set them up and download and install any missing pre-requisites software from the internet. I however took the option of manually installing all the pre-requisites to highlight what is required. A summary of the steps I took to setup my server following the minimum requirements for the following environments Database server in a farm and Front-end Web servers and application servers in a farm : (1) Enabled the Application and Web Server (IIS) roles and.net Framework and PowerShell Integrated Scripting Environment Features by running the following command in an elevated cmd prompt NOTE: The following needs to be run as one single command line, and it is truncated for presentation only ServermanagerCMD -install Web-Server Web-Common-Http Web-Static-Content Web-Default-Doc Web-Dir- Browsing Web-Http-Errors Web-App-Dev Web-Asp-Net Web-Net-Ext Web-ISAPI-Ext Web-ISAPI-Filter Web- Health Web-Http-Logging Web-Log-Libraries Web-Request-Monitor Web-Http-Tracing Web-Security Web- Basic-Auth Web-Windows-Auth Web-Filtering Web-Digest-Auth Web-Performance Web-Stat-Compression Web- Dyn-Compression Web-Mgmt-Tools Web-Mgmt-Console Web-Mgmt-Compat Web-Metabase Web-WMI Web-Lgcy- Scripting Web-Lgcy-Mgmt-Console Web-Windows-Auth NET-Framework-Core WAS WAS-Process-Model WAS-NET- Environment WAS-Config-APIs Application-Server AS-Web-Support AS-TCP-Port-Sharing AS-WAS-Support AS- HTTP-Activation AS-TCP-Activation AS-Named-Pipes AS-Net-Framework PowerShell-ISE -logpath %TEMP%\IISInstall.log (2) Downloaded and installed the following fixes and applications (NOTE: The Windows fixes listed below are for Windows Server 2008 R2 ONLY. Refer to Hardware and software requirements for SharePoint 2010 for links to fixes for Windows Server 2008 x Microsoft Sync Framework Runtime v1.0 (x64): Microsoft Office 2010 Filter Pack (64bit) aka Microsoft Filter Pack 2.0: 4

5 Microsoft Chart Controls for the Microsoft.NET Framework 3.5: ADO.NET Data Services Update for.net Framework 3.5 SP1 (x64): A hotfix for the.net Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF (x64): Windows Identity Foundation (WIF) x64: KB QFE for SharePoint issues - Perf Counter fix & User Impersonation (x64): (3) Downloaded and installed the following SQL components from the Microsoft SQL Server 2008 Feature Pack, April 2009 web page: SQL Server 2008 Native Client (x64): 4D11-AB51-6A65019D4706/sqlncli.msi Microsoft ADOMD.NET (x64): AB51-6A65019D4706/SQLSERVER2008_ASADOMD10.msi Microsoft Analysis Management Objects (x64) (This is required component for installing the AX 2009 Role Centers and Enterprise Portal Feature): 4D11-AB51-6A65019D4706/SQLSERVER2008_ASAMO10.msi 5

6 Step 2: Download, Install and Configure SharePoint Foundation 2010 NOTE: I am logged in as a Local Admin user account which is also my AX Admin user account, and the user confirms to the requirements detailed at I downloaded SharePoint Foundation 2010 from and ran it and selected the option Install SharePoint Foundation from the initial splash screen. Read and accepted the Licence terms and clicked Continue Clicked on option Server Farm 6

7 In the Server Type form selected option Complete and clicked on Install Now button: After the install left the check box selected to run the configuration wizard, and clicked Close: 7

8 On the Welcome to SharePoint Products page, clicked Next: In the dialog box that notifies you that some services might need to be restarted during configuration, clicked Yes: 8

9 On the Connect to a server farm page, clicked Create a new server farm, and then clicked Next: On the Specify Configuration Database Settings page I specified the SQL Server that I m using that will host my SharePoint databases; specified the Configuration Database name; and specified my domain username of the server farm account, and clicked Next: 9

10 NOTE: The server farm account is used to create and access your configuration database. It also acts as the application pool identity account for the SharePoint Central Administration application pool, and it is the account under which the Microsoft SharePoint Foundation Workflow Timer service runs. The SharePoint Products Configuration Wizard adds this account to the SQL Server Login accounts, the SQL Server dbcreator server role, and the SQL Server securityadmin server role. The user account that you specify as the service account must be a domain user account, but it does not need to be a member of any specific security group on your front-end Web servers or your database servers. Although in my example I am have used an administrator account on this test systems, it is strongly recommended that you follow the principle of least privilege and specify a user account that is not a member of the Administrators group on your front-end Web servers or your database servers. On the Specify Farm Security Settings page, specified type a passphrase, and then clicked Next: NOTE: Although a passphrase is similar to a password, it is usually longer to enhance security. It is used to encrypt credentials of accounts that are registered in Microsoft SharePoint Foundation; for example, the Microsoft SharePoint Foundation system account that you provide when you run the SharePoint Products Configuration Wizard. Ensure that you remember the passphrase, because you must use it each time you add a server to the farm. Ensure that the passphrase meets the following criteria: o Contains at least eight characters o Contains at least three of the following four character groups: o English uppercase characters (from A through Z) o English lowercase characters (from a through z) o Numerals (from 0 through 9) o Nonalphabetic characters (such as!, $, #, %) 10

11 On the Configure SharePoint Central Administration Web Application page, I specified a port number I want to use for my SharePoint Central Administration Web application and Clicked NTLM authentication provider, and clicked Next: On the Completing the SharePoint Products Configuration Wizard page, I reviewed my configuration settings and clicked Next 11

12 The configuration wizard now starts configuring SharePoint, and my configuration completed successfully and I clicked on Finish: NOTE: If the SharePoint Products Configuration Wizard fails, check the PSCDiagnostics log files, which are located on the drive on which SharePoint Foundation is installed, in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\LOGS folder. Setup is now complete and it will launch a web page to run the Farm Configuration Wizard. (To manually run the Farm Configuration Wizard, On the SharePoint Central Administration Web site, on the Configuration Wizards page, click Launch the Farm Configuration Wizard). I got prompted for user credentials when the wizard launches in Internet Explorer, I entered my credentials and added the web server to the Local Intranet sites in IE Security zones. Instructions for how to configure IE settings are provided at On the Help Make SharePoint Better page, I clicked one of the options and then clicked OK. On the Configure your SharePoint farm page, I clicked Start the Wizard button to walk me through the settings using this wizard 12

13 THIS IS AN IMPORTANT STEP IF YOU PLAN TO USE THE EXISTING SHAREPOINT WEB SITE IT CREATES FOR HOSTING RC+EP. In the Service Account section, I created a new service account that is the.net business connector service account as defined in AX, and deselected the two services as I don t want to use them, and clicked Next: 13

14 On the Create Site Collection page, I selected options to create a test Team site just as a way to ensure that SharePoint can host a site successfully, and clicked OK. This creates a web site on port 80 and a site collection in the web site: 14

15 My site creation completes successfully, and I clicked Finish: 15

16 To test the site, ran Internet Explorer and browsed to the URL and it launched my test site successfully: Run the IIS Manager to see the web site and application pools created to host the new web site on port 80: I can use the SharePoint 80 web site now to host my AX 2009 Role Centers and Enterprise Portal, as it is already configured with the correct application pool account. NOTE: See Appendix A on how to change the application pool account using SharePoint 2010 Central Administration. 16

17 Step 3: Patching Microsoft Dynamics AX 2009 Setup files with hotfix KB Next I downloaded the hotfix KB and requested hotfix KB from Microsoft support and extracted its contents (at time of writing hotfix KB was not available on Partnersource). Then I followed through the document Deployment of Microsoft SharePoint 2010 with Microsoft Dynamics AX 2009 SP1.docx that ship with the hotfix. The following is a summary of the steps I followed. This by no means replaces the document that ships as that contains other vital information like what the supported scenarios are etc. The following steps also encompass using fix KB (1) Extracted the hotfix KB to D:\ folder on the EP server. Verified that the file version of the 3 files in the Setup Assemblies folder ("D:\ \Setup Assemblies") is v (2) Copied my Microsoft Dynamics AX 2009 RTM setup files from the DVD to a folder on my D: drive, under D:\AX2009 (3) Patched the setup files with files from the hotfix. Copied the Microsoft.Dynamics.Framework.Deployment.Portal.dll and Microsoft.Dynamics.Framework.Portal.dll files from the Setup Assemblies folder ("D:\ \Setup Assemblies") and pasted them into the AX 2009 setup folder in the following locations and replaced the existing files: D:\AX2009\Msi\Components32\Program Files\Microsoft Dynamics AX\50\Client\Bin D:\AX2009\Msi\Components64\Program Files (x86)\microsoft Dynamics AX\50\Client\Bin (4) Copied the Microsoft.Dynamics.Framework.Deployment.Portal.dll from the Setup Assemblies folder ("D:\ \Setup Assemblies") and pasted them into the following locations and replaced the existing files: D:\AX2009\Msi\Components32\Program Files\Microsoft Dynamics AX\50\Setup D:\AX2009\Msi\Components64\Program Files\Microsoft Dynamics AX\50\Setup (5) Copied the AxSetup.exe file from the Setup Assemblies folder ("D:\ \Setup Assemblies") and pasted it to the following location by replacing the existing files: D:\AX2009\Support 17

18 Step 4: Installing AX 2009 Kernel and Application updates that add compatibility support for Microsoft SharePoint 2010 (6) We need AX 2009 Kernel Build or later deployed on all servers to add compatibility with SharePoint The Kernel hotfix that ships with KB is at build IMPORTANT NOTES: a. If you have however installed the Kernel Rollup Hotfix AX 2009 SP1 Hotfix Rollup 6 and above then you don t need to install this kernel update from KB (Rollup 6 already contains the update and the kernel build for RU6 is ) b. Ensure you install the same kernel build running on the AOS server on to the Enterprise Portal Server (and other servers running AX components and your AX clients) c. Kernel hotfixes ARE cumulative (Application hotfixes aren t) (7) I Installed the Kernel hotfix on all my AX servers by running axupdate.exe from the Kernel folder of the hotfix (D:\ \Kernel). (8) We also need to install AX 2009 Application Hotfix which adds compatibility support for Enterprise Portal running on SharePoint We can deploy the application hotfix that comes bundled with KB , however that application hotfix has now been superseded by KB which also addresses an issue as detailed at (9) I Installed the Application hotfix by running axupdate.exe from the Application folder of the hotfix (D:\ ). (10) Verify the Kernel and Application Build on the AOS server a. Application hotfix is a standalone hotfix and internally versioned at b. However, if you look at the AX Help -> About Microsoft Dynamics AX window it will NOT display this application version as it s a standalone version. Only Service Packs and Hotfix Rollup Application fixes are displayed in the About box. It will however display the current Kernel version as in use by 18

19 the AX client. This is what s displayed from the AX client that I ran from my AOS server: c. Check the AOT -> Classes -> SysManifestHotfix class to see if the application hotfix got deployed. Here is what my class looks like: d. NOTE: See Appendix B for what errors you may get if the correct Kernel and Application hotfixes are not installed 19

20 Step 5: Deploying Microsoft Dynamics AX 2009 Role Centers and Enterprise Portal Now that my AX 2009 setup files are patched and I have installed the kernel and application hotfix , next I ran setup.exe from the patched setup folder and deployed Role Centers and Enterprise Portal (1) Before running setup.exe, I compiled the SysEPDeployment and SysDevelopmentProxy Classes from my AOS server which also has the.net Business Connector installed (This class needs to be compiled from a system that has the.net business connector installed see this link) (2) Ran D:\AX2009\setup.exe, and followed through initial setup screens and selected custom installation type: 20

21 (3) Selected Role Centers and Enterprise Portal and.net Business Connector from Select Components form and clicked Next: (4) Clicked Install prerequisites software button: 21

22 (5) Once the pre-requisites were installed clicked Next: (6) Left the default install folders selected, and clicked Next: 22

23 (7) Selected the.net Business Connector display language, and clicked Next: (8) Specified my AOS servername and the TCP port it is listening on and hit Next: 23

24 (9) Specified my.net Business Connector proxy username password, and hit Next: (10) Selected the SharePoint web site in which I want to create the Enterprise Portal site collection, and hit Next (The selected web site s application pool user account already runs as the.net business connector proxy user account): 24

25 (11) In the Ready to Install page, left the default selection and hit Next: (12) Then waited for the deployment to complete: 25

26 (13) Received a deployment success (14) Verified in the Web Sites form that the web site is registered. Ran AX Client on the AOS server and opened up AX -> Administration -> Setup -> Internet -> Enterprise Portal -> Web Sites (15) Installed the Kernel hotfix on all EP server and ran IISRESET.EXE, to recycle the IIS services. (16) Browsed the Enterprise Portal Site to verify that I can launch it without any errors (17) Followed through the rest of the post installation tasks of Configuring Enterprise Portal and maintaining Role Centers as detailed at (Set up Enterprise Portal and Role Centers) List of Known Issues and Resolutions: For a list of other well-known issues and resolutions when hosting or deploying Microsoft Dynamics AX 2009 Role Centers and Enterprise Portal see

27 Appendix A Configuring Application Pool User Account The following is a sample demonstration describing how to change the Application Pool user account that is currently in use by the SharePoint 80 web site to use the FABRIKAM\AXBCProxy User account: The following steps can be used to change the service account used by the application pool account mapped to any SharePoint Web site from the server hosting the SharePoint Central Administration web site: NOTE: It is recommended that you secure the SharePoint Central Administration web site first using encryption technologies like SSL/TLS, as credentials will be sent in clear text (see for more info) (1) Run SharePoint 2010 Central Administration (2) Click on Security on the left-hand bar, and it displays the following page: 27

28 (3) Under General Security click on Configure managed accounts and it should displays all the managed accounts you have setup: 28

29 (4) Click on the link Register Managed Account to add a new domain user account to be used as your managed application pool account: Click on OK and the new account will be listed: 29

30 (5) Change the SharePoint 80 Web site to use the new managed account. Click on Security on the left-hand bar and then under General Security click on Configure service accounts. It should then display the following form: (6) From the Select one drop-down box, select the Web Application Pool - Sharepoint - 80 and under Select an account for this component, select your new user account. In my case I selected the FABRIKAM\AXBCproxy user account: and clicked OK 30

31 (7) Read and then click OK on the following message that is displayed: Wait for the change to apply, and if successful, the Security form will be shown again: (8) Check in IIS Manager that the new account is setup: (9) Open up an elevated cmd prompt an run IISRESET /noforce on all your servers in the Farm. 31

32 Appendix B Unable to detect the correct version of SharePoint ISSUE: You have patched your Microsoft Dynamics AX 2009 RTM setup files with files from hotfix KB You have successfully installed SharePoint 2010 and can create SharePoint web sites and site collections. However when you try to deploy Role Centers and Enterprise Portal by running setup.exe from your patched setup folder, you get an error in the DynamicsSetupLog.txt and Application Event log stating that you haven t got Windows SharePoint Services installed: DynamicsSetupLog.txt: Dynamics Adapter CreateAxaptaObject failed. Microsoft.Dynamics.Framework.BusinessConnector.Session.Exceptions.XppSessionException at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsSession.HandleException(String message, Exception exception, HandleExceptionCallback callback) at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.CreateAxaptaObject(String classname) at Microsoft.Dynamics.Framework.BusinessConnector.Proxy.ProxyObjectBase..ctor(IAxaptaAdapter axaptaadapter, ProxyClassName classname) at Microsoft.Dynamics.Framework.BusinessConnector.Proxy.SysEPDeployment..ctor(IAxaptaAdapter axaptaadapter) at Microsoft.Dynamics.Framework.Deployment.Portal.EPDeployment.DeployEnterprisePortal(String virtualserverurl) Enterprise Portal cannot be deployed because Windows SharePoint Services is not installed on this computer. Microsoft.Dynamics.BusinessConnectorNet.XppException at Microsoft.Dynamics.BusinessConnectorNet.Axapta.CreateAxaptaObject(String classname, Object[] paramlist) at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.CreateAxaptaObject(String classname) An error occurred during setup of Role Centers and Enterprise Portal. Reason: Dynamics Adapter CreateAxaptaObject failed. Application event log entries: Log Name: Application Source: Dynamics.NET Business Connector 5.0 Event ID: 110 Task Category: None Level: Warning Keywords: Classic User: N/A Description: Microsoft Dynamics AX Business Connector Session 17. An X++ exception has occurred. Enterprise Portal cannot be deployed because Windows SharePoint Services is not installed on this computer and.. 32

33 Log Name: Application Source: Microsoft.Dynamics.Framework.BusinessConnector Event ID: 3000 Task Category: None Level: Warning Keywords: Classic User: N/A Description: Dynamics Adapter CreateAxaptaObject failed. Enterprise Portal cannot be deployed because Windows SharePoint Services is not installed on this computer. Microsoft.Dynamics.BusinessConnectorNet.XppException at Microsoft.Dynamics.BusinessConnectorNet.Axapta.CreateAxaptaObject(String classname, Object[] paramlist) at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.CreateAxaptaObject(String classname) RESOLUTION: This error can occur for two reasons (1) a. Ensure the AX 2009 Setup files are patched correctly with the updated assembly files that ship in the "Setup Assemblies" folder inside hotfix KB (i).copy all the files of the Microsoft Dynamics AX 2009 DVD to a shared network folder (we will refer to this as [SharedFolder] later on). (ii). Extract hotfix KB to an empty folder. The Extracted fix should contain the following folder structure: (iii). Copy the Microsoft.Dynamics.Framework.Deployment.Portal.dll and Microsoft.Dynamics.Framework.Portal.dll files from the "Setup Assemblies" folder in hotfix KB and paste them into the following locations by replacing the existing Microsoft.Dynamics.Framework.Deployment.Portal.dll and Microsoft.Dynamics.Framework.Portal.dll files: [SharedFolder]\Msi\Components32\Program Files\Microsoft Dynamics AX\50\Client\Bin [SharedFolder]\Msi\Components64\Program Files (x86)\microsoft Dynamics AX\50\Client\Bin (iv).copy the Microsoft.Dynamics.Framework.Deployment.Portal.dll from the "Setup Assemblies" folder and paste them into the following locations by replacing the existing Microsoft.Dynamics.Framework.Deployment.Portal.dll file: [SharedFolder]\Msi\Components64\Program Files\Microsoft Dynamics AX\50\Setup [SharedFolder]\Msi\Components32\Program Files\Microsoft Dynamics AX\50\Setup 33

34 (iv).copy the AxSetup.exe file from the "Setup Assemblies" folder and paste the file into the following location by replacing the existing AxSetup.exe file: [SharedFolder]\Support b. As a minimum install Application and Kernel hotfix and/or install AX 2009 SP1 Hotfix Rollup 6 Kernel and Application hotfix to add support for SharePoint (2) The AXSETUP.EXE is in charge of checking all the pre-reqs. It determines the SharePoint version by looking for the Version registry key for SharePoint. If it cannot find the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Version then it will raise a similar error. Verify that the key exists, with a version number value of at least See for more details. 34

35 Appendix C List of Application Pools created by SharePoint Foundation

36 This document is for illustration purposes only. Microsoft disclaims all warranties and conditions with regard to use of the programming example for other purposes. Microsoft shall not, at any time, be liable for any special, direct, indirect or consequential damages, whether in an action of contract, negligence or other action arising out of or in connection with the use or performance of the programming example. Nothing herein should be construed as constituting any kind of warranty. See terms at 36