HP Intelligent Management Center v7.1 SQL Server 2012 Installation and Configuration Guide

HP Intelligent Management Center v7.1 SQL Server 2012 Installation and Configuration Guide Abstract This document describes configuration during and after database installation when IMC is used with Microsoft SQL Server. It is applicable to the SQL Server 2012 Enterprise edition and slightly different from other editions of SQL Server 2012. This document is intended for use by network engineers or system administrators responsible for installing network software and components. HP Part Number: 5998-6610 Published: September 2014 Software Version: IMC PLAT 7.1 (E0302) Edition: 1.0

Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgements SQL Server, Windows, and Windows Server are trademarks of the Microsoft Group of companies.

Contents 1 SQL Server 2012 in IMC...4 2 Preparing for installation...5 Installing.NET Framework 3.5...5 Turning off the Windows firewall...8 3 Installing SQL Server 2012...10 4 Registering the SQL Server license...26 5 Installing the SQL Server client...28 Installation procedure...28 Testing connectivity...35 6 Setting up SQL Server 2012...36 Configuring TCP/IP properties...36 Modifying the maximum server memory for SQL Server...38 Starting the SQL Server Browser service...40 Changing the SQL Server service startup account...41 Restarting the SQL Server service...43 Creating a superuser and granting a privilege to the user...43 7 Uninstalling a SQL Server...47 8 FAQ...49 The default instance of the database is used by another application. How do I install the database using a named instance?...49 Does changing the computer name affect the database? How do I restore the database?...53 During IMC installation, "MS SQLServer is not Installed Correctly, MSSOLSERVER Service Does not Exist" is displayed. How do I solve the problem?...54 During IMC installation, "Database Service MSSQLSERVER Is not Configured to Be Started with Local System" is displayed. How do I resolve the problem?...54 During IMC installation, "The ADO 1.5 Component Is not Found in Current System" is displayed. How do I resolve the problem?...54 During IMC installation, "Provider Cannot Be Found" is displayed. How do I resolve the problem?...54 During IMC installation, the system displays "Failed to run bcp.exe, Database tools not installed or Windows not restarted after MS SQL Server installed." How do I solve the problem?...56 How do I update database passwords for IMC?...57 Why can't I install the SQL server on a Microsoft Gold Standard server?...58 9 Support and other resources...59 Contacting HP...59 Subscription service...59 Related information...59 Documents...59 Websites...59 Typographic conventions...60 Document conventions...60 GUI conventions...60 Symbols...60 10 Documentation feedback...61 Index...62 Contents 3

1 SQL Server 2012 in IMC Before installing IMC, install SQL Server on a database server for storing IMC data, or install it on the server on which you plan to install IMC. When SQL Server installation is complete, restart the operating system, and then install IMC. This document provides installation and configuration information for Microsoft SQL Server 2012. For more information, see IMC Deployment Guide. If you plan to install the database on a separate database server, follow these guidelines: On the IMC server, install a SQL Server client with the same version as the database. Before installing IMC, create a data file folder for storing IMC data on the database server. You must specify the local path to the folder during the deployment of IMC components, as shown in Figure 1. Figure 1 IMC installation: Database Configuration page NOTE: To ensure proper operation of SQL Server, use Microsoft SQL Server licensed installation software. Using localized software or other unauthorized editions might cause a failure in database installation and operation. 4 SQL Server 2012 in IMC

2 Preparing for installation Before installing SQL Server 2012 and SQL Server client, complete the following tasks: Install.NET Framework 3.5 on Windows Server 2008 R2..NET Framework 3.5 is required by SQL Server 2012. By default, it is not installed on Windows Server 2008 R2. Turn off the Windows firewall on the SQL Server host to open TCP port 1443. By default, Microsoft Windows enables the Windows firewall, which closes port 1443 to prevent Internet computers from connecting to a default instance of SQL Server. Installing.NET Framework 3.5 1. From the Start menu or Quick Launch toolbar, select Server Manager. The Server Manager page opens, as shown in Figure 2. Figure 2 Server Manager page 2. Select Features in the navigation tree, and then click Add Features in the right pane. The Add Features Wizard window opens, as shown in Figure 3. Installing.NET Framework 3.5 5

Figure 3 Select Features page 3. Expand the.net Framework 3.5.1 Features option, select.net Framework 3.5.1, and click Next. The Confirm Installation Selections page opens, as shown in Figure 4. Figure 4 Confirm Installation Selections page 4. Click Install. 6 Preparing for installation The Installation Progress page opens, as shown in Figure 5.

Figure 5 Installation Progress page When the installation is complete, the Installation Results page opens, as shown in Figure 6. Figure 6 Installation Results page 5. Click Close. Installing.NET Framework 3.5 7

Turning off the Windows firewall 1. Select Start > Control Panel > System and Security > Windows Firewall. The Windows Firewall page opens. Figure 7 Windows Firewall page 2. Select Turn Windows Firewall on or off. The Customize Settings page opens. 8 Preparing for installation

Figure 8 Customize Settings page 3. Select Turn off Windows Firewall (not recommended) for both Home or work (private) network location settings and Public network location settings, and then click OK. The Windows Firewall page displays the firewall status. Figure 9 Disabling Windows firewall Turning off the Windows firewall 9

3 Installing SQL Server 2012 1. Run the installation program. The SQL Server Installation Center window opens (see Figure 10). Figure 10 SQL Server Installation Center window 2. Select Installation in the navigation tree, and then select New SQL Server stand-alone installation or add features to an existing installation. The Setup Support Rules page opens (see Figure 11). The system runs a check to identify problems that might occur when you install the SQL Server setup support files. 10 Installing SQL Server 2012

Figure 11 Setup Support Rules page 3. When the check is complete, click OK. The Product Key page opens (see Figure 12). Figure 12 Product Key page 11

4. Enter the product key, and then click Next. The License Terms page opens (see Figure 13). Figure 13 License Terms page 5. Select I accept the license terms, and then click Next. The Product Updates page opens (see Figure 14). 12 Installing SQL Server 2012

Figure 14 Product Updates page 6. Clear the Include SQL Server product updates check box, and then click Next. The Install Setup Files page opens (see Figure 15). Figure 15 Install Setup Files page 13

When the setup files are installed successfully, the Setup Support Rules page opens (see Figure 16). The system checks for problems that might occur when you install the SQL Server setup files. Figure 16 Setup Support Rules page 7. When the check is complete, click Next. The Setup Role page opens (see Figure 17). 14 Installing SQL Server 2012

Figure 17 Setup Role page 8. Select SQL Server Feature Installation, and then click Next. The Feature Selection page opens (see Figure 18). 15

Figure 18 Feature Selection page 9. Select the features to install the Shared feature directory path and the Shared feature directory (x86) path (see Figure 18). The Shared feature directory and Shared feature directory (x86) paths are for the shared features. The default settings are C:\Program Files\Microsoft SQL Server and C:\Program Files(x86)\Microsoft SQL Server. To ensure sufficient disk space, specify the paths to other disks. 10. Click Next. The Installation Rules page opens (see Figure 19). The installer checks the installation environments on your computer. 16 Installing SQL Server 2012

Figure 19 Installation Rules page 11. Click Next. The Instance Configuration page opens (see Figure 20). Figure 20 Instance Configuration page 17

12. Select Default instance and use the default instance MSSQLSERVER. Do not modify the default instance ID. You can select Named instance and enter a custom instance ID. For information about how to install SQL Server 2012 using a named instance, see "The default instance of the database is used by another application. How do I install the database using a named instance?." If you use a custom instance, you must enter the custom instance ID in the Instance Name combo box in the Checking Database Connectivity window during IMC installation. 13. Click Next. The Disk Space Requirements page opens (see Figure 21). The system calculates the required disk space for the selected features, and then checks and displays the disk usage results. Figure 21 Disk Space Requirements page 14. Click Next. The Service Accounts tab displays the login accounts for SQL Server services and the service startup type (see Figure 22). 18 Installing SQL Server 2012

Figure 22 Service Accounts tab 15. Use the default settings on the Service Accounts tab. 16. Click the Collation tab. The Collation tab displays the nondefault collations for the database engine (see Figure 23). Figure 23 Collation tab 19

17. Use the default settings. Click Next. The Database Engine Configuration page opens (see Figure 24). Figure 24 Database Engine Configuration page 18. Under Authentication Mode, select Mixed Mode, set the password for user sa, and add a SQL Server administrator (see Figure 25). SQL Server 2012 has password complexity requirements. For more information, see the SQL Server 2012 online help. For IMC to correctly identify the sa logon password during installation, make sure the password does not contain any of the following characters: Left bracket (<) Right bracket (>) Vertical bar ( ) Tab character (\t) If you do not want to change the password of user sa, create a superuser with sa user privileges, and make sure the password does not contain any of these characters. For information about creating a database superuser, see "Creating a superuser and granting a privilege to the user." 20 Installing SQL Server 2012

Figure 25 Specifying SQL Server administrators 19. Use the default settings on the Data Directories tab (see Figure 26) and the FILESTREAM tab (see Figure 27). Figure 26 Data Directories tab 21

Figure 27 FILESTREAM tab 20. Click Next. The Error Reporting page opens (see Figure 28). Figure 28 Error Reporting page 22 Installing SQL Server 2012

21. Use the default settings. Click Next. The Installation Configuration Rules page opens (see Figure 29). Figure 29 Installation Configuration Rules page 22. Click Next. The Ready to Install page opens (see Figure 30). 23

Figure 30 Ready to Install dialog box 23. Click Install. The Installation Progress page displays installation progress (see Figure 31). Figure 31 Installation Progress page 24 Installing SQL Server 2012

24. When the installation is complete, click Next. The Complete page provides a link to the summary log file for the installation and other important notes (see Figure 32). Figure 32 Complete page 25. Click Close and restart the operating system. 25

4 Registering the SQL Server license The SQL Server supports the following license registration modes: Per User licensing Used to register the SQL Server 2012 Developer and Parallel Data Warehouse. Per Processor licensing Used to register the SQL Server Developer and Parallel Data Warehouse. The number of Per Processor licenses is determined by the number of processors on a SQL server. You must buy a Per Processor license for each processor on a server on which the SQL server component is installed. With Per Processor licensing, the number of SQL servers and IMC servers is not relevant. Per Processor licensing is applicable to networks that contain several SQL servers and IMC servers. SQL Server 2008 R2 is used as an example, as shown in Figure 33. Figure 33 Per Processor licensing NOTE: The number of Per Processor licenses is not determined by the number of kernels in a processor. Server/CAL licensing The number of Server/CAL licenses is determined by the number of SQL servers and IMC servers. You must buy a server license for each SQL server and a CAL license for each IMC server. Server/CAL licensing is applicable to networks that contain few SQL servers and IMC servers. SQL Server 2008 R2 is used as an example, as shown in Figure 34. 26 Registering the SQL Server license

Figure 34 Server/CAL licensing Before choosing a license registration mode, determine the IMC deployment environment. If IMC is deployed in centralized mode, buy a CAL license for the IMC server only. If IMC is deployed in distributed mode, buy a CAL license for each IMC server that must access the SQL server. For more information about SQL server license registration, see the Microsoft documentation. NOTE: The license registration modes apply to the Standard and Enterprise editions of SQL Server 2008/2008 R2/2012/2014. You do not need to buy a license for the SQL Server Express edition. 27

5 Installing the SQL Server client Installation procedure If you are installing IMC and the SQL server on different hosts, do the following: Install the SQL Server client on the host where IMC is located. Make sure the client version matches the SQL server version. To install the SQL Server client: 1. Run the SQL Server 2012 installation program. 2. In the Feature Selection page, select the features Management Tools - Basic and SQL Client Connectivity SDK (see Figure 35). For information about displaying the Feature Selection page, see "Registering the SQL Server license." Figure 35 Feature Selection page 3. Click Next. The Installation Rules page opens (see Figure 36). 28 Installing the SQL Server client

Figure 36 Installation Rules page 4. Click Next. The Disk Space Requirements page opens (see Figure 37). The system calculates the required disk space for the selected features, and then checks and displays the disk usage results. Installation procedure 29

Figure 37 Disk Space Requirements page 5. Click Next. The Error Reporting page opens (see Figure 38). 30 Installing the SQL Server client

Figure 38 Error Reporting page 6. Use the default setting. Click Next. The Installation Configuration Rules page opens (see Figure 39). Installation procedure 31

Figure 39 Installation Configuration Rules page 7. Click Next. The Ready to Install page opens (see Figure 40). 32 Installing the SQL Server client

Figure 40 Ready to Install page 8. Confirm the installation information, and then click Install. The Installation Progress page opens (see Figure 41). Installation procedure 33

Figure 41 Installation Progress page When the installation is complete, the Complete page opens (see Figure 42). Figure 42 Complete page 34 Installing the SQL Server client

9. Click Close and restart the operating system. Testing connectivity After the SQL Server client is installed, you can test the connectivity between the client and the SQL server. To test connectivity between the SQL Server client and the SQL server: 1. Select Run from the Start menu, and then enter cmd in the Run dialog box. 2. In the CMD window, enter one of the following commands: For the default instance: osql S 192.168.20.110 U sa P imc123456 For a custom instance: osql S 192.168.20.110\instancename U sa P imc123456 In these commands, 192.168.20.110 is the IP address of the SQL server, sa and imc123456 are the username and password of the default superuser, and instancename represents the name of the custom instance. If the SQL command prompt appears, connect to the SQL server and enter SQL command mode (see Figure 43). Figure 43 Testing connectivity Testing connectivity 35

6 Setting up SQL Server 2012 This chapter discusses the steps and procedures to set up and configure an SQL Server database. Configuring TCP/IP properties 1. Select Start > All Programs > Microsoft SQL Server 2012 > Configuration Tools > SQL Server Configuration Manager, as shown in Figure 44. Figure 44 SQL Server Configuration Manager Figure 45 SQL Server Configuration Manager window 36 Setting up SQL Server 2012

2. On the SQL Server Configuration Manager window: a. Select SQL Server Network Configuration > Protocols for MSSQLSERVER from the navigation tree. b. Double-click TCP/IP on the main pane or select TCP/IP, and then click the Properties icon on the toolbar. The TCP/IP Properties dialog box appears, as shown in Figure 46. Figure 46 Configuring TCP/IP properties 3. On the Protocol tab, make sure Yes is selected for Listen All. 4. Click the IP Address tab and select Yes for the Enabled option of each IP address. 5. Set TCP Port to 1433, as shown in Figure 47. Configuring TCP/IP properties 37

Figure 47 Configuring IP addresses for TCP/IP 6. Click OK to save the configuration. The following message appears: Any changes made will be saved; however, they will not take effect until the service is stopped and restarted. 7. Click OK. 8. Restart the SQL Server to validate the configuration. For more information about the configuration procedure, see "Restarting the SQL Server service." NOTE: Make sure Yes is selected for Listen All on the TCP/IP Properties dialog box. Otherwise, you must enter the dialog box to update the previously-configured IP addresses if the server IP address changes after installing SQL Server 2012. Otherwise, you cannot connect to the database. You can configure the Named Pipes property in the same way TCP/IP Properties is configured. In distributed deployment, make sure you configure all database servers to use the same listening port. Modifying the maximum server memory for SQL Server To ensure the optimum SQL server performance, the maximum server memory is set to 2147483647 MB, so that SQL Server can take advantage of the optimum amount of memory at any given time. When IMC and SQL Server are installed on the same server, to meet the memory requirements of IMC processes, you must control the maximum server memory that SQL Server can use. HP recommends that you set the maximum server memory to half of the server's physical memory. To modify the maximum server memory for SQL Server: 38 Setting up SQL Server 2012

1. Select All programs > Microsoft SQL Server 2012 > SQL Server Management Studio from the Start menu. Figure 48 Database login window 2. Select SQL Server Authentication from the Authentication list. 3. Enter the superuser username sa in the Login field, enter the password, and click Connect. Figure 49 Microsoft SQL Server Management Studio main pane 4. Right-click the server name. 5. Select Properties from the shortcut menu. 6. Select Memory in the navigation tree. Modifying the maximum server memory for SQL Server 39

Figure 50 Setting the maximum server memory 7. Set the value of Maximum server memory to half of the server's physical memory, and click OK. In this example, the server's physical memory is 4096 MB, so the value here is 2048 MB. The maximum server memory for SQL Server has been set. 8. Restart the operating system to validate the modification. Starting the SQL Server Browser service If you set a custom instance for the SQL Server 2012, you must start the SQL Server Browser service, so IMC can connect to the SQL Server database. To start the SQL Server Browser service: 1. Select Start > All Programs > Microsoft SQL Server 2012 > Configuration Tools > SQL Server Configuration Manager. 2. Select SQL Server Services from the navigation tree, right-click SQL Server Browser on the main pane, and then select Properties from the shortcut menu. Figure 51 Launching the SQL Server Browser Properties window 40 Setting up SQL Server 2012

3. Click the Service tab, and then select Automatic for Start Mode. Figure 52 Setting the service start mode to Automatic 4. Click OK. 5. In the SQL Server Configuration Manager window, right-click SQL Server Browser, and then select Start from the shortcut menu. Figure 53 Starting the SQL Server Browser service Changing the SQL Server service startup account When you specify a superuser for IMC to use a remote SQL Server database, the user must have write permissions to all the disks on the database server. To ensure that, you must configure the SQL Server service to start up using the built-in local system account. To configure the SQL Server service to start up using the built-in local system account: 1. On the SQL Server Configuration Manager window, select SQL Server Services from the navigation tree and you can see the operational status of SQL Server services on the right, as shown in Figure 54. Changing the SQL Server service startup account 41

2. Right-click SQL Server (MSSQLSERVER), and then select Properties from the shortcut menu. Figure 54 Operational status of SQL Server services 3. Click the Log On tab. 4. Make sure Local System is selected for the Built-in account list. 5. Click OK. Figure 55 Configuring the startup account 6. Restart the SQL Server (MSSQLSERVER) service on the SQL Server Configuration Manager window to validate the configuration. 42 Setting up SQL Server 2012

Restarting the SQL Server service After you change the startup account for the SQL Server services, the SQL Server services must be restarted for the change to take effect. To restart the SQL Server service: 1. On the SQL Server Configuration Manager window, select SQL Server Services from the navigation tree. 2. Select SQL (MSSQLSERVER) on the right. 3. Click Restart service on the toolbar, as shown in Figure 56. Figure 56 Restart the SQL Server Service NOTE: Alternatively, you can restart the service by rebooting the Windows operating system. Rebooting the operating system is required for installing IMC after the SQL server installation is complete. You do not need to restart the SQL server service separately. Creating a superuser and granting a privilege to the user By default, the superuser sa is used to access the SQL Server database. You can create a superuser and grant the administrator privilege to it. To create a a superuser and grant administrator privileges to the user: Restarting the SQL Server service 43

1. Select Start > All programs > Microsoft SQL Server 2012 > SQL Server Management Studio. The database login window appears, as shown in Figure 57. Figure 57 Login window 2. Select SQL Server Authentication for Authentication, select a login username, enter the password, and click Connect. The Microsoft SQL Server Management Studio main pane appears. 3. Expand the Security node in the navigation tree, right-click Logins, and select New Login from the shortcut menu, as shown in Figure 58. Figure 58 Microsoft SQL Server Management Studio main pane The page for adding a login user appears, as shown in Figure 59. 44 Setting up SQL Server 2012

Figure 59 Add a login user 4. Set the login name, click SQL Server authentication, set the password, and clear the User must change password at next login box. For IMC to correctly identify the password, make sure that the password does not contain any of the following characters: Left bracket (<) Right bracket (>) Vertical bar ( ) Tab (\t) 5. From the navigation tree, select Server Roles and then set the server roles as shown in Figure 60. Creating a superuser and granting a privilege to the user 45

Figure 60 Setting server roles 6. Select sysadmin and click OK. The user is granted database administrator privileges, and appears under the Security > Logins node in the navigation tree of the Microsoft SQL Server Management Studio main pane, as shown in Figure 61. Figure 61 Viewing the new user 46 Setting up SQL Server 2012

7 Uninstalling a SQL Server 1. Select Start > Control Panel > Uninstall or Change a program > Uninstall/Change. 2. Select Microsoft SQL Server 2012 (64-bit), and then click Uninstall. Follow the same procedure to uninstall other programs displayed in the red box (see Figure 62). Figure 62 Uninstalling SQL Server 2012 with the Uninstall/Change function Manually remove the following programs from your host: Microsoft SQL Server 2012 (64-bit) Microsoft SQL Server 2008 R2 Management Objects Microsoft SQL Server 2012 Data-Tier App Framework Microsoft SQL Server 2012 Management Objects Microsoft SQL Server 2012 Management Objects (x64) Microsoft SQL Server 2012 Native Client Microsoft SQL Server 2012 T-SQL Language Service 47

Microsoft SQL Server System CLR Types Microsoft System CLR Types for SQL Server 2012 48 Uninstalling a SQL Server

8 FAQ The default instance of the database is used by another application. How do I install the database using a named instance? The installation procedure is similar to the installation procedure for using the default instance. The following information only describes the differences. For information about other steps, see "Registering the SQL Server license." 1. After the Setup Support Rules check is complete, click Next. The Installation Type page opens. Figure 63 Installation Type page 2. Select New installation or add shared features and click Next. 3. Enter the product key, agree with the license terms, and select the setup role. The Feature Selection page opens. The default instance of the database is used by another application. How do I install the database using a named instance? 49

Figure 64 Feature Selection page 4. Select the features as shown in the figure above, and then click Next. When the rule check has been passed, the Instance Configuration page opens. 50 FAQ

Figure 65 Instance Configuration page 5. Select Named instance and click Next. The Server Configuration page opens. The default instance of the database is used by another application. How do I install the database using a named instance? 51

Figure 66 Server Configuration page 6. Set the account name and click Next. The Database Engine Configuration page opens. 52 FAQ

Figure 67 Database Engine Configuration page 7. Under Authentication Mode, select Mixed Mode, and then enter the password of user sa. The password must not contain the following characters: < > \t. 8. Use the default settings on the Data Directories and FILESTREAM tabs. Click Next. 9. The remaining setup steps are the same as those for the default instance. Does changing the computer name affect the database? How do I restore the database? Changing the name of the computer running SQL Server might cause database operations to fail. Perform the following steps to update the computer name saved in the database. In this example, the old computer name is SERVER_1, and the new computer name is SERVER_2. 1. Open the CMD window and execute the following scripts (the login username is sa, and the password is imcpass): osql -Usa -PiMCpass select @@SERVERNAME go The old computer name, SERVER_1, is displayed in the interface. 2. Execute the following commands to modify the computer name saved in the database: sp_dropserver @server= SERVER_1, @droplogins=null go sp_addserver @server= SERVER_2, @local='local', @duplicate_ok= 'duplicate_ok' go Does changing the computer name affect the database? How do I restore the database? 53

exit The old computer name, SERVER_1, is deleted, and the new computer name, SERVER_2, is added. 3. Restart the SQL Server service in the Windows Service Manager to restore the database. During IMC installation, "MS SQLServer is not Installed Correctly, MSSOLSERVER Service Does not Exist" is displayed. How do I solve the problem? The MSSQLSERVER string is the default instance name of the Microsoft SQL Server. This message indicates that you have selected the default instance, but the instance does not exist. If you do not select the default instance, but you specify the instance name ABC, MSSQL$ABC is displayed. To solve the problem, check the default instance name in the SQL Server Configuration Manager, and specify the correct instance name during IMC installation. During IMC installation, "Database Service MSSQLSERVER Is not Configured to Be Started with Local System" is displayed. How do I resolve the problem? To create the database file for IMC, the MSSQLSERVER service must start with the local system and must have write privileges to any local disk. Otherwise, IMC cannot be installed. For the configuration procedure, see "Changing the SQL Server service startup account." During IMC installation, "The ADO 1.5 Component Is not Found in Current System" is displayed. How do I resolve the problem? IMC uses ADO 1.5 to connect the database. ADO 1.5 is provided by the operating system. This message indicates that ADO 1.5 is corrupted. To solve the problem, reinstall ADO on the host. During IMC installation, "Provider Cannot Be Found" is displayed. How do I resolve the problem? This message indicates that MDAC is not installed on the server, or that the MDAC installation is corrupted. MDAC corruption typically occurs when application programs attempt to install a partial version of MDAC. To solve the problem: 1. Download the installation program mdac_typ.exe from the Microsoft website, and then reinstall MDAC. 2. If the MDAC installation fails, perform the following steps: a. In Windows Explorer, open the C:\WINDOWS\inf folder. NOTE: This folder might be hidden. b. Right-click the mdac.inf file and select Install. You can select files from the Service Pack CD-ROM or the current operating system. To select files from the Service Pack CD-ROM, locate the i386 directory from the CD-ROM drive. For example, if the CD-ROM drive is D:, select the directory D:\ i386. To select files from the current operating system, click Browse, select a file, and click Retry. 54 FAQ

c. Files to be located during installation follow: File name: adcjavas.inc Location: C:\Program Files\Common Files\System\msadc File name: adojavas.inc Location: C:\Program Files\Common Files\System\ado File name: msdadc.dll Location: C:\Program Files\Common Files\System\ole db File name: dao360.dll Location: C:\Program Files\Common Files\Microsoft shared\dao File name: handler.reg Location: C:\Program Files\Common Files\System\msadc File name: oledbjvs.inc Location: C:\Program Files\Common Files\System\ole db File name: MDACRdMe.htm Location: If you cannot locate this file, change the name of the file MDACReadme.htm to MDACRdMe.htm. d. When the installation is complete, reboot the operating system. NOTE: The MDAC installation is successful if no error message is displayed. 3. If the problem persists, use the MDAC Component Checker to identify MDAC installation problems. a. Download the MDAC Component Checker cc_pkg.exe from the Microsoft website. b. Decompress the file to the C:\ComponentChecker directory. c. In the Component Checker window, select the first option, and then click OK. Figure 68 Component Checker window After performing the analysis, mismatch information is displayed under File Details. This information indicates potential problems with the MDAC installation. During IMC installation, "Provider Cannot Be Found" is displayed. How do I resolve the problem? 55

Figure 69 Viewing Mismatch information under the File Details node d. Click MISMATCH and view the files in the main pane. These file versions are different from the MDAC version. The Mismatch Field column displays expected file versions. The File Version column displays actual file versions. e. If the version mismatch information cannot be resolved through MDAC installation, copy files to the corresponding directories. i. Locate the mdacxpak.cab file from the decompressed file mdac_typ.exe. Use WinZip to decompress the mdacxpak.cab file, which contains most of the important MDAC files. ii. Copy the decompressed files to the corresponding paths displayed in MISMATCH. f. Reboot the operating system. 4. If you still cannot solve the problem, reinstall the operating system and databases, or contact Technical Support. During IMC installation, the system displays "Failed to run bcp.exe, Database tools not installed or Windows not restarted after MS SQL Server installed." How do I solve the problem? For IMC to access a remote database server using the bcp.exe tool, make sure the Client Tools Connectivity feature is installed on the IMC server. If the Client Tools Connectivity feature is not installed: 1. Run the SQL Server 2012 installation program. 2. Select Client Tools Connectivity on the Feature Selection page. 56 FAQ

Figure 70 Feature Selection page 3. Restart Windows to make the client software bcp.exe take effect after the Client Tools Connectivity feature is installed. How do I update database passwords for IMC? The usernames and passwords used by IMC components are stored in ciphertext in the file \common\conf\server-addr.xml in the installation path. Use the pwdmgr.bat command to obtain plain text passwords or update the latest passwords to the file. Typically, you use the database management tool to change the database password of an IMC component. To ensure communication between IMC and the database, use the pwdmgr.bat command to update the corresponding password in the file server-addr.xml. If IMC is deployed in distributed mode, you must update the password for every IMC server. How do I update database passwords for IMC? 57

Figure 71 Updating database passwords for IMC In this example, 192.168.20.107 is the IP address of the database. To obtain the IP address and name of a SQL Server database, view the settings of the corresponding user in the file $IMCROOT/common/conf/server-addr.xml. The dbpassword string represents the latest database password of the imc_config user. The config_db string represents the database name. Why can't I install the SQL server on a Microsoft Gold Standard server? To install the SQL server on a Microsoft Gold Standard server, make sure you are a system user with the proper privileges to install the SQL server. Table 1 User privileges Local policy object display name Backup files and directories Debug programs Manage auditing and security log User privilege SeBackupPrivilege SeDebugPrivilege SeSecurityPrivilege 58 FAQ

9 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Technical support registration number (if applicable) Product serial numbers Product model names and number Product identification number Applicable error message Add-on boards or hardware Third-party hardware or software Operating system type and revision level Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/wwalerts After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources. Related information Documents Websites To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section and select a networking category. For a complete list of acronyms and their definitions, see HP FlexNetwork Technology Acronyms. HP.com: http://www.hp.com HP Networking: http://www.hp.com/go/networking HP manuals: http://www.hp.com/support/manuals HP download drivers and software: http://www.hp.com/support/downloads HP software depot: http://www.software.hp.com HP Education: http://www.hp.com/learn Contacting HP 59

Typographic conventions This section describes the conventions used in this documentation set. Document conventions Table 2 Document conventions Convention Blue text: Table 2 (page 60) Blue, underlined text: http://www.hp.com Description Cross-reference links and email addresses Website addresses Bold text Keys that are pressed Text typed into a GUI element, such as a box GUI elements that are clicked or selected, such as menu and list items, buttons, tabs, and check boxes Italic text Text emphasis Monospace text File and directory names System output Code Commands, their arguments, and argument values Monospace, italic text Code variables Command variables Monospace, bold text Emphasized monospace text GUI conventions Table 3 GUI conventions Convention Boldface > Description Window names, button names, field names, and menu items are in bold text. For example, the New User window appears; click OK. Multi-level menus are separated by angle brackets. For example, File > Create > Folder. Symbols NOTE: An alert that contains additional or supplementary information. 60 Support and other resources

10 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback. 61

Index Symbols.NET Framework 3.5 installation, 5 A account SQL Server service startup account, 41 B browser SQL Server Browser service start, 40 C changing SQL Server service startup account, 41 client SQL Server, 4 SQL Server client installation, 28 SQL Server client./server connectivity, 35 configuring SQL Server TCP/IP properties, 36 contacting HP, 59 creating superuser, 43 D database SQL Server, 4 documentation, providing feedback on, 61 F FAQ ADO 1.5 corruption, 54 connectivity troubleshooting, 56 database restoration, 53 IMC database password update, 57 MDAC troubleshooting, 54 MSSQLSERVER configuration, 54 MSSQLSERVER default, 54 named instance database installation, 49 SQL Server on Microsoft Gold Standard server installation, 58 firewall Windows firewall turn off, 8 G granting user privilege, 43 GUI conventions (HP), 60 H hardware SQL Server, 4 SQL Server Browser service start, 40 SQL Server client installation, 28 SQL Server client./server connectivity, 35 SQL Server installation, 10 SQL Server license registration, 26 SQL Server memory max modification, 38 SQL Server service restart, 43 SQL Server service startup account, 41 SQL Server TCP/IP properties, 36 HP contacts for support, 59 documentation, 59 GUI conventions, 60 subscription service, 59 support websites, 59 symbols, 60 typographic conventions, 60 I IMC SQL Server, 4 SQL Server Browser service start, 40 SQL Server client installation, 28 SQL Server client./server connectivity, 35 SQL Server installation, 10 SQL Server license registration, 26 SQL Server memory max modification, 38 SQL Server service restart, 43 SQL Server service startup account, 41 SQL Server TCP/IP properties, 36 SQL Server uninstallation, 47 superuser creation, 43 user privilege, 43 installing.net Framework 3.5, 5 SQL Server, 5, 10 SQL Server client, 28 SQL Server uninstallation, 47 IP SQL Server TCP/IP properties, 36 L license SQL Server license registration, 26 M memory SQL Server memory max modification, 38 modifying SQL Server memory max, 38 P privilege user privilege, 43 procedure changing SQL Server service startup account, 41 configuring SQL Server TCP/IP properties, 36 62 Index

creating superuser, 43 granting user privilege, 43 installing NET Framework 3.5, 5 installing SQL Server, 10 installing SQL Server client, 28 modifying SQL Server memory max, 38 registering SQL Server license, 26 restarting SQL Server service, 43 starting SQL Server Browser service, 40 testing SQL Server client./server connectivity, 35 turning off Windows firewall, 8 uninstalling SQL Server, 47 product documentation (HP), 59 R registering SQL Server license, 26 restarting SQL Server service, 43 S server NET Framework 3.5 installation, 5 SQL Server, 4 SQL Server Browser service start, 40 SQL Server client installation, 28 SQL Server client./server connectivity, 35 SQL Server license registration, 26 SQL Server memory max modification, 38 SQL Server service restart, 43 SQL Server service startup account, 41 SQL Server TCP/IP properties, 36 superuser creation, 43 user privilege, 43 service SQL Server Browser service start, 40 SQL Server service restart, 43 SQL Server service startup account, 41 SQL Server ADO 1.5 corruption, 54 Browser service start, 40 client installation, 28 client./server connectivity, 35 connectivity troubleshooting, 56 database restoration, 53 IMC database password update, 57 IMC installation, 4 installation, 5, 10 license registration, 26 MDAC troubleshooting, 54 memory max modification, 38 Microsoft Gold Standard server installation, 58 MSSQLSERVER configuration, 54 MSSQLSERVER default, 54 named instance database installation, 49 NET Framework 3.5 installation, 5 restart, 43 service startup account, 41 superuser creation, 43 TCP/IP properties, 36 uninstallation, 47 user privilege, 43 Windows firewall turn off, 8 starting SQL Server Browser service, 40 starting up SQL Server service startup account, 41 storage SQL Server memory max modification, 38 subscription service (HP), 59 symbols (HP), 60 T TCP/IP SQL Server TCP/IP properties, 36 testing SQL Server client./server connectivity, 35 turning off Windows firewall, 8 typographic conventions (HP), 60 U uninstalling SQL Server, 47 user privilege, 43 superuser creation, 43 W websites (HP), 59 Windows firewall turn off, 8 63