SQL Server 2008 R2. Installation and Configuration Guide

Transcription

1 SQL Server 2008 R2 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 R2 SP1 Enterprise edition and slightly different from other editions of SQL Server This document is intended for use by network engineers or system administrators responsible for installing network software and components. Part number: Software version: IMC PLAT 5.2 (E0401) Document version: 5P

2 Legal and notice information Copyright 2013 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 Installing SQL Server 2008 R2 1 2 Registering the SQL server license 25 3 Installing the SQL Server client 27 Installation procedure 27 Testing connectivity 34 4 Setting Up SQL Server 2008 R2 36 Configuring TCP/IP properties 36 Starting the SQL Server Browser service 40 Configuring the SQL Server service to log on as local system (Optional) 42 Restarting the SQL Server service 44 Creating a super user and granting a privilege to the user 45 5 Uninstalling SQL Server database 49 6 Installing embedded database 50 Installation requirements 50 Installation preparations 50 Installing embedded database 50 Removal requirements 51 7 FAQs 52 Support and other resources 62 Contacting HP 62 Subscription service 62 Related information 62 Documents 62 Websites 62 Conventions 63 Index 64 i

4 1 Installing SQL Server 2008 R2 Before installing IMC, install SQL Server first. After installing SQL Server, restart the operating system, update the server with latest Windows patches and then proceed to install IMC. You can install IMC components on a specific server, install the database on a remote server, and save IMC data on the database server. To install the database on a remote 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 on the database server before you start the installation. When deploying the IMC components, you can input the local path to the folder, as shown in Figure 1. Figure 1 IMC installation-database Configuration Info NOTE: To ensure the normal 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. 1

5 1. After running the setup program, enter the SQL Server Installation Center, as shown in Figure 2. Figure 2 SQL Server Installation Center 2. Select Installation from the navigation tree, and then click New installation or add features to an existing installation to enter the Setup Support Rules dialog box, as shown in Figure 3. 2

6 Figure 3 Setup Support Rules dialog box 3. Click OK to enter the Product Key dialog box, as shown in Figure 4. 3

7 Figure 4 Product Key dialog box 4. Input the product key and click Next to enter the License Terms dialog box, as shown in Figure 5. 4

8 Figure 5 License Terms dialog box 5. Select I accept the license terms, and click Next to enter the Setup Support Files dialog box, as shown in Figure 6. 5

9 Figure 6 Setup Support Files dialog box 6. Click Install to start installing setup support files. The setup support files dialog box appears, as shown in Figure 7. 6

10 Figure 7 Setup Support Files operation process 7. Upon completion of the installation, the Setup Role dialog box appears, as shown in Figure 8. 7

11 Figure 8 Setup Role dialog box 8. Select SQL Server Feature Installation and click Next to enter the Feature Selection dialog box, as shown in Figure 9. 8

12 Figure 9 Feature Selection dialog box 9. Select the features as shown in Figure 9, and then click Next and the Installation Rules dialog box appears as shown in Figure 10. 9

13 Figure 10 Installation Rules dialog box 10. Click Next to enter the Instance Configuration dialog box, as shown in Figure

14 Figure 11 Instance Configuration dialog box Select Default instance and use MSSQLSERVER as the Instance ID. Do not modify the default instance ID. HP recommends you also set the default instance for the SQL Server 2008 R2 Express edition, even though the Named instance option is selected by default. An advanced user can select Named instance and then enter a custom instance ID. For detailed installation step, see When the default instance of database has been used by other application, how to intall the databse using named instance? 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 R2 Express edition, start the SQL Server Browser service after the installation. For more information, see "Starting the SQL Server Browser service." 11. Click Next to enter the Disk Space Requirements dialog box, as shown in Figure

15 Figure 12 Disk Space Requirements dialog box 12. Click Next to enter the Server Configuration dialog box as shown in Figure

16 Figure 13 Server Configuration dialog box 13. Click Use the same account for all SQL Server services to set a service account, shown in Figure 14. Figure 14 Use the same account for all SQL Server 2008 R2 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

17 Figure 15 Server Configuration dialog box 14. Click Collation, as shown in Figure

18 Figure 16 Collation tab page 15. Without any configuration on the Collation tab page, click Next to enter the Database Engine Configuration dialog box, as shown in Figure

19 Figure 17 Database Engine Configuration dialog box 16. Configure the Authentication Mode as Mixed Mode and input the password of user sa. SQL Server 2008 R2 has certain requirements for password complexity. For information about password complexity, see the online help in the system. Furthermore, you can specify an SQL Server administrator according to the actual conditions, as shown in Figure 18. IMPORTANT: For IMC to correctly identify the sa logon password during installation, make sure that the password does not contain any of the following characters: < > \t If you do not want to change the password of the sa user, create a user with sa user privileges and make sure that the password does not contain any of the previous characters. For more information about creating a database user, see "Creating a super user and granting a privilege to the user." 16

20 Figure 18 Specify SQL Server administrators The Data Directions Figure 19 and FILESTREAM Figure 20 use the default values without any configuration. 17

21 Figure 19 Data Directories tab page The FILESTREAM tab page is shown in Figure

22 Figure 20 FILESTREAM tab page 17. Click Next to enter the Error Reporting dialog box, as shown in Figure

23 Figure 21 Error Reporting dialog box 18. Without any configuration, click Next to enter the Installation Rules dialog box, shown in Figure

24 Figure 22 Installation Rules dialog box 19. Click Next to enter the Ready to Install dialog box, as shown in Figure

25 Figure 23 Ready to Install dialog box 20. Click Install to enter the Installation Progress dialog box, as shown in Figure

26 Figure 24 Installation Progress dialog box The components installed are relevant to the features selected previously. 21. Upon completion of the installation, click Next to enter the Complete dialog box, as shown in Figure Click Close to close the Complete dialog box. 23

27 Figure 25 Complete dialog box 24

28 2 Registering the SQL server license The SQL server supports three license registration modes: Per Processor, Server/Client Access License (CAL), and Per User. The Per Processor is used for registering the SQL Server 2008 R2 Developer and Parallel Data Warehouse. This chapter describes the registration modes of Per Processor and Server/CAL. Per Processor licensing: The number of Per Processor licenses is counted by the number of processors on an SQL server. 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 26 for an example. Figure 26 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 27 for an example of CAL licensing. 25

29 Figure 27 Server/CAL 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. NOTE: The application of the license registration modes is for SQL Server 2005/2008/2008 R2 of standard and enterprise editions. You do not need to buy a license for the SQL Server Express edition. For more information about SQL server license registration, see official Microsoft documents. 26

30 3 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. 1. On the Feature Selection dialog box, select client components, as shown in Figure 28. See "1 Installing SQL Server 2008 R2" for how to enter the Feature Selection dialog box. Figure 28 Feature Selection dialog box 2. Select the features (Management Tools Basic and SQL Client Connectivity SDK) shown in Figure 29, and then click Next. 27

31 Figure 29 Installation Rules dialog box 3. Click Next to enter the Disk Space Requirements dialog box, shown in Figure

32 Figure 30 Disk Space Requirements dialog box 4. Click Next and proceed to configure error report settings shown in Figure

33 Figure 31 Error Reporting dialog box 5. Use the default setting on the dialog box, and click Next. The Installation Configuration Rules dialog box appears, shown in Figure

34 Figure 32 Installation Configuration Rules dialog box 6. Click Next to enter the Ready to Install dialog box shown in Figure

35 Figure 33 Ready to Install dialog box 7. Confirm the installation information, and click Install to start installing SQL Server 2008 R2 client and to enter the Installation Progress dialog box, as shown in Figure

36 Figure 34 Installation Progress dialog box 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 Click Close to close the Complete dialog box. 33

37 Figure 35 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, you successfully connect to the SQL server and enter the SQL command mode. 34

38 Figure 36 Testing connectivity 35

39 4 Setting Up SQL Server 2008 R2 This chapter discusses the steps and procedures to setup and configure an SQL Server. This includes: Configuring TCP/IP Configuring the SQL Server service Restarting the SQL Server service Creating a super user Configuring TCP/IP properties 1. Select Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager, as shown in Figure 37. The SQL Server Configuration Manager dialog box appears as shown in Figure 38. Figure 37 SQL Server Configuration Manager Figure 38 SQL Server Configuration Manager window 36

40 2. In the SQL Server Configuration Manager window, click SQL Server 2005 Network Configuration. 3. If the database has only one instance, only one protocol item exists in the red frame in Figure 39. In this case, go to step 5. 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. Follow these steps to check the listening ports of instances: a. Click Protocols for MSSQLSERVER on the tree on the left. b. Double-click TCP/IP on the right (or click TCP/IP and then click the Properties button on the toolbar). Figure 39 SQL Server Configuration Manager window c. On the IP Addresses configuration page, you can view the listening port used by the instance. The instance uses TCP port 1433, as shown in Figure

41 Figure 40 Configure TCP/IP properties 4. Repeat step 3 to view the listening ports used by existing instances. 5. Configure the TCP/IP attributes for the newly added instance. Click Protocols for IMCMILP on the tree on the left. 6. 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 as shown in Figure

42 Figure 41 Configure TCP/IP properties 7. Select Yes for Listen All on the Protocol tab. 8. Select Yes for the Enabled option of each IP address. 9. 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 42. The TCP Port should be specified as needed. Make sure the specified TCP Port has not been used by any other instances and application. 39

43 Figure 42 Configure IP addresses for TCP/IP 10. Click OK to save the configuration. 11. Click OK when the message box "Any changes made will be saved; however, they will not take effect until the service is stopped and restarted." appears. Restart the SQL server to make the configuration effective. For more information about the configuration procedure, see "Restarting the SQL Server service." NOTE: If you did not select Yes for Listen All on the TCP/IP Properties dialog box, enter the dialog box to update the previously-configured IP addresses if the server IP address changes after installing SQL Server 2008 R2. Otherwise, you cannot connect to the database. When you set the TCP/IP properties, for a named instance, all the IP addresses on the IP Address configuration page use the dynamic port (the value for TCP Dynamic Ports is set to 0) by default. You must first delete the value of the TCP Dynamic Ports item for IPALL and each IPn, and then specify the TCP port. In distributed deployment, if multiple database servers are used, these servers must have the same listening port. Starting the SQL Server Browser service If you set a custom instance for the SQL Server 2008 R2 Express edition, you must start the SQL Server Browser service, so IMC can connect to the SQL server database. 40

44 To start the SQL Server Browser service: 1. Select Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager. Figure 43 Launching the SQL server configuration manager 2. In the SQL Server Configuration Manager window, 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 44 Locating the SQL Server Browser service 3. Click the Service tab, and then select Automatic for Start Mode. 41

45 Figure 45 Service tab 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 46 Starting the SQL Server Browser service Configuring the SQL Server service to log on as local system (Optional) 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

46 Figure 47 Operational status of SQL Server services Check the Log On As column of the SQL Server, and make sure its value is Local System. The value is sure to be Local System if you strictly follow the installation steps mentioned above. If you did not strictly follow the installation steps mentioned above, the value may be Network Service. In this case, you should change it to Local System, with the procedure as follows: 1. Double-click the row, or select the row and then click the Properties icon on the toolbar. The SQL Server Properties dialog box appears. 2. Change the Log on as property to Local System in the Built-in account option, as shown in Figure

47 Figure 48 Configure the Log on as property on the SQL Server Properties dialog box NOTE: Valid characters for IMC database account passwords include all ANSI characters but the angle brackets (<, >) and tab character (\t). For example, you can use letters (A to Z and a to z), digits (0 to 9), and symbols such as at (@), pound (#), dollar ($), caret (^), percent (%), ampersand (&), and asterisk (*). 3. Click OK to save the configuration. Restarting the SQL Server service After completing the preceding configurations, you must restart the SQL Server service to make the configurations take effect. On the SQL Server Configuration Manager window, select SQL Server Services from the navigation tree, select SQL Server (MSSQLSERVER) on the right, and then click Restart service on the toolbar, as shown in Figure

48 Figure 49 Restart the SQL Server Service The reboot of the Windows operating system can automatically restart all the services. As the reboot of the operating system is required for installing IMC after the SQL Server installation is completed, you do not need to restart the SQL Server service separately. Creating a super user and granting a privilege to the user When installing IMC, you must use a super user to access the database. The super user can be the default user sa or a user-defined super user. This chapter describes how to create a super user and grant the administrator privilege to it. 1. Select Start > All programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio. The database login window appears, as shown in Figure

49 Figure 50 Login interface 2. Select SQL Server Authentication for Authentication, select a login username, enter the password, and click Connect. Expand the Security node in the navigation tree, right-click Logins, and select New Login from the shortcut menu. The following menu screen appears, Figure 51. Figure 51 Microsoft SQL Server Management Studio main pane 3. The Add a login user dialog box appears, as shown in Figure

50 Figure 52 Add a login user Set the login name, click SQL Server authentication, and set the password. IMPORTANT: For IMC to correctly identify the password, make sure that the password does not contain any of the following characters: < > \t 4. Clear the User must change password at next login box and select Server Roles in the navigation tree to set the server roles, as shown in Figure

51 Figure 53 Set server roles 5. Select sysadmin and click OK. The user is granted with the database administrator privilege. After the previous operations, the new user can be seen under the Security > Logins node in the navigation tree of the Microsoft SQL Server Management Studio main pane. 48

52 5 Uninstalling 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 54. Figure 54 Uninstall SQL Server 2008 R2 with the Change function 49

53 6 Installing embedded database To facilitate IMC installation and maintenance, you can use the automatic installation and configuration of the embedded database to install and deploy IMC of the Standard edition in the Windows operating system without database installed. Installation requirements IMC Standard edition use the embedded database of Microsoft SQL Server 2008 R2 SP2 Express. IMC dedicated edition does not provide an embedded database. Because the embedded database supports only limited data size (a maximum size of 10 G for each database), Use SQL Server 2008 Enterprise edition. To ensure stable IMC performance, use no more than 1000 devices that IMC manages. Before installing SQL Server 2008 R2 SP2 Express, install the software.net Framework 2.0 SP2 first. The embedded database setup programs do not install the software automatically. You can go to to download the software. NOTE: Microsoft SQL Server 2008 R2 SP2 Express can be installed only in the partition where Windows is installed and it requires about 500 MB of free disk space. SQL Server 2008 R2 SP2 Express can be installed in the following operating systems: Windows XP SP3, Windows 2003 SP2, Windows 2003 R2 SP2, Windows 2008 SP2, Windows 7, Windows 2008 R2. Installation preparations Before installing the embedded database, make sure the lower version SQL server has been uninstalled if there is any. Installing embedded database You can install the embedded database when deploying IMC components. For the Standard edition, if the component being deployed needs the support of the SQL Server database that is not installed on the server, a message appears in the Data Configuration Info window of the deployment wizard, asking you to install the embedded database. If the requirements for installing SQL Server 2008 R2 Express are met, perform the following steps: 1. In the Data Configuration Info window of the deployment wizard, select the Install embedded database checkbox. 2. Click Next to enter the Configure Web Service Port window. 3. Click Deploy. IMC automatically installs SQL Server 2008 R2 Express. After the installation finishes, you can deploy the components. If the requirements for installing SQL Server 2008 Express are not met, a message appears in the Data Configuration Info window to inform you of the unsatisfied requirements. You can install the database and deploy components only after the requirements are met. 50

54 NOTE: The same procedure applies to the installation of the embedded database on the master and subordinate servers. SQL Server 2008 R2 Express is automatically installed in the partition where Windows is installed. The login password for the sa user is IMC-Install2008. Removal requirements The embedded database is not automatically removed when you uninstall IMC. To remove it, select Control Panel > Add or Remove Programs. 51

55 7 FAQs When the default instance of database has been used by other application, how to intall the databse using named instance? The installation procedure is similar to the installation procedure of using the default instance. The following section describes only the differences. For the other steps, see Installing SQL Server 2008 R2. After the Setup Support Rules check is complete. Click Next to enter the Installation Type dialog box, as shown in Figure 55. Figure 55 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, as shown in Figure

56 Figure 56 Feature Selection Select the features as shown in Figure 56, and then click Next. Enter the Instance Configuration dialog box appears as shown in Figure

57 Figure 57 Instance Configuration Select the Named instance, and enter an instance name. Set the Instance root directory. Click Next to enter the Server Configuration dialog box as shown in Figure

58 Figure 58 Server Configuration Set the account name as shown in the figure above. Click Next to enter the Database Engine Configuration dialog box, as shown in Figure

59 Figure 59 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 may cause some failures on operating SQL Server database. In this case, perform the following operations to update the computer name saved in the database: Suppose the old computer name is SERVER_1 and the new one is SERVER_2. Open cmd.exe of Windows and execute the following scripts (assuming that the login user name is sa and the password is imcpass): osql -Usa -PIMCpass go The old computer name SERVER_1 is displayed on the interface. Continue to execute the following commands to modify the computer name saved in the database: go SERVER_2, 'duplicate_ok' 56

60 go exit The commands above first delete the old computer name SERVER_1 and then add a new one SERVER_2. 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? MSSQLSERVER is the default instance name of the Microsoft SQL Server. Displaying MSSQLSERVER means you have selected the default instance. If you do not select the default instance but specify an instance name ABC, MSSQL$ABC is displayed. To view the correct instance name, make sure the default instance or the specified instance name exists in the SQL Server Configuration Manager. During the IMC installation, "Database Service MSSQLSERVER Is not Configured to Be Started with Local System" is displayed. What shall I do? During the installation, IMC needs to create its own database file. If the MSSQLSERVER service is not configured to run as the Local System, IMC fails to be installed because of the disc access restriction. To solve the problem, do as follows: Select Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager as shown in Figure 60. Figure 60 Select SQL Server Configuration Manager from the Start menu Right-click SQL Server (MSSQLSERVER) on the SQL Server Configuration Manager window and select Properties, as shown in Figure

61 Figure 61 SQL Server Configuration Manager window On the SQL Server (MSSQLSERVER) Properties window, click Built-in account, select Local System from the list, and then click OK, as shown in Figure 62. Figure 62 SQL Server (MSSQLSERVER) Properties window 58

62 After completing the preceding configurations, you need to restart the SQL Server (MSSQLSERVER) service on the SQL Server Configuration Manager window. After that, configurations take effect. 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 error indicates that ADO 1.5 is corrupted. To solve the problem, you can re-install ADO. During the IMC installation, "Provider Cannot Be Found" is displayed. What shall I do? This error means that MDAC is not installed on the server or that your MDAC installation is corrupted. MDAC corruption usually occurs when some application programs erroneously attempt to install a partial version of MDAC. To solve the problem, you can download the installation program mdac_typ.exe from Microsoft's website to re-install MDAC. If MDAC installation fails, you can do as follows: 1. In Windows Explorer, open the C:\WINDOWS\inf folder. Note that the folder may be hidden. 2. 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. If you want 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:, you need to select the D:\i386 directory. If you want to select files from the current operating system, click Browse to select files. Select a file and click Retry. 3. MDAC is installed successfully if no error is displayed after you complete the installation. Files to be located during the installation and their 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. After the installation, you need to reboot the operating system. If the problem is not solved, you can use the MDAC Component Checker provided by Microsoft to locate MDAC installation problems. Download a free 59

63 MDAC Component Checker, cc_pkg.exe from the Microsoft website, decompress it to the C:\ComponentChecker directory, click on the first button in the window as shown in Figure 63, and click OK. Figure 63 Component Checker window After a short time analysis, some information is displayed, as shown in Figure 64. Pay attention to the information about MISMATCH under File Details. The MISMATCH information indicates the potential problems of the MDAC installation. Figure 64 Information about MISMATCH under File Details 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. When version mismatch cannot be solved through MDAC installation, you need to copy files to the corresponding directories. 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. Copy the depressed files to corresponding paths shown in MISMATCH. Reboot the operating system. If you still cannot solve the problem, you are recommended to re-install your operating system and databases, or contact the technical support department. 60

64 During the IMC installation, the system prompts "Failed to run bcp.exe, Database tools not installed or Windows not restarted after MS SQL Server installed". How to solve this problem? When you select to use a remote database server, a server which the business components are not on, IMC needs to use a tool such as bcp.exe to access the database. You should manually install Connectivity Components client tools on the IMC server. For the detailed installation procedures, see the Feature Selection dialog box in Figure 9. Additionally, after installing the Connectivity Components, you should restart the Windows to make the client software bcp.exe take effect. How can I update database passwords for IMC? The usernames and passwords used by the IMC modules are stored in cipher text in file \common\conf\ server-addr.xml in the installation path. You can use the pwdmgr.bat command to obtain passwords in clear text or update the latest passwords to the file. Usually, a user can use the database management tool to change the database password of a certain IMC module. 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, as shown in Figure 65. Figure 65 Update database passwords for IMC In the preceding commands, dbpasswd represents the latest database password of the IMC_config user, config_db represents the database name, and 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. Why I cannot 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 who is granted the proper rights to install the SQL server. Table 2 User right list Local policy object display name Backup files and directories Debug Programs Manage auditing and security log User right SeBackupPrivilege SeDebugPrivilege SeSecurityPrivilege 61

65 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: An notification is sent to you after registration is completed containing: Product enhancements New driver versions Firmware updates 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 A-Series Acronyms. HP.com: HP Networking: HP manuals: HP download drivers and software: 62

66 HP software depot: Conventions This section describes the conventions used in this documentation set. Command conventions Convention Boldface Italic / Description Bold text represents commands and keywords that you enter literally as shown. Italic text represents arguments that you replace with actual values. Multi-level menus are separated by forward slashes. For example, [File/Create/Folder]. 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 Convention WARNING CAUTION IMPORTANT NOTE Description An alert that calls attention to important information that if not understood or followed can result in personal injury. An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information. An alert that contains additional or supplementary information. 63

67 Index add a login user, 47 MISMATCH, 60 CAL licensing not configured to be started, 57 device CAL, 26 provider cannot be found, 59 user CAL, 26 restoring the database, 56 collation tab page, 15 server does not exist, 57 configuring TCP/IP properties, 36 SQL server configuration manager, 57 conventions SQL server not installed correctly, 57 command, 63 SQL server properties window, 58 GUI, 63 updating passwords, 61 symbols, 63 filestream, 19 data directories page, 18 HP support website, 62 database engine configuration IMC installation, 1 authentication mode, 16, 56 configuration info, 1 dialog box, 16 database, 1 mixed mode, 16, 56 installation dialog box database configuration, 1 completion, 24, 34 navigation tree, 2 database engine configuration, 15, 16 installing SQL disk space requirements, 12, 29 client, 27 error reporting, 20, 30 feature selection, 27 feature selection, 9, 27 IMC installation database, 1 installation progress, 23, 33 server 2008 R2, 1 installation rules, 10, 21, 28, 31 license terms dialog box, 5 instance configuration, 11 login interface, 46 license terms, 5 MSSQLSERVER product key, 4 database service, 57 ready to install, 22, 32 instance ID, 11 same account, 13 properties, 58 server configuration, 13, 14 server configuration manager, 59 setup role, 8 SQL server, 44 setup support files, 6 SQL Server, 57 setup support rules, 3 product key dialog box, 4 SQL server properties, 44 registering SQL server license, 25 embedded database related information installation preparations, 50 documents, 62 installation requirements, 50 websites, 62 installing, 50 restarting the SQL server service, 45 removal, 51 server license FAQs, 52 CAL licensing, 26 ADO 1.5 components not found, 59 per processor, 25 changing the computer name, 56 registering, 25 component checker window, 60 SQL server license, 25 database server not configured, 57 server setup, 36 database tools not installed, 61 set server roles, 48 failed to run, 61 setup role, 8 local system, 57 setup support files, 7 64

68 operation process, 7 rules, 7 setup support files dialog box, 6 SQL server administrator, 17 authentication, 47 change function, 49 configuration manager, 36 configuration manager window, 36, 58 installation center, 2 local system, 42 operational status, 43 properties window, 58 restarting service, 44 service, 44 services, 43 setup, 36 uninstalling server database, 49 SQL server management studio, 46 super user creating, 45 granting privileges, 45 support and resources contacting HP, 62 subscription service, 62 uninstalling SQL server database, 49 update database passwords, 61 websites, 62 65