Installation and Configuration Guide

Transcription

1 v7.0 HP Intelligent Management Center SQL Server 2008 Installation and Configuration Guide Abstract This document describes the configuration during and after database installation when IMC is used together with Microsoft SQL Server. The document is applicable to the SQL Server 2008 SP3 Enterprise edition and slightly different from the prior editions. This document is intended for use by network engineers or system administrators responsible for installing network software and components. HP Part Number: Software Version: IMC PLAT 7.0 (E0202) Published: March 2014 Edition: 1.1

2 Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. 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.

3 Contents 1 SQL Server 2008 in IMC Installing SQL Server Installation procedure Registering the SQL server license Installing the SQL Server client...22 Installation procedure...22 Testing connectivity Setting up SQL Server Configuring TCP/IP properties...28 Modifying the maximum server memory for SQL Server...31 Starting the SQL Server Browser service...33 Configuring SQL Server service to Log on as local system (Optional)...35 Restarting the SQL Server service...36 Creating a super user and granting a privilege to the user Uninstalling an SQL Server database FAQs...42 When the default instance of database has been used by other application, how to install the database using named instance?...42 Does changing the computer name affect the database? How to restore the database?...45 During the IMC installation, "MS SQLServer is not Installed Correctly, MSSOLSERVER Service Does not Exist" is displayed. What shall I do?...46 During the IMC installation, "Database Service MSSQLSERVER Is not Configured to Be Started with Local System" is displayed. What shall I do?...46 During the IMC installation, "The ADO1.5 Component Is not Found in Current System" is displayed. What shall I do?...47 During the IMC installation, "Provider Cannot Be Found" is displayed. What shall I do?...47 During the IMC installation, the system displays "Failed to run bcp.exe, Database tools not installed or Windows not restarted after MS SQL Server installed". How to solve this problem?...50 How can I update database passwords for IMC? Support and other resources...52 Contacting HP...52 Subscription service...52 Related information...52 Documents...52 Websites...52 Typographic conventions...52 Document conventions...53 GUI conventions...53 Symbols...53 Index...54 Contents 3

4 1 SQL Server 2008 in IMC Before installing IMC, first install SQL Server on a database server for storing IMC data, or on the same server on which you want to install IMC. After SQL Server installation is complete, restart the operating system before you proceed to install IMC. This document describes the installation procedure and configuration guide for Microsoft SQL Server For more information, see the IMC Deployment Guide. To install the database on a separate database server, follow these guidelines: On the IMC server, install an SQL Server client with the same version as the database. Create a data file folder for storing IMC data on the database server before you start the installation. You are required to input the local path to the folder during the deployment of IMC components, as shown in Figure 1. Figure 1 IMC installation-database Configuration NOTE: To ensure proper operation of SQL Server, use licensed installation software of Microsoft SQL Server. Using the localized software or other unauthorized editions may cause a failure in database installation and operation. SQL Server 2008 cannot be installed on Windows 2008 R2. 4 SQL Server 2008 in IMC

5 2 Installing SQL Server 2008 Installation procedure To install SQL Server 2008: 1. Run the installation program. The SQL Server Installation Center window appears, as shown in Figure 2. Figure 2 SQL Server Installation Center window 2. Select Installation from the navigation tree, and then click New SQL Server stand-alone installation or add features to an existing installation. The Product Key page appears, as shown in Figure 3. Installation procedure 5

6 Figure 3 Product Key page 3. Enter the product key and click Next. The License Terms page appears, as shown in Figure 4. Figure 4 License Terms page 6 Installing SQL Server 2008

7 4. Select I accept the license terms and click Next. The Setup Support Files page appears, as shown in Figure 5. Figure 5 Setup Support Files page 5. Click Install to start installing setup support files. The Setup Support Files installation process page appears, as shown in Figure 6. Installation procedure 7

8 Figure 6 Setup Support Files operation process 6. Upon completion of the installation, the Setup Support Rules dialog box appears, as shown in Figure 7. Figure 7 Setup Support Rules page 8 Installing SQL Server 2008

9 7. Click Next. The Feature Selection page appears, as shown in Figure 8. Figure 8 Feature Selection page 8. Select the features shown in the above figure, and then click Next. The Instance Configuration page appears, as shown in Figure 9. Installation procedure 9

10 Figure 9 Instance Configuration page Select Default instance and use the default instance MSSQLSERVER. Do not modify the default instance ID. HP recommends you also set the default instance for the SQL Server 2008 Express edition, even though the Named instance option is selected by default. An advanced user can select Name instance and then enter a custom instance ID. The user must enter the instance ID in the Instance Name combo box in the Checking Database Connectivity window during IMC installation. If you set a custom instance ID for the SQL Server 2008 Express edition, start the SQL Server Browser service after the installation. For more information, see "Starting the SQL Server Browser service." 9. Click Next. The Disk Space Requirements page appears, as shown in Figure 10. The system calculates the required disk space for the selected features, and then checks and displays the disk usage results. 10 Installing SQL Server 2008

11 Figure 10 Disk Space Requirements page 10. Click Next. The Server Configuration appears as shown in Figure 11. Figure 11 Service Configuration page Installation procedure 11

12 Click Use the same account for all SQL Server services to set a service account. Select account NT AUTHORITY\SYSTEM, as shown in Figure 12. Figure 12 Use the same account for all SQL Server 2008 services dialog box Set the account for starting the SQL Server service. Then click OK to go back to the server configuration dialog box, as shown in Figure 13. Figure 13 Server Configuration page Click Collation, as shown in Figure Installing SQL Server 2008

13 Figure 14 Collation tab page 11. Without any configuration on the Collation tab page, click Next. The Database Engine Configuration page appears, as shown in Figure 15. Figure 15 Database Engine Configuration page Installation procedure 13

14 12. In the Authentication Mode area, select Mixed Mode, set the password for user sa, and add an SQL Server administrator, as shown in Figure 16. SQL Server 2008 has password complexity requirements. For more information, see the online help of SQL Server 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 ( ) \t If you do not want to change the password of the sa user, create a super user with sa user privileges and make sure the password does not contain any of the previous characters. For more information about creating a database super user, see Creating a super user and granting a privilege to the user. Figure 16 Specifying SQL Server administrators page 13. Use the default settings of the Data Directories tab (see Figure 17) and the FILESTREAM tab (see Figure 18). 14 Installing SQL Server 2008

15 Figure 17 Data Directories tab page Figure 18 FILESTREAM tab page 14. Click Next. The Error and Usage Reporting page appears, as shown in Figure 19. Installation procedure 15

16 Figure 19 Error and Usage Reporting page 15. Use the default settings and click Next. The Installation Rules page appears, as shown in Figure 20. Figure 20 Installation Rules page 16 Installing SQL Server 2008

17 16. Click Next. The Ready to Install page shows a tree view of installation options, as shown in Figure 21. Figure 21 Ready to Install page 17. Click Install. The Installation Progress page displays the installation progress, as shown in Figure 22. Installation procedure 17

18 Figure 22 Installation Progress page The components installed are relevant to the features selected previously. Figure 23 shows the setup operation complete. Figure 23 Setup operation completion 18 Installing SQL Server 2008

19 18. Upon completion of the installation, click Next. The Complete page appears, as shown in Figure 24. Figure 24 Complete page 19. Click Close. Installation procedure 19

20 3 Registering the SQL server license The SQL server supports the following license registration modes: Per User licensing Used for registering the SQL Server 2012 Developer and Parallel Data Warehouse. Per Processor licensing The number of Per Processor licenses is counted by the number of processors on an SQL server. The Per Processor is used for registering the SQL Server Developer and Parallel Data Warehouse. You must buy a Per Processor license for each processor on a server installed with the SQL server component. The Per Processor registration mode is irrelevant to the number of SQL servers and IMC servers, and is applicable to the networks containing a lot of SQL servers and IMC servers. See Figure 25. Figure 25 Per Processor Licensing NOTE: The number of the Per Processor licenses is irrelevant to the number of kernels in a processor. Server/CAL licensing The number of Server/CAL licenses is counted 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. The Server/CAL registration mode is applicable to the networks containing a few SQL servers and IMC servers. See Figure Registering the SQL server license

21 Figure 26 Server/Client Access Licensing Before you choose a registration mode, determine the IMC deployment environment: When IMC is deployed in centralized mode, buy a CAL license for only the IMC server. When IMC is deployed in distributed mode, buy a CAL license for each IMC server that needs to access the SQL Server. For more information about SQL Server license registration, see official Microsoft documents. NOTE: The application of the license registration modes is for SQL Server 2005/2008/2008 R2/2012 of standard and enterprise editions. You do not need to buy a license for the SQL Server Express edition. 21

22 4 Installing the SQL Server client Installation procedure If you install IMC and the SQL server on different hosts, install the SQL Server client on the host where IMC is located, and make sure the client version matches the SQL server version. To install the SQL Server client: 1. On the Feature Selection dialog box, select client components, as shown in Figure 27. See Installing SQL Server 2008 for how to enter the Feature Selection dialog box. Figure 27 Feature Selection dialog box 2. Select the features (Management Tools Basic and SQL Client Connectivity SDK) shown in the above figure, and then click Next to enter the Disk Space Requirements dialog box, as shown in Figure Installing the SQL Server client

23 Figure 28 Disk Space Requirements dialog box 3. Click Next to enter the Error and Usage Reporting dialog box, as shown in Figure 29. Figure 29 Error and Usage Reporting dialog box Installation procedure 23

24 4. Without any configuration, click Next to enter the Installation Rules dialog box, as shown in Figure 30. Figure 30 Installation Rules dialog box 5. Click Next to enter the Ready to Install dialog box, shown in Figure Installing the SQL Server client

25 Figure 31 Ready to Install dialog box 6. Click Install to enter the Installation Progress dialog box, as shown in Figure 32. Figure 32 Installation Progress dialog box Installation procedure 25

26 7. The components installed are relevant to the features selected previously. When the installation process is complete the setup operation completion dialog box appears, as shown in Figure 33. Figure 33 Setup operation completion 8. Upon completion of the installation, click Next to enter the Complete dialog box, as shown in Figure Installing the SQL Server client

27 Figure 34 Complete dialog box 9. Click Close to close the Complete dialog box. Testing connectivity After the SQL Server client is installed, you can verify whether or not it can connect to the SQL server. To test the 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 either command: For the default instance: osql h Usa PiMC123 For a custom instance: osql h \instancename Usa PiMC123 In the previous commands, is the IP address of the SQL server, sa and imc123 are the username and password of the default superuser, and instancename represents the name of the custom instance. If the SQL command prompt appears, as shown in Figure 35, you successfully connect to the SQL server and enter the SQL command mode. Figure 35 Testing connectivity Testing connectivity 27

28 5 Setting up SQL Server 2008 This chapter discusses the steps and procedures to setup and configure an SQL Server database. Configuring TCP/IP properties To configure TCP/IP properties: 1. Select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager, as shown in Figure 36. The SQL Server Configuration Manager dialog box appears as shown in Figure 37. Figure 36 SQL Server Configuration Manager Figure 37 SQL Server Configuration Manager window 2. In the SQL Server Configuration Manager window, click SQL Server Network Configuration. If the database has only one instance, only one protocol item exists in the red frame. In this case, go to step 3. If the database has multiple instances, because different instances must use different listening ports, you must check the listening port used by each instance to avoid conflicts. On the SQL Server Configuration Manager window, follow these steps to check the listening ports of instances: a. Select SQL Server Network Configuration > Protocols for MSSQLSERVER from the navigation tree. 28 Setting up SQL Server 2008

29 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. Figure 38 SQL Server Configuration Manager window c. On the IP Addresses tab, you can view the listening port used by the instance. The instance uses TCP port 1433, as shown in Figure 39. Figure 39 Configure TCP/IP properties Configuring TCP/IP properties 29

30 d. Repeat Step a-c to view the listening ports used by existing instances. 3. Configure the TCP/IP attributes for the newly added instance. Select SQL Server Network Configuration > Protocols for IMCMILP from the navigation tree. 4. Double-click TCP/IP on the right (or click TCP/IP and then click the Properties button on the toolbar). The TCP/IP Properties dialog box appears. Figure 40 Configure TCP/IP properties 5. On the Protocol tab, make sure Yes is selected for Listen All. 6. Click the IP Address tab and select Yes for the Enabled option of each IP address. 7. Make sure the TCP Dynamic Ports item is null for IPAll and each IPn (such as IP1, IP2, IP3, etc). Set TCP Port to 8433 on the IP Address tab as shown in Figure 41. The TCP Port should be specified as needed. Make sure the specified TCP Port has not been used by any other instances and application. 30 Setting up SQL Server 2008

31 Figure 41 Configure IP addresses for TCP/IP 8. 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. 9. Click OK. 10. 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 Otherwise, you cannot connect to the database. You can use the same way to enable the Named Pipes property. Modifying the maximum server memory for SQL Server To ensure the optimum SQL server performance, the maximum server memory is set to 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: Modifying the maximum server memory for SQL Server 31

32 1. Select All programs > Microsoft SQL Server 2008 > SQL Server Management Studio from the Start menu. Figure 42 Database login window 2. Select SQL Server Authentication from the Authentication list. 3. Enter super username sa in the Login field, enter the password, and click Connect. Figure 43 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. 32 Setting up SQL Server 2008

33 Figure 44 Set server properties 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. After the previous operations, restart the operating system to validate the modification. Starting the SQL Server Browser service If you set a custom instance for the SQL Server 2008, 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 2008 > Configuration Tools > SQL Server Configuration Manager. Figure 45 Launching the 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. Starting the SQL Server Browser service 33

34 Figure 46 Locating the SQL Server Browser service 3. Click the Service tab, and then select Automatic for Start Mode. Figure 47 Service tab 4. Click OK. 34 Setting up SQL Server 2008

35 5. In the SQL Server Configuration Manager window, right-click SQL Server Browser, and then select Start from the shortcut menu. Figure 48 Starting the SQL Server Browser service Configuring SQL Server service to Log on as local system (Optional) 1. In the SQL Server Configuration Manager window, select SQL Server Services from the navigation tree. You can view the operational status of SQL Server services on the right, as shown in Figure 49. Figure 49 Operational status of SQL Server services 2. Check the Log On As column of the SQL Server, and ensure its value is Local System. If you follow the previous installation steps, the value is Local System. Otherwise, the value can be Network Service. In this case, double-click the row (or select the row and then click the Properties button on the toolbar), and the SQL Server Properties dialog box appears. In the dialog box, change the Log on as property into Local System in the Built-in account option. Configuring SQL Server service to Log on as local system (Optional) 35

36 Figure 50 Configure the Log on as property on the SQL Server Properties dialog box 3. Click OK to save the configuration. 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. 1. On the SQL Server Configuration Manager window, select SQL Server Services from the navigation tree. 2. Select SQL (MSSQLSERVER) on the right. 36 Setting up SQL Server 2008

37 3. Click Restart service on the toolbar, as shown in Figure 51. Figure 51 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 super user and granting a privilege to the user By default, the super user sa is used to access the SQL Server database. You can create a super user and grant the administrator privilege to it. 1. Select Start > All programs > Microsoft SQL Server 2008 > SQL Server Management Studio. The database login window appears, as shown in Figure 52. Figure 52 Login interface Creating a super user and granting a privilege to the user 37

38 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 53. The page for adding a login user appears, as shown in Figure 54. Figure 53 Microsoft SQL Server Management Studio main pane 38 Setting up SQL Server 2008

39 Figure 54 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 ( ) \t 5. From the navigation tree, select Server Roles and then set the server roles as shown in Figure 55. Creating a super user and granting a privilege to the user 39

40 Figure 55 Setting server roles 6. Select sysadmin and click OK. The user is granted with the database administrator privilege and appears under the Security > Logins node in the navigation tree of the Microsoft SQL Server Management Studio main pane. 40 Setting up SQL Server 2008

41 6 Uninstalling an SQL Server database If you uninstall the SQL Server database with the Remove function on the Control Panel > Add or Remove Programs page, you may fail to uninstall the database (the setup.exe process hangs) because of operating system configuration problems. As a solution, you can use the Change function to uninstall the database as shown in Figure 56. Figure 56 Uninstall SQL Server 2008 with the Change function 41

42 7 FAQs When the default instance of database has been used by other application, how to install the database using named instance? The installation procedure is similar to the installation procedure of using the default instance. The following section describes only the differences. After the Setup Support Rules check is complete. Click Next to enter the Installation Type dialog box. Figure 57 Installation Type Select New installation or add shared features and click Next. Enter the product key, agree with the license terms, and select the setup role. And then the Feature Selection dialog box appears. 42 FAQs

43 Figure 58 Feature Selection Select the features as shown in the figure above, and then click Next. Enter the Instance Configuration dialog box appears. Figure 59 Instance Configuration When the default instance of database has been used by other application, how to install the database using named instance? 43

44 Select the Named instance, and enter an instance name. Set the Instance root directory. Click Next to enter the Server Configuration dialog box. Figure 60 Server Configuration Set the account name as shown in the figure above. Click Next to enter the Database Engine Configuration dialog box. 44 FAQs

45 Figure 61 Database Engine Configuration Configure the Authentication Mode as Mixed Mode and input the password of user sa. Make sure the password does not contain the following characters: < > \t. The Data Directions and FILESTREAM use the default values without any configuration. The following setup is the same as the setup when the default instance is used. Does changing the computer name affect the database? How to restore the database? Changing a computer name might cause failures on operating the SQL Server database. In this case, perform the following operations to update the computer name saved in the database: For example, the old computer name is SERVER_1 and the new name is SERVER_2. 1. Open the CMD window and execute the following scripts (where the login user name is sa and the password is imcpass). osql -Usa -PIMCpass go The window displays the old computer name SERVER_1 on the interface. 2. Continue to execute the following commands to modify the computer name saved in the database: go SERVER_2, 'duplicate_ok' go exit The commands above first delete the old computer name SERVER_1 and then add a new one SERVER_2. Does changing the computer name affect the database? How to restore the database? 45

46 3. After the modification above, you must restart the SQL Server service in the Windows Service Manager to restore the database. During the IMC installation, "MS SQLServer is not Installed Correctly, MSSOLSERVER Service Does not Exist" is displayed. What shall I do? 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 specify an 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 in the IMC installation. During the IMC installation, "Database Service MSSQLSERVER Is not Configured to Be Started with Local System" is displayed. What shall I do? To create the database file for IMC, the MSSQLSERVER service must start with Local System and have the write rights to any local disk. Otherwise, IMC cannot be installed. To solve the problem, follow these steps: 1. Select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager. Figure 62 Select the SQL Server Configuration Manager from the Start menu 2. Right-click SQL Server (MSSQLSERVER) on the SQL Server Configuration Manager window and select Properties. Figure 63 SQL Server Configuration Manager window 46 FAQs

47 3. On the SQL Server (MSSQLSERVER) Properties window, click on the Built-in account radio button. 4. Select Local System from the list and then click OK as shown in Figure 64. Figure 64 SQL Server (MSSQLSERVER) Properties window 5. Restart the SQL Server (MSSQLSERVER) service on the SQL Server Configuration Manager window. During the IMC installation, "The ADO1.5 Component Is not Found in Current System" is displayed. What shall I do? 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 the IMC installation, "Provider Cannot Be Found" is displayed. What shall I do? This message means that MDAC is not installed on the server or that your MDAC installation is corrupted. MDAC corruption typically occurs when some application programs erroneously attempt to install a partial version of MDAC. To solve the problem: 1. You can download the installation program mdac_typ.exe from Microsoft website to re-install MDAC. 2. If MDAC installation fails, you can do as follows: During the IMC installation, "The ADO1.5 Component Is not Found in Current System" is displayed. What shall I do? 47

48 a. In Windows Explorer, open the C:\WINDOWS\inf folder, which might be hidden. b. Right-click the mdac.inf file in the folder and select Install. You can select each file from Service Pack CD-ROM, or from the current operating system. To select files from Service Pack CD-ROM, locate the i386 directory from the CD-ROM drive. For example, if the CD-ROM drive is D:, select the D:\i386 directory. To select files from the current operating system, click Browse, select a file, and click Retry. c. Files to be located during the installation and their default locations are as follows: 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 find the MDACRdMe.htm, change the name of the file MDACReadme.htm to MDACRdMe.htm. MDAC is successfully installed if no error message is displayed after the you complete the installation. d. Reboot the operating system, after installation is completed. 3. If the problem persists, use the MDAC Component Checker to locate MDAC installation problems. a. Download the MDAC Component Checker named cc_pkg.exe from the Microsoft website for free. b. Decompress it to the C:\ComponentChecker directory. c. Select the first option in the window. d. Click OK, as shown in Figure FAQs

49 Figure 65 Component Checker window After a short time analysis, the window displays mismatch information under the File Details node, as shown in Figure 66. Mismatch information indicates the potential problems for the MDAC installation. Figure 66 Information about MISMATCH under File Details Mismatch information indicates the potential problems for the MDAC installation. e. Click MISMATCH and view files in the right window. 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. f. If the version mismatch information cannot be solved through MDAC installation, copy files to the corresponding directories. g. Locate the mdacxpak.cab file from the depressed path of MDAC_TYPE.exe and use WinZip to decompress the mdacxpak.cab file. The file contains most of the important MDAC files. h. Copy the depressed files to corresponding paths shown in MISMATCH. i. Reboot the operating system. 4. If you still cannot solve the problem, reinstall your operating system and databases, or contact the technical support department. During the IMC installation, "Provider Cannot Be Found" is displayed. What shall I do? 49

50 During the IMC installation, the system displays "Failed to run bcp.exe, Database tools not installed or Windows not restarted after MS SQL Server installed". How to solve this 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 it is not installed: 1. Run the SQL Server 2008 installation program. 2. Select Client Tools Connectivity on the Feature Selection page. 3. Restart Windows to make the client software bcp.exe take effect after the Client Tools Connectivity feature is installed. Figure 67 Feature Selection page How can I update database passwords for IMC? The usernames and passwords used by the 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, a user can use the database management tool to change the database password of a certain IMC component. To ensure communication between IMC and the database, use the pwdmgr.bat command to update the corresponding password in file server-addr.xml. If IMC is deployed in distributed mode, you must update the password for every IMC server. 50 FAQs

51 Figure 68 Update database passwords for IMC In the preceding commands, represents 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 file $IMCROOT/common/conf/server-addr.xml. The dbpasswd string represents the latest database password of the IMC_config user, and the config_db string represents the database name. How can I update database passwords for IMC? 51

52 8 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: 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: After registering, you will receive 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: 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: HP Networking: HP download drivers and software: Typographic conventions This section should list only those conventions actually used in the document and only information that is critical to a user's understanding, such as the meaning of cautions and warnings. This section describes the conventions used in this documentation set. 52 Support and other resources

53 Document conventions Table 1 Document conventions Convention Blue text: Table 1 (page 53) Blue, underlined text: Description Cross-reference links and 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 2 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. Typographic conventions 53

54 Index C configuring SQL server service to log on as local system, 35 configuring TCP/IP properties, 28 contacting HP, 52 creating a super user, 37 D dialog box collation, 13 complete, 27 data directories, 15 database engine configuration, 13 disk space requirements, 11, 23 error and usage reporting, 23 error reporting, 16 feature selection, 9, 22 FILESTREAM, 15 install setup files, 8 installation complete, 19 installation configuration rules, 16 installation progress, 18, 25 installation rules, 24 instance configuration, 10 license terms, 6 product key, 6 ready to install, 17, 25 service configuration, 11 setup support rules, 8 specifying SQL Server administrators, 14 SQL Server installation center, 5 documentation, 52 typographic conventions, 53 F FAQ ADO1.5 Component is not found, 47 failed to run bcp.exe, 50 MS SQLServer is not installed correctly, 46 MSSQLSERVER is not configured to be started with local system, 46 provider cannot be found, 47 updating database passwords, 50 FAQs, 42 G granting a privilege creating a super user, 37 H help obtaining, 52 HP technical support, 52 I IMC SQL Server 2008, 4 IMC installation configuration info, 4 database, 4 installation database configuration, 4 installing SQL client, 22 feature selection, 22 IMC installation database, 5 installing SQL Server 2008, 5 introduction SQL Server 2008 in IMC, 4 L login interface, 37 M maximum server memory modifying, 31 modifying the maximum server memory, 31 MSSQLSERVER server configuration manager, 36 P procedure installing SQL Server 2008, 5 R registering product, 52 subscription service, 52 registering SQL server license, 20 restarting the SQL server service, 36 S server license registering, 20 server setup, 28 SQL server authentication, 38 restarting service, 36 server configuration, 28 server configuration window, 28 setup, 28 uninstalling server database, 41 SQL Server Browser service starting, 33 SQL server management studio, 37 starting the SQL Server Browser service, 33 T TCP/IP 54 Index

55 configuring, 28 technical support, 52 HP, 52 typographic conventions documentation, 52 symbols, 53 text GUI conventions, 53 U uninstalling SQL server database, 41 W websites, 52 55