TN Installing PV4E 6.0 under Windows Server 2008 (R2) (3264 Bit) and Remote DB Support

Transcription

1 TN Installing PV4E 6.0 under Windows Server 2008 (R2) (3264 Bit) and Remote DB Support Issue Date: Revision Date: Product (configuration) CenterMind PV4E PV4E 6.0 PV4E 6.0 SP1 Site Wiz Report Center Paladin Dashboard CAD Site Pro PVMAX SQL Windows Server Bit Windows Server 2008 R2 64Bit Affected Items: Publications Software Hardware Firmware Spare Parts Implementation: On request Method of Implementation: Server and Data Base Configuration Estimated Time: 60 Minutes Table of Contents This Technical note includes the following sections: 1. Symptoms and Cause 2. Prerequisites for Installation 3. Installation Procedures\Work-around 4. Post Installation Page 1 of 23

2 1. Symptoms and Cause When installing PV4E 6.0 on Windows Server 2008 you encounter one of the following issues: PV4E Setup show message about FTP/SMTP/MSMQ that need to be installed. After installation the PV4E Services are not working and CmsLogView crashes. After installation the PV4E license manager service is failed to start. The IIM Service takes a lot of memory and stuck. The Active I feature is not working. Can t work with remote DB. Can t use SitePro. Cause There are several things that have been changed in the Windows Server 2008 operating system version which require special care when installing PV4E 6.0. Fix The following steps describe how to install PV4E 6.0 on Windows Server Please follow all these steps to insure proper PV4E 6.0 installation. 2. Prerequisites for Installation Before installing PV4E First need to insure that the following windows components are installed: IIS 7 (with IIS 6 Management Compatibility + FTP server) MSMQ SMTP Server Installing IIS 7 (with IIS 6 Management Compatibility + FTP server) Open the "Server Manager" window (right click on Computer >Manage) Choose "Roles" and click on "Add Roles" hyper link. Make sure that all the required features are checked as in the following images: Page 2 of 23

3 Select Role services Page 3 of 23

4 Select Role services - continue If some of the features are not checked, checked them and click next to install them. Page 4 of 23

5 Installing MSMQ, SMTP Server and.net Framework 3.0 Features Open the "Server Manager" window (right click on Computer >Manage) Choose "Features" and click on "Add Features" hyper link. Make sure that all the required features are checked as in the following image: Select Features If the features "Message Queuing Server" and/or "SMTP Server" are not checked, please check them. Page 5 of 23

6 Select Features - continue Check the.net Framework 3.0 features as in the above image. After you checked all required features, click next to install them. Make sure FTP server is running After installation of IIS, we need to make sure that the FTP service "Startup Type" is set to "Automatic" and that the server is running. At "Server Manager" window click on "Configuration" to expand, then click on "Services". Search for the service "FTP Publishing Services". Make sure that its Startup type is set to "Automatic" and its status is "Started". Page 6 of 23

7 Workaround for FTP checking The PV4E setup searches for the registry key "MSFTPSVC" to check if FTP server exists. The key located at: HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\ServiceProvider\ServiceTypes\MSFTPSVC This registry key not exists in Windows Server Even after installing the FTP server. The workaround is to insert this key manually using "regedit", then the setup will run ok. Turn off UAC In order the PV4E installation to install correctly and the PV4E server to operate ok, the UAC must be turned off. Please follow the steps to turn off the UAC: For Window Server 2008: 1. Click Start, and then click Control Panel. 2. In Control Panel, click User Accounts. 3. In the User Accounts window, click User Accounts. 4. In the User Accounts tasks window, click Turn User Account Control on or off. 5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue. 6. Clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK. 7. Click Restart Now to apply the change right away. UAC settings in Windows Server 2008 Page 7 of 23

8 For Windows Server 2008 R2: 1. Click Start, and then click Control Panel. 2. In Control Panel, click System and Security. 3. In the System and Security window, click Action Center. 4. In the User Accounts tasks window, click Change User Account Control Settings. 5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue. 6. Move the slider to Never Notify and then click OK. 7. Restart the System to apply the changes UAC settings in Windows Server 2008 R2 Page 8 of 23

9 3. Installation Procedures\Work-around Installing SQL server Windows Server 2008 does not support MS-SQL 2000 and requires MS-SQL 2005/2008. If SQL2005 is to be used, SQL2005 SP2 must also be installed to support Win2008. After SP2 installation, "SQL user provisioning tool" must also be applied. It launches automatically when the SP2 installation has finished, but it may not finish successfully. If so it can be accessed through the- "SQL surface area configuration->add new administrator Page 9 of 23

10 Installing PV4E At this point, assuming SQL Server is already installed, we can start install PV4E. Start the PV4E installation process and wait until installation has finished and ask if you want to restart your computer. Choose Don't restart and check the following before restarting: Fix FLEXlm registry values Open regedit and search for the following key: HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager Make sure that the following registry values are exist in this key: RIT_LICENSE_FILE <PV4E RootDir>\Server\Bin\PV4E.lic Rlicense_LICENSE_FILE <PV4E RootDir>\Server\Bin\PV4E.lic If not, add them manually. These values are required by the PV4E License Manager Service to operate right. FLEXlm registry values validation Page 10 of 23

11 Check Performance Counters Another thing to do before restarting is to check the Performance Counters settings. Open the Application log at Event Viewer (Server Manager -> Diagnostics -> Event Viewer -> Windows Log -> Application) Search for the following events: Event ID: 3011 Source: LoadPerf Description: Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. Event ID: 3012 Source: LoadPerf Description: The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. Page 11 of 23

12 Application log with events 3011 and 3012 In case above events are exist in the Application log do the following: Open Command Prompt using right-click and "Run as Administrator" Type the following and press enter: lodctr /R Page 12 of 23

13 If you don't run as administrator you will get "Error: Unable to rebuild performance counter setting from system backup store, error code is 5" The command will fix the Performance Counter settings in the system. This operation is required for the IIM service to work right. Technical notation: There are several processes running by IIM service that are using "Performance Counters". When the IIMAppServer.exe is running it calls to the function: System.Diagnostics.Process.GetProcessesByName(processName) at project PV4EAppManager in function AppManager.KillAllHostProcess(ArrayList processfilenamelist) This function is using Performance Counters. Also the Enterprise Library logging and exception handling (which used by the Dashboard processes) is using the Performance Counters. Restarting Now restart the computer and wait for the Sanity Analyzer process to complete. Page 13 of 23

14 4. Post Installation After installing PV4E Before opening PV4E, we need to add additional permission required in Windows Server 2008 to the CmsServ component at DCOM and to the BootLoader directory. CmsServ additional permissions Steps to add the required permission to CmsServ: 1. Open Component Services window (Run -> dcomcnfg) 2. Go to "DCOM Config" and search for CmsServ. 3. Open CmsServ properties and go to the Security tab. 4. Edit the "Launch and Activation Permissions". 5. Add groups IUSR and NETWORK SERVICE and give them all available permissions. 6. Press OK to save your settings. Page 14 of 23

15 CmsServ Launch and Activation permissions BootLoader directory additional permissions Steps to add the required permission to BootLoader directory: 1. Browse to the PV4E folder, typically at: C:\Program Files\RiT Technologies\PatchView for the Enterprise 2. Right click on BootLoader folder and click on Properties 3. Go to the Security tab and click on Edit button. 4. Add group IUSR and give it Full Control permission. 5. Press OK to save your settings. Page 15 of 23

16 The BootLoader directory is used as FTP directory for the Software Upgrade operation. Add permission to IUSR group for BootLoader directory Upload directory additional permissions (for ActiveI) Please use the same method above and apply Full Control permissions for the groups IUSR and NETWORK SERVICE to the Upload directory which is under: C:\Program Files\RiT Technologies\PatchView for the Enterprise\Presentation Page 16 of 23

17 IIS additional permissions (for ActiveI) In order the ActiveI feature of PV4E to work correctly, additional settings need to be added to the IIS. Please do the following steps to add the required permission to the IIS: 1. Open the Server Manager window (Right click on Computer icon -> Manage) 2. Expand the Roles node and click on Web Server (IIS) 3. Go to Application Pools, right click on DefaultAppPool and choose Advanced Settings option. 4. For 64-Bit machine: At Advanced Settings window, set the option Enable 32-Bit Applications to True. 5. Set the value of Identity property to NetworkService. 6. Press OK to save your settings. DefaultAppPool location in IIS Page 17 of 23

18 DefaultAppPool - Advanced Settings Page 18 of 23

19 Setting Application Pool Identity Working with SitePro Since Windows Server 2008 comes with built-in firewall program, we should configure it to open the SitePro TCP port (default port value is as in ssettingproperties table in DB). The other option is to shutdown the windows firewall. After setting this configuration working with SitePro should be enabled. If you encounter more issues regarding PV4E functionality under Windows Server 2008, and you know how to overcome those issues, please don't hesitate to add this information into this document and redistribute it. Working with Remote Database First of all, when working with remote DB, we need to make sure that the SQL Server at the remote machine is configured to work as a remote DB server. Setting SQL Server to work remotely In the Sql Server Configuration Manager tool, check that the service SQL Server Browser is running and the TCP/IP protocol is enabled under SQL Server Network Configuration. Page 19 of 23

20 Enable the TCP/IP protocol in Configuration Manager Also at the Microsoft SQL Server Management Studio check that the checkbox Allow remote connections to this server is checked under server properties window (right click on server -> Properties, at Connections page). Page 20 of 23

21 Allow remote connections at Server properties Setting Window Firewall to work with SQL Server At the Windows Firewall, go to Exceptions and add access to application sqlserver.exe to enable communication from outside. Setting Network DTC Access In order the PV4E Server to work with remote DB, we need to enable the DTC to work with remote clients. Please do the following steps in the PV4E Server local machine: 1. Click Start, and then click Run. Page 21 of 23

22 2. Type dcomcnfg and press Enter. 3. At the Component Services window go to Local DTC, right click -> Properties. 4. Go to Security tab and set the Security Settings as in the following image: DTC Security Settings Please apply these DTC settings also at the remote DB machine in the same way. Stop the PV4E Services and change the PV4E settings to work with the remote DB. Start the PV4E Services. Set the Windows Firewall to work with MS DTC Please do the following Firewall settings both in local and remote machines: 1. Open Windows Firewall. To open Windows Firewall, on the Start menu, click Control Panel. In Control Panel, do one of the following: a. Under Security, click Allow a program through Windows Firewall. b. If Control Panel is in Classic view, click Windows Firewall. Page 22 of 23

23 2. On the Exceptions tab, select the Distributed Transaction Coordinator check box. 3. Click OK If the PV4E succeed to login but doesn t let the user to create new locations or any operation which requires DB write access, please turn off the Windows Firewall both at the local and remote machines and check again. For more information about how to enable DTC to work through firewall please look at the following link: Report source LAB Resolver Shalom Amar Known issues PBX import is not working (due to LAB testing). Importation feature is not working (due to LAB testing). Additional query words: Windows Server 2008, PV4E Setup, Services, ActiveI, Remote DB. Send feedback to RiT Page 23 of 23