HPE Intelligent Management Center SQL Server 2008 R2 Installation Guide
Oglas
Oglas
HPE Intelligent Management Center
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 the
Microsoft SQL Server. This document is applicable to the SQL Server 2008 R2 SP1 Enterprise edition and slightly different from other editions of SQL Server 2008. This document is intended for use by network engineers and system administrators responsible for installing network software and components.
Part number: 5200-2702
Software version: IMC PLAT 7.3 (E0501)
© Copyright 2015, 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise 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. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise 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.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Contents
Acknowledgments ··········································································· 2
Overview ······················································································· 1
Installing SQL Server 2008 R2 ··························································· 2
Registering the SQL server license ···················································· 16
Installing the SQL Server client ························································· 18
Setting Up SQL Server 2008 R2 ························································ 24
Uninstalling the SQL Server database ················································ 37
Installing the embedded database······················································ 38
FAQs ··························································································· 40
About HPE IMC documents ······························································ 49
Document conventions ···································································· 50
Support and other resources····························································· 51
i
Overview
Before installing IMC, install the SQL Server first. After installing the SQL Server, restart the operating system, update the server with the 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 a 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 enter the local path to the folder, as shown in Figure 1 .
Figure 1 IMC installation-Database Configuration Info
NOTE:
To ensure normal operation of the SQL Server, use licensed installation software of the Microsoft
SQL Server. Using localized software or other unauthorized editions might cause a failure in database installation and operation.
1
Installing SQL Server 2008 R2
1. After running the setup program, enter the SQL Server Installation Center , as shown in
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
2
Figure 3 Setup Support Rules page
3. Click OK to enter the Product Key
Figure 4 Product Key page
3
4. Enter the product key and click Next to enter the License Terms page, as shown in
Figure 5 License Terms page
5. Select I accept the license terms and click Next to enter the Setup Support Files page, as
Figure 6 Setup Support Files page
4
6. Click Install
to start installing setup support files, as shown in Figure 7 .
Figure 7 Setup Support Files operation process
Upon completion of the installation, the Setup Support Role
page opens, as shown in Figure
Figure 8 Setup Support Role page
5
7. Click Next to open the Setup Role page, as shown in
Figure 9 Setup Role
8. Select SQL Server Feature Installation and click Next to enter the Feature Selection page,
Figure 10 Feature Selection page
6
9.
Select the features shown in Figure 10 , and consult your SQL Server administrator for an
optimized location of shared features. Click Next and the Installation Rules page opens, as
Figure 11 Installation Rules page
10. Click Next to enter the Instance Configuration
Figure 12 Instance Configuration page
7
11. Select Default instance and use MSSQLSERVER as the Instance ID . Do not modify the default instance ID. As a best practice, 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
the instance ID in the Instance Name field on the Checking Database Connectivity page during IMC installation.
If you set a custom instance ID for the SQL Server 2008 R2 Express edition, start the SQL
12. Click Next to enter the Disk Space Requirements
Figure 13 Disk Space Requirements page
13. Click Next to enter the Server Configuration
8
Figure 14 Server Configuration page
14. If you selected Named instance
for the SQL Server in Figure 12 , set
Startup Type for the SQL
Server Browser service to Automatic .
15. Click Use the same account for all SQL Server services to set a service account, as shown
Figure 15 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 page, as shown in Figure 16 .
9
Figure 16 Server Configuration page
16. Click the Collation
Figure 17 Collation tab page
10
17. Without any configuration on the Collation tab page, click Next to enter the Database Engine
Configuration
Figure 18 Database Engine Configuration page
18. Configure the Authentication Mode as Mixed Mode and enter 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. You can also specify a SQL Server
administrator according to the actual conditions, as shown in Figure 19 .
IMPORTANT:
For IMC to correctly identify the sa logon password during installation, make sure 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
11
Figure 19 Specifying SQL Server administrators
The Data Directions
tab page is shown in Figure 20 . Consult your SQL Server administrator
for an optimized location of SQL Temp and Data files.
Figure 20 Data Directories tab page
12
The FILESTREAM
tab page is shown in Figure 21 . Use the default values without any
configuration.
Figure 21 FILESTREAM tab page
19. Click Next to enter the Error Reporting
Figure 22 Error Reporting page
13
20. Without any configuration, click Next to enter the Installation Rules
Figure 23 Installation Rules page
21. Click Next to enter the Ready to Install
Figure 24 Ready to Install page
14
22. Click Install to enter the Installation Progress
Figure 25 Installation Progress page
The components installed are relevant to the features selected previously.
23. Upon completion of the installation, click Next to enter the Complete
24. Click Close to close the Complete page.
Figure 26 Complete page
15
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. The following information 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 a 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 27 for an example.
Figure 27 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 28 for an example of CAL licensing.
16
Figure 28 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 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.
17
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
page, select client components, as shown in Figure 29 . See
" Installing SQL Server 2008 R2 "
for how to enter the Feature Selection page.
Figure 29 Feature Selection page
2. Select the features (Management Tools – Basic and SQL Client Connectivity SDK) shown
Next .
18
Figure 30 Installation Rules page
3. Click Next to enter the Disk Space Requirements
Figure 31 Disk Space Requirements page
19
4. Click Next
and proceed to configure the error report settings shown in Figure 32 .
Figure 32 Error Reporting page
5. Use the default setting on the page, and click Next . The Installation Configuration Rules
page opens, as shown in Figure 33 .
Figure 33 Installation Configuration Rules page
20
6. Click Next to enter the Ready to Install
Figure 34 Ready to Install page
7. Confirm the installation information, and click Install to start installing SQL Server 2008 R2 client and to enter the Installation Progress
Figure 35 Installation Progress page
21
The components installed are relevant to the features selected previously. When the
installation process is complete the setup operation completion page opens, as shown in Figure
8. Click Close to close the Complete page.
Figure 36 Complete page
Testing connectivity
After the SQL Server client is installed, you can verify whether 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 of the following command:
For the default instance: osql –h172.8.9.63 –Usa –PiMC123
For a custom instance: osql –h172.8.9.63\instancename –Usa –PiMC123
In the previous commands, 172.8.9.63
is the IP address of the SQL server, sa and iMC123 are the username and password of the default superuser, and instancename is the name of the custom instance.
If the SQL command prompt is displayed, you successfully connected to the SQL server and entered the SQL command mode.
22
Figure 37 Testing connectivity
23
Setting Up SQL Server 2008 R2
The following information discusses the steps and procedures to setup and configure a 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
SQL Server Configuration
Manager
Figure 38 Launching the SQL Server Configuration Manager
Figure 39 SQL Server Configuration Manager
2. In the SQL Server Configuration Manager , click SQL Server 2005 Network Configuration .
3. If the database has only one instance, only one protocol item exists in the red frame in
6 .
24
4. If the database has multiple instances, perform the following steps to check the listening port used by each instance to avoid conflicts: a. Click Protocols for MSSQLSERVER on the left navigation tree. b. Double-click TCP/IP in the right pane (or click TCP/IP and then click the Properties button on the toolbar).
Figure 40 Launching the TCP/IP Properties page c. Click the IP Addresses tab to view the listening port used by the instance. The instance
uses TCP port 1433, as shown in Figure 41 .
Figure 41 Viewing the TCP port used by the database instance
25
5. Repeat step 4 to view the listening ports used by existing instances.
6. Configure the TCP/IP attributes for the newly added instance. Click Protocols for IMCMILP on the left navigation tree.
7. Double-click TCP/IP in the right pane (or click TCP/IP and then click the Properties button on the toolbar). The TCP/IP Properties
page opens, as shown in Figure 42 .
Figure 42 Configuring general TCP/IP properties
8. Select Yes for Listen All on the Protocol tab.
9. Select Yes for the Enabled option of each IP address.
10. 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 43 . The TCP Port should
be specified as needed. Make sure the specified TCP Port is not used by any other instances and application.
26
Figure 43 Configuring IP addresses for TCP/IP
11. Click OK to save the configuration.
12. Click OK when the following message is displayed: Any changes made will be saved; however, they will not take effect until the service is stopped and restarted.
13. 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 page, enter the page 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.
27
Modifying the maximum server memory for the
SQL Server
To ensure optimum SQL server performance, the maximum server memory is set to 2147483647 MB, so that the SQL Server can take advantage of the optimum amount of memory at any given time.
When IMC and the SQL Server are installed on the same server, to meet the memory requirements of IMC processes, you must control the maximum server memory that the SQL Server can use. As a best practice, set the maximum server memory to half the server's physical memory.
To modify the maximum server memory for SQL Server:
1. Select All programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio from the Start menu.
Figure 44 Database login page
2. Select SQL Server Authentication from the Authentication list.
3. Enter super username sa in the Login field, enter the password, and then click Connect .
Figure 45 Microsoft SQL Server Management Studio
28
4. Right-click the server name.
5. Select Properties from the shortcut menu.
6. Select Memory in the navigation tree.
Figure 46 Setting the maximum server memory
7. Set the value of Maximum server memory to half of the server's physical memory, and then click OK . In this example, the server ’s physical memory is 4096 MB, so set the value to 2048.
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 2008 R2 Express edition, you must start the SQL
Server Browser service, so IMC can connect to the SQL Server database.
If you set Startup Type for the SQL Server Browser service to Automatic during the SQL Server installation process, you do not need to start the SQL Server Browser service after the installation is complete.
To start the SQL Server Browser service:
1. Select Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL
Server Configuration Manager .
29
Figure 47 Launching the SQL Server Configuration Manager
2. Select SQL Server Services from the navigation tree.
3. On the right pane, right-click SQL Server Browser and then select Properties from the shortcut menu.
Figure 48 Launching the SQL Server Browser Properties page
4. Click the Service tab, select Automatic for Start Mode , and then click OK .
Figure 49 Setting the service start mode to Automatic
5. Right-click SQL Server Browser and select Start from the shortcut menu.
30
Figure 50 Starting the SQL Server Browser service
Configuring the SQL Server service to log on as local system (Optional)
1. On the SQL Server Configuration Manager page, select SQL Server Services from the navigation tree.
The page displays the operational status of SQL Server services on the right pane, as shown in
Figure 51 Viewing the operational status of SQL Server services
2. Verify that the Log On As column of the SQL Server displays Local System .
3. If the value is not Local System , perform the following steps: a. Double-click the SQL Server service (or select the service and then click the Properties button on the toolbar). b. On the SQL Server Properties dialog box, select the Built-in account option and then select Local System from the list, as shown in
c. Click OK .
31
Figure 52 Configuring the Log on as property on the SQL Server Properties dialog box
NOTE:
Valid characters for IMC database account passwords include all ANSI characters, except for the angle brackets (<, >) and tab character (\t). For example, you can use letters (A to Z and a to z), numerals (0 to 9), and symbols such as at (@), pound (#), dollar ($), caret (^), percent (%), ampersand (&), and asterisk (*).
Restarting the SQL Server service
After completing the preceding configurations, you must restart the SQL Server service to make the configurations take effect.
1. In the SQL Server Configuration Manager , select SQL Server Services from the navigation tree.
2. Select SQL Server (MSSQLSERVER) in the right pane, and then click Restart service on the
toolbar, as shown in Figure 53 .
This step is optional, because you must reboot the operating system before installing IMC after the SQL Server installation is complete. Rebooting the operating system automatically restarts all SQL Server services
32
Figure 53 Restarting the SQL Server Service
Creating a database user with administrator privileges
When installing IMC, you must be a super user to access the database. The super user can be the default user sa or a user-defined super user. The following information 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 page opens, as shown in Figure 54 .
Figure 54 Login interface
33
2. Select SQL Server Authentication from the Authentication list.
3. Select a login username, enter the password, and click Connect .
The Microsoft SQL Server Management Studio page opens.
4. Expand the Security node in the navigation tree, right-click Logins , and select New Login
from the shortcut menu, as shown in Figure 55 .
The menu screen for adding a login user opens, as shown in
Figure 55 Microsoft SQL Server Management Studio main pane
34
Figure 56 Adding a login user
5. Enter the login name, click SQL Server authentication , and then enter the password.
IMPORTANT:
For IMC to correctly identify the password, make sure that the password does not contain any of the following characters:
< > | \t
6. Clear User must change password at next login .
7. Select Server Roles in the navigation tree.
All the server roles are listed in the right pane, as shown in Figure 57 .
35
Figure 57 Selecting server roles
8. Select sysadmin and click OK .
The user is granted database administrator privileges.
After the previous operations, the new user is displayed under the Security > Logins node in the navigation tree of the Microsoft SQL Server Management Studio main pane.
36
Uninstalling the SQL Server database
If you uninstall the SQL Server database with the Remove function on the Control Panel > Add or
Remove Programs page, you might fail to uninstall the database (the setup.exe process hangs) because of operating system configuration problems. As an alternative, you can use the Change
function to uninstall the database, as shown in Figure 58 .
Figure 58 Uninstalling SQL Server 2008 R2 with the Change function
37
Installing the 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 the database installed.
Installation requirements
IMC Standard edition uses 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, make sure IMC manages no more than 1000 devices.
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. Go to http://www.microsoft.com/downloads 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 on the following operating systems: Windows XP SP3, Windows 2003 SP2, Windows 2003
R2 SP2, Windows 2008 SP2, Windows 7, and 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 the embedded database
You can install the embedded database when deploying IMC components.
For the Standard edition, if the component being deployed requires the support of the SQL Server database that is not installed on the server, a message is displayed on the Data Configuration Info page 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. On the Data Configuration Info page of the deployment wizard, select Install embedded database .
2. Click Next to enter the Configure Web Service Port page.
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 is displayed on the Data Configuration Info page to inform you of the unsatisfied requirements. You can install the database and deploy components only after the requirements are met.
38
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 .
39
FAQs
When the default instance of the database is used by other application, how do I install the database using the named instance?
The installation procedure is similar to the installation procedure for using the default instance. The following information describes only the differences. For information about other steps, see
" Installing SQL Server 2008 R2 ." After the
Setup Support Rules check is complete, click Next to enter the Installation Type
Figure 59 Installation Type page
Select New installation or add shared features and click Next.
Enter the product key, agree with the license terms, and select the setup role. The Feature Selection
page opens, as shown in Figure
40
Figure 60 Feature Selection page
Select the features as shown in Figure 60 , and then click
Next. The Instance Configuration page
opens, as shown in Figure 61 .
Figure 61 Instance Configuration page
41
Select Named instance , and enter an instance name. Set the Instance root directory . Click Next to enter the Server Configuration
Figure 62 Server Configuration
Set the account name as shown in
Next to enter the Database Engine
Configuration
42
Figure 63 Database Engine Configuration page
Configure the Authentication Mode as Mixed Mode and enter the password of user sa . Make sure the password does not contain the following characters: < > | \t.
Use the default settings on the Data Directions and FILESTREAM tabs.
The following setup is the same as the setup when the default instance is used.
Does changing the computer name affect the database? How do I restore the database?
Changing a computer name might cause some SQL Server database failures.
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 in
Windows and execute the following scripts (assuming that the login user name is sa and the password is iMCpass ): osql -Usa -PIMCpass select @@SERVERNAME 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: sp_dropserver @server=‘SERVER_1’, @droplogins=NULL go sp_addserver @server=‘SERVER_2’, @local='local', @duplicate_ok= 'duplicate_OK' go exit
43
The commands above first deletes the old computer name SERVER_1 and then adds 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, the following message is displayed: MS SQLServer Is not
Installed Correctly, MSSOLSERVER Service Does not Exist. How do I resolve the issue?
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, the following message is displayed: Database Service
MSSQLSERVER Is not Configured to Be Started with Local System. How do I resolve the issue?
During the installation, IMC requires its own database file to be created. If the MSSQLSERVER service is not configured to run as the Local System, IMC fails to be installed because of the disk access restriction. To resolve the issue:
Select Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL
Server Configuration Manager
Figure 64 Launching the SQL Server Configuration Manager
Right-click SQL Server (MSSQLSERVER) on the SQL Server Configuration Manager and select
Properties
44
Figure 65 SQL Server Configuration Manager
On the SQL Server (MSSQLSERVER) Properties page, click Built-in account , select Local
System from the list, and then click OK
Figure 66 SQL Server (MSSQLSERVER) Properties page
After completing the preceding configurations, you must restart the SQL Server (MSSQLSERVER) service on the SQL Server Configuration Manager page. After that, configurations take effect.
45
During the IMC installation, the following message is displayed: The ADO1.5 Component Is not Found in Current System. How do I resolve the issue?
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 resolve the issue, re-install ADO.
During the IMC installation, the following message is displayed: Provider Cannot Be Found.
How do I resolve the issue?
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 resolve the issue, download the installation program mdac_typ.exe from Microsoft's website to re-install MDAC. If MDAC installation fails, do the following:
1. In Windows Explorer, open the C:\WINDOWS\inf folder. This folder might 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.
To select files from Service Pack CD-ROM, locate the i386 directory on 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 then 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.
4. Reboot the operating system.
5. If the problem persists, you can use the MDAC Component Checker provided by Microsoft to locate MDAC installation problems. a. Download a free MDAC Component Checker, cc_pkg.exe
from the Microsoft website b. Decompress it to the C:\ComponentChecker directory.
46
c. In the Component Checker dialog box, select Perform analysis of your machine and automatically determine the release version , and click OK .
Figure 67 Component Checker page
After a short time analysis, mismatch information is displayed, as shown in Figure 68 .
View the information about MISMATCH under File Details . The MISMATCH information indicates the potential problems of the MDAC installation.
Figure 68 Viewing MISMATCH information under the File Details node d. Click MISMATCH and view files in the right 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.
6. When version mismatch cannot be solved through MDAC installation, you must copy files to the corresponding directories. a. 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. b. Copy the depressed files to corresponding paths shown in MISMATCH . c. Reboot the operating system.
7. If you still cannot resolve the issue, re-install your operating system and databases, or contact the technical support department.
47
During the IMC installation, the following message is displayed: Failed to run bcp.exe,
Database tools not installed or Windows not restarted after MS SQL Server installed. How do
I resolve the issue?
When you select to use a remote database server, a server the business components are not on,
IMC requires a tool such as bcp.exe to access the database. Manually install Connectivity
Components client tools on the IMC server. For the detailed installation procedures, see the Feature
Selection
After installing the Connectivity Components, restart Windows for the client software bcp.exe to 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 an 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 69 .
Figure 69 Updating 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 192.168.20.107
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 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 granted the proper rights to install the SQL server.
Table 1 User right list
Local policy object display name
Backup files and directories
Debug Programs
Manage auditing and security log
User right
SeBackupPrivilege
SeDebugPrivilege
SeSecurityPrivilege
48
About HPE IMC documents
The following are the documents available for HPE IMC:
Documents
Hardware specifications and installation
Purposes
HP IMC Getting Started Guide
HP IMC Installation Guide
HP IMC Probe Installation Guide
Quickly guides you through the IMC main features and troubleshooting common problems.
Provides a complete guide to IMC platform and component installation and deployment.
Provides a complete guide to IMC Probe installation and deployment.
SQL Server 2008 Installation and Configuration Guide Guides you through installing SQL Server 2008 for
IMC.
SQL Server 2008 R2 Installation and Configuration
Guide
Guides you through installing SQL Server 2008 R2 for IMC.
SQL Server 2012 Installation and Configuration Guide Guides you through installing SQL Server 2012 for
IMC.
SQL Server 2014 Installation and Configuration Guide Guides you through installing SQL Server 2014 for
IMC.
Oracle 11g Installation and Configuration Guide(for
Linux)
Oracle 11g R2 Installation and Configuration
Guide(for Linux)
Oracle 12c Installation and Configuration Guide(for
Linux)
MySQL 5.5 Installation and Configuration Guide (for
Linux)
MySQL 5.5 Installation and Configuration Guide (for
Windows)
MySQL 5.6 Installation and Configuration Guide (for
Linux)
MySQL 5.6 Installation and Configuration Guide (for
Windows)
Red Hat Enterprise Linux 6.4 Installation Guide
Guides you through installing Oracle 11g on Linux for IMC.
Guides you through installing Oracle 11g R2 on
Linux for IMC.
Guides you through installing Oracle 12c on Linux for IMC.
Guides you through installing MySQL 5.5 on Linux for IMC.
Guides you through installing MySQL 5.5 on
Windows for IMC.
Guides you through installing MySQL 5.6 on Linux for IMC.
Guides you through installing MySQL 5.6 on
Windows for IMC.
Guides you through installing Red Hat Enterprise
Linux 6.1 for IMC
Software configuration
HP IMC Base Platform Administrator Guide
Online Help
Operations and maintenance
Readme
Describes operation procedures on the IMC base platform.
Helps you properly use IMC.
Provides most recent IMC release information.
49
Document conventions
This section describes the conventions used in the documentation.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
Command conventions
Convention
Boldface
Italic
#
GUI conventions
Description
Bold text represents commands and keywords that you enter literally as shown.
Italic text represents arguments that you replace with actual values.
A line that starts with a pound (#) sign is comments.
Convention
Boldface
Description
Window names, button names, field names, and menu items are in Boldface. For example, the New User window opens; click OK .
Multi-level menus are separated by angle brackets. For example, File > Create >
Folder .
Symbols
>
Convention
WARNING!
CAUTION:
IMPORTANT:
NOTE:
TIP:
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.
An alert that provides helpful information.
50
Support and other resources
Accessing Hewlett Packard Enterprise Support
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website: www.hpe.com/support/hpesc
Information to collect
Technical support registration number (if applicable)
Product name, model or version, and serial number
Operating system name and version
Firmware version
Error messages
Product-specific reports and logs
Add-on products or components
Third-party products or components
Accessing updates
Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method.
To download product updates, go to either of the following:
Hewlett Packard Enterprise Support Center Get connected with updates page: www.hpe.com/support/e-updates
Software Depot website: www.hpe.com/support/softwaredepot
To view and update your entitlements, and to link your contracts, Care Packs, and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on
Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials
51
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett
Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.
Websites
Website
Networking websites
Hewlett Packard Enterprise Information Library for
Networking
Hewlett Packard Enterprise Networking website
Hewlett Packard Enterprise My Networking website
Hewlett Packard Enterprise My Networking Portal
Hewlett Packard Enterprise Networking Warranty
General websites
Hewlett Packard Enterprise Information Library
Hewlett Packard Enterprise Support Center
Hewlett Packard Enterprise Support Services Central
Contact Hewlett Packard Enterprise Worldwide
Subscription Service/Support Alerts
Software Depot
Customer Self Repair (not applicable to all devices)
Insight Remote Support (not applicable to all devices)
Link www.hpe.com/networking/resourcefinder www.hpe.com/info/networking www.hpe.com/networking/support www.hpe.com/networking/mynetworking www.hpe.com/networking/warranty www.hpe.com/info/enterprise/docs www.hpe.com/support/hpesc ssc.hpe.com/portal/site/ssc www.hpe.com/assistance www.hpe.com/support/e-updates www.hpe.com/support/softwaredepot www.hpe.com/support/selfrepair www.hpe.com/info/insightremotesupport/docs
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website: www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service, or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure
52
submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback ( [email protected]
). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
53
Preuzimanje
Javna poveznica ažurirana
Javna poveznica na vaš razgovor je ažurirana. You may view and manage your chat links after registration here.
Javna poveznica dokumenta
Oglas