CME V200R009C02SPC610 Installation Guide (Standalone CME for Windows)

DOCPROPERTY Confidential CME V200R009C02SPC610 Installation Guide (Standalone CME for Windows)

CMEV200R009C02SPC610Installation Guide (Standalone CME for Windows)

Document Version01

Release Date2011-3-25

DOCPROPERTY Confidential

Huawei Technologies Co., Ltd.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address:Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website:http://www.huawei.com

Email:[email protected]

Telephone:0755-28560000 4008302118

Fax0755-28560111

About This DocumentAuthorAuthorWang XiaoKangDate2011-3-25

Reviewed ByAn Xiangbin, Zhang Xiaomao, Chen Huanjun, Qian Cheng, Luo Shumin, Yan Hui, LianJie, Wu HaoDate2011-3-25

Tested ByCao JiaWuDate2011-3-25

Approved ByZhang XiaomaoDate2011-3-25

OrganizationIt is recommended that you read the installation guide of this version before using the V200R009C02SPC610. The following table lists the contents contained in this documentChapterDescription

1

REF _Ref241463446 \h \* MERGEFORMAT OverviewThis chapter provides the information related to the installation of the CME V200R009C02SPC610.

2

REF _Ref241463449 \h \* MERGEFORMAT PreparationsThis chapter describes the preparations for the installation of the CME V200R009C02SPC610 and related instruction.

3

REF _Ref251766385 \h Installation of the Standalone CMEThis chapter provides the guide to the installation of the CME V200R009C02SPC610.

4

REF _Ref273188897 \h GU Component InstallationThis chapter provides the guide to installation the GU Component of the CME V200R009C02SPC610.

5

REF _Ref273189450 \h Uninstallation of the Standalone CMEThis chapter provides the guide to the uninstallation of the CME V200R009C02SPC610.

6

REF _Ref251766443 \h FAQsThis chapter provides FAQs of the CME V200R009C02SPC610.

HistoryVersionDescriptionRelease DatePrepared ByApproved By

V1.00Initial commercial release2011-3-25

Contents91 Overview

91.1 Impacts of the Installation Process on the Existing Program

91.2 Match Standalone Mode Version

91.2.1 OS Versions

91.2.2 Database Version

101.2.3 Microsoft Office Version

101.2.4 NE Versions

131.2.5 Mapping Between Software Packages and Versions

142 Preparations

142.1 Obtaining the Software Required for the Installation

142.2 Installation Precautions

3-13 Installation of the Standalone CME

3-13.1 Checking Before the Installation of the SQL Server

3-23.2 Installing the SQL Server

3-33.3 Installing a New Standalone CME

3-123.4 Verifying the Installation

3-123.4.1 Starting the CME Client

4-134 GU Component Installation

4-134.1 Installing a CME Component Corresponding to a GU NE Version

5-155 Uninstallation of the Standalone CME

5-155.1 Uninstalling the Standalone CME

6-176 FAQs

6-176.1 What Should I Do When the System Displays ".Net Framework 2.0 Is not installed" While Installing the Microsoft SQL Server 2005 Express?

6-176.1.1 Symptom

6-186.1.2 Troubleshooting

6-186.2 What Should I Do When the System Displays 0x8007007e Error Message While Starting the SQL Server Configuration Manager?

6-186.2.1 Symptom


6-186.3 What Should I Do When the Name or Password of the Database User Is Changed After the Installation Is Complete?

6-186.3.1 Symptom


196.4 How Should I Check Whether the Port Used in the SQL Server 2005 is Static Port?

196.4.1 Symptom

196.4.2 Troubleshooting

216.5 How Should I Use the Static Port Instead of the Dynamic Port?

216.5.1 Sypmtom


216.6 How Should I Make the SQL Server 2000 Compatible with the SQL Server 2005?

216.6.1 Symptom


236.7 What Should I Do When the System Prompt Me to Use a Strong Password During the One-Click Installation of the SQL Server 2005?

236.7.1 Symptom


246.8 What Should I Do When the SQL Server Installation Program Fails to Install Files to the Compressed or Encrypted Folder?

246.8.1 Symptom


256.9 How Should I Check the Installation of .net Framework2.0?

266.10 How Should I Start and Stop the SQL Server Service?

266.11 How Should I Back Up and Restore the Data of the Standalone Version?

276.12 What Should I Do When the Script Engine VBScript Fails to Be Found During the Operation of the Standalone CME?

276.12.1 Symptom


286.13 What Should I Do When the System Prompts Me to Install Windows Installer 3.1 While Installing .net Framework2.0?

286.13.1 Symptom


286.14 How Should I Use Standalone Mode When I Did not Select the Server Components While Installating the CME?

286.14.1 Symptom


286.15 What Should I Do When Creating BTSs by Using the CME Takes a Long Time?

286.15.1 Symptom


326.16 What Should I Do When the System Displays "Provider cannot be found. It may not be properly installed" While Installing the CME?

326.16.1 Symptom


336.17 What Should I Do When the CME Menu Item Is Not on the GUI of the M2000 Client After the CME Is Installed on the Windows 2008?

336.17.1 Symptom


346.18 What Should I Do When the System Displays "Cannot resolve the collation conflict between 'Chinese_PRC_CI_AS' and 'Chinese_PRC_BIN'" While Creating a BTS by Importing the BTS Data to the CME?

346.18.1 Symptom

346.18.2 Cause


346.19 How Should I Check the Version Information of the MSDE?

356.20 What Should I Do When I Cannot Manually Delete the Help_cme.hdx File in the Installation Directory After Uninstalling the Standalone CME?

356.20.1 Symptom

356.20.2 Cause


366.21 What Should I Do When I Cannot Install the msxml6r During the Installation of the SQL Server?

366.21.1 Symptom

366.21.2 Cause


366.22 What Should I Do When Disk Space of the Default Installation Disk C Is Insufficient During One-Click Installation of the SQL Server?

366.22.1 Symptom

376.22.2 Cause


376.23 What Should I Do When A License Expires Because the System Time in the PC Is Not A.D Time?

376.23.1 Symptom

376.23.2 Cause


376.24 What Should I Do When the SQL Server Service Fails to Be Started Because An Error Occurs During the Installation of the SQL Server?

376.24.1 Symptom

386.24.2 Cause


396.25 What Should I Do When I Cannot Uninstall the CME Program in the Control Panel After the CME Offline Installation Fails?

396.25.1 Symptom

396.25.2 Cause


396.26 What Should I Do When the System Displays "Failed in starting CME service" While Starting the CME?

396.26.1 Symptom

396.26.2 Cause


396.27 What Should I Do When the CME Installation Program Cannot Be Complete?

396.27.1 Symptom

406.27.2 Cause


406.28 What Should I Do When a BSoD Is Displayed During the Installation of the SQL Server 2005 in Window XP?

406.28.1 Symptom

406.28.2 Cause


407 Version Changes

417.1.1 Feature Changes

418 Solved Problems and Unsolved Problems

428.1 Solved Problems

428.2 Unsolved Problems

429 Appendix

429.1 Preparation for the Upgrade

1 Overview1.1 Impacts of the Installation Process on the Existing Program If the CME V200R009 standalone or integrated mode is installed before, you need to uninstall it.

You must familiarize yourself with the CME V200R009C02SPC610 Release Notes.

The client software of the standalone mode is also applicable to the integrated mode.1.2 Match Standalone Mode Version1.2.1 OS VersionsOSVersion Description

Client: Windows Windows 7 Professional

Microsoft Vista Business Service Pack 1

Microsoft Windows XP Professional Service Pack 2 or later versions

1.2.2 Database VersionDatabase SystemVersion Description

Microsoft SQL Server 2005Microsoft SQL Server 2005 with SP3

(Microsoft SQL Server 2005 is one version of MSDE)

1.2.3 Microsoft Office VersionTable 1-1lists the Microsoft Office version required for implementing certain features of the CME V200R009C02SPC610.

Table 1-1 Required Microsoft Office versionDeviceVersion Description

CME client Microsoft Office Excel 2003

Microsoft Office Excel 2007

Microsoft Office Excel 2010

If the required Microsoft Office version is not provided, the following features cannot be implemented:

2G/3G radio network planning (RNP) data import and export in .xls format

3G Iu/Iur negotiation data import and export

3G Iub negotiation data import and export

2G/3G base station reparenting

2G cell parameter import and export in .xls format 2G RNP import and export in .xls format

2G cell frequency import and export in .xls format

2G TRX device import and export in .xls format

2G BA list import and export in .xls format

2G negotiation data import

GUI data table export in .xls format

Hot cell feature1.2.4 NE Versions

The CME supports the hot patch versions of the BSC6900, BSC6810, MBTS, NodeB and all patch versions of BSC6000.For example:If CME supports BSC6900V900R011C00SPC720, BSC6900V900R011C00SPH72# is supported by default.NE TypeNE Version

BSC6900BSC6900V900R011C00SPC700(Corresponding components need to be installed.)BSC6900V900R011C00SPC710(Corresponding components need to be installed.)BSC6900V900R011C00SPC720

BSC6810BSC6810V200R011C00SPC100BSC6800V100R012C00SPC100

TGWTGW1000V100R002C01SPC000

MBTSBTS3900V100R002C00SPC100

BTS3900V100R002C00SPC120

BTS3900 V100R002C00SPC121

BTS3900 V100R002C00SPC130

BTS3900 V100R002C00SPC150

BTS3900 V100R002C00SPC200

BTS3900 V100R002C00SPC220

BTS3900 V100R002C00SPC230

BTS3900V100R002C01

BTS3900V100R002C01SPC100

NodeBBTS3812E-12AC-12AE-BTS3812AV100R010C01SPC100

BTS3812E-12AC-12AE-BTS3812AV100R011C00SPC200


BTS3812E-12AC-12AE-BTS3812AV100R012C00



DBS3800V100R010C01SPC100

DBS3800V100R010C01SPC200

DBS3800V100R011C00SPC100

DBS3800V100R011C00SPC200

DBS3800V100R011C00SPC300

DBS3800V100R011C00SPC500

DBS3800V100R012C00

DBS3800V100R012C00SPC100

DBS3800V100R012C00SPC200

DBS3800V100R012C00SPC300

BTS3900-BTS3900A WCDMA V200R010C01SPC300








BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC050






BTS3900-BTS3900A-BTS3900L WCDMA V200R012C00




DBS3900 WCDMA V200R010C01SPC300














DBS3900 WCDMA V200R012C00




BTS3900-1U WCDMA V200R010C01SPC300








BTS3900-1U WCDMA V200R012C00




DBS3900-1U WCDMA V200R010C01SPC300








DBS3900-1U WCDMA V200R012C00












Data configuration of GBTSs is incorporated into the data configuration of BSCs, and the GBTS versions are not displayed on the CME client. For details about the supported GBTS versions, see the BSC6000 or BSC6900 release notes.The CME supports the hot patch versions of the BSC6900, BSC6000, BSC6810, MBTS, and NodeB.1.2.5 Mapping Between Software Packages and VersionsPackageVersion

Setup.exeCME V200R009C02SPC610

SQLEXPR32_sp3_ENU.EXEInstall.batMicrosoft SQL Server 2005 with SP3

CMEComponent_MBSC6900V9R11SPC700.exeBSC6900V900R011C00SPC700

CMEComponent_MBSC6900V9R11SPC710.exeBSC6900V900R011C00SPC710

2 Preparations2.1 Obtaining the Software Required for the InstallationDownload the CME software package at http://support.huawei.com/. After logging in to the website, choose Software Center > Version Software > Wireless Product Line > Wireless OSS > CME. Alternatively, you can obtain the software disk of CME

DOCPROPERTY ProductVersion \* MERGEFORMAT V200R009C02SPC610 Windows from Huawei.

CME SoftwareDirectory and Name of the Software PackageDescription

CME Softwaresetup.exeDownload the Client(Include Standalone Mode).rar package, and then decompress it.

MSDE Software\MSDE_Install\Download the Client(Include Standalone Mode).rar package, and then decompress it.

Save the package to a local PC. This document takes the root directory of C:/ as an example.Apply the license file for the standalone CME.Apply license file from Huawei Technology Support Website http://support.huawei.com. The detailed path is SUPPORT > NOTICE > Software Bulletin. Then, search for the OSS M2000&PRS&CME&AHR&APM Product Universal License Release Bulletin.2.2 Installation Precautions The CME standalone version can be installed only on an operating system of simplified Chinese or English version. Before installing the standalone CME V200R009C02, you need to install the Microsoft SQL Server 2005 Express.

The .net Framework2.0 or a later version needs to be installed for the installation of the Microsoft SQL Server 2005 Express (refer to chapter 6.9

REF _Ref288910982 \h How Should I Check the Installation of .net Framework2.0?). The .net Framework2.0 installation package is available in the dotNet Framework 2.0 folder in the installation of MSDE_Insall

If you have installed the standalone or integrated CME client on the local PC, uninstall the CME client first. Installing the standalone CME client requires:PC typeConfiguration

Windows XP (The lowest configuration)CPU:1.6GHz/Memory:1G/Disk:4GB free space

Windows Vista (The lowest configuration)CPU:2.0GHz/ Memory:2G/ Disk:4GB free space

Windows XP (The recommend configuration)CPU:2.0GHz/ Memory:2G/ Disk:8GB free space

Windows Vista (The recommend configuration)CPU:2.4GHz/ Memory:2G/ Disk:8GB free space

3 Installation of the Standalone CME

It takes about three minutes to install the SQL Server. After the installation, it takes about eight minutes to install the standalone CME client.

3.1 Checking Before the Installation of the SQL ServerStep 2 If the Microsoft SQL Server 2005 or SQL Server 2000 is not installed before, install one by referring to section 3.2 "Installing the SQL Server."

Step 3 If the Microsoft SQL Server 2005 Express database is installed, confirm the static port used on the SQL Server and obtain the port number by referring to section 6.4 "How Should I Check Whether the Port Used in the SQL Server 2005." If a dynamic port is used, modify the port configuration of the used instance by referring to section 6.5 "How Should I Use the Static Port Instead."

Step 4 If the SQL Server 2000 is installed, make it compatible with the SQL Server 2005 (if required) by referring to section 6.6 "How Should I Make the SQL Server 2000 Compatible with the SQL Server 2005." If no compatibility is required, uninstall the SQL Server 2000.

Step 5 The default password for the one-click installation of the SQL Server is emsems. If you need to change the password, change the SAPWD value in the template.ini file in the one-click installation package. A strong password containing uppercase letters, lowercase letters, and numerals is required for the installation of the SQL Server.

Step 6 If the SQL Server need install on other disk except C, referring to section 6.22

REF _Ref273190037 \h What Should I Do When Disk Space of the Default Installation Disk C Is Insufficient During One-Click Installation of the SQL Server?Step 7 If your computer runs Windows Server 2003, Windows Server 2008, or Windows 7, set a strong password by referring to section 6.7

REF _Ref289172126 \h \* MERGEFORMAT What Should I Do When the System Prompt Me to Use a Strong Password During the One-Click Installation of the SQL Server 2005? Then, install the SQL Server.----End3.2 Installing the SQL ServerStep 8 Copy the installation MSDE_Install to a hard disk on a local PC.

Step 9 Open MSDE_Install folder, and ouble-click Install.bat to perform one-click installation, as shown in Figure 3-1.Figure 3-2 One-click installation of the SQL Server 2005

Figure 3-3 The installation is complete. Installation finished

----End3.3 Installing a New Standalone CME

The standalone CME can be installed only in the Windows operating system. Therefore, do not install the standalone CME in other environments. You must install a standalone CME or use a standalone CME as a user in the Administrators user group. Before installing the standalone CME, suppose that the password of the SQL server user sa is emsems. Choose Start > Run, and then type cmd in the Run dialog box. Then, type sqlcmd -S127.0.0.1,1433 -Usa -Pemsems in the displayed interface. If 1> is displayed, you can infer that the database connection is normal. In such a case, type exit. If not, please check whether the sa password or the configuration of SQLServer 2005 was right. If you change the default port to another port, you need to add the port number when run the sqlcmd command to access the non-default port; otherwise, the connection to the port fails. For example, if you change the default port to port 1434, you need to run sqlcmd -S127.0.0.1,1434 -Usa -Pemsems to access port 1434.

Double-click Setup.exe in the folder of the Windows resource manager. Do not use tools such as Total commander.Step 10 Copy the installation package from the installation disk to a drive on the local PC.

Step 11 Open the installation package of the CME client, and then double-click setup.exe. A dialog is displayed, prompting you to select the language of the program. Choose Chinese (Simplified) or English, as shown in Figure 3-3.

Figure 3-4 Selecting the language

Step 12 After you click Next, the dialog box is displayed, as shown in Figure 3-4, prompting you to confirm the installation.Figure 3-5 Installation preparation

Step 13 Click Next. The License Agreement dialog box is displayed, as shown in Figure 3-5. Figure 3-6 License Agreement dialog box

Step 14 If you do not accept the terms, click Cancel. If you accept the terms, select I accept the terms of the license agreement and click Next. The dialog box shown in Figure 3-6 is displayed, showing user information.Figure 3-7 User information

Step 15 Click Next. A dialog box shown in Figure 3-7 is displayed, prompting you to specify the destination folder.Figure 3-8 Specifying the destination folder

Step 16 Specify the destination folder and then click Next. A dialog box shown in Figure 3-8 is displayed, prompting you to confirm the installation of the components. Select both of CME Client and Client Assistant Daemon. Click Next. Figure 3-9 Components to be installed

Step 17 Enter the MSDE database user name and password and port (default value is sa, emsems,1433) , and then click Next, as shown in Figure 3-9.

Figure 3-10 Database login information

Step 18 A dialog box is displayed, indicating that the wizard is ready to begin the installation. Figure 3-11 Wizard ready for the installation

Step 19 Click Install to start the installation. The progress of installing the data files is displayed, as shown in Figure 3-11. The system will install database automatically. Figure 3-12 Installation progress

Step 20 Click Finish to complete the installation and restart the computer.Figure 3-13 Installation progress

----End3.4 Verifying the Installation3.4.1 Starting the CME ClientChoose Start > All Programs > Huawei CME > CME Client. A windows dialog box is displayed, as shown in Figure 3-13. Figure 3-14 Starting the CME client

Click Browse to select a valid license file, then click OK to continue.The license file should be applied in advance from Huawei company.

Apply the license file refer to chapter 2.1 .----End4 GU Component Installation

Files of the most GU NE versions that are supported by the CME have been contained in the installation package of the standalone CME. You can install components corresponding to NE versions that are not frequently used on the standalone CME. For details about NE versions that need to install components, see section 1.2.4

REF _Ref273189814 \h NE Versions . It need 35~45 minutes to install a GU NE Component.4.1 Installing a CME Component Corresponding to a GU NE Version

To install a CME component corresponding to a certain GU NE version, perform the following steps:Step 21 Obtain the component package.

Log in to http://support.huawei.com, download the Client(Include Standalone Mode).rar file package corresponding to the current CME version, and then decompress it to obtain the CME component package corresponding to a GU NE version from the Standalone Component directory. The following part takes the CMEComponent_MBSC6900V9R12.exe file that corresponding to BSC6900 V900R012C00SPC100 for example.Step 22 Terminate CME application and double-click the CMEComponent_MBSC6900V9R12.exe file to start decompression.

Step 23 After the decompression is complete, a window is displayed, as shown in the following figure. Select a correct CME installation path, and then click Install.

Step 24 After the installation is complete, click OK

5 Uninstallation of the Standalone CME5.1 Uninstalling the Standalone CMEStep 25 Choose Start > Control Panel > Add or Remove Programs.

Figure 5-15 Selecting the CME

Step 26 Select the CME, and then click Change or Remove and confirm the operation.Figure 5-16 Confirmation for removing the CME

Step 27 The uninstallation progress is displayed.Figure 5-17 Uninstallation progress

Step 28 After the uninstallation is complete, check that the CME is removed from Control Panel.Figure 5-18 Confirmation for uninstallation of the CME

----End6 FAQs6.1 What Should I Do When the System Displays ".Net Framework 2.0 Is not installed" While Installing the Microsoft SQL Server 2005 Express?

6.1.1 Symptom

The system displays ".Net Framework 2.0 Is not installed" when the Microsoft SQL Server 2005 Express is being installed.


Install the NetFx20SP1_x86.exe program in the MSDE_Install\dotNet Framework 2.0 directory.

6.2 What Should I Do When the System Displays 0x8007007e Error Message While Starting the SQL Server Configuration Manager?

6.2.1 Symptom

The system displays "Cannot connect to WMI provider. You do not have permission [0x8007007e]" when the SQL Server Configuration Manager is being started.6.2.2 Troubleshooting

Copy the framedyn.dll file from C:\WINDOWS\system32\wbem\ to C:\WINDOWS\system32\.

Note: If the root disk of Windows installation directory is in other disks, copy the file to the system32 directory in the corresponding disk.

6.3 What Should I Do When the Name or Password of the Database User Is Changed After the Installation Is Complete?

6.3.1 Symptom

The name or password of the database user is changed after the installation is complete.


Run the Database Parameter Management.exe file in the \CME\Bin directory to modify the configuration parameters.

6.4 How Should I Check Whether the Port Used in the SQL Server 2005 is Static Port?

6.4.1 SymptomA static port of SQL Server 2005 is required for the installation of the standalone CME. If the default instance is used during the installation, the static port number is 1433. If a command instance is used during the installation, a dynamic port is required. The SQL Server 2005 sets a port number when the system is started each time.


Step 29 Check whether the port of SQL Server 2005 is static port.

1. Start the SQL Server Configuration Manager.

Figure 6-19 Starting the SQL Server Configuration Manager

2. Select the used instance, as shown in Figure 6-2. Then, double-click TCP/IP.

Figure 6-20 Selecting the used instance

3. On the IP Addresses tab page of the displayed TCP/IP Properties dialog box, if the values of all TCP dynamic ports are empty or 0, it indicates that a static port is enabled for the SQL Server 2005. Otherwise, it indicates that a dynamic port is used. In this case, use a static port instead by referring to section 6.5 "How Should I Use the Static Port Instead."

Figure 6-21 TCP/IP Properties dialog box

----EndStep 30 Obtain the port number.

You need to obtain the port number used in the SQL Server 2005 for the installation of the standalone CME. The default instance uses default port number 1433. You can confirm and obtain the port number by referring to Step 1"Check whether the port of SQL Server 2005 is static port."

6.5 How Should I Use the Static Port Instead of the Dynamic Port?

6.5.1 SypmtomA static port of SQL Server 2005 is required for the installation of the standalone version. If the default instance is used during the installation, the static port number is 1433. If a command instance is used during the installation, a dynamic port is required. The SQL Server 2005 sets a port number when the system is started each time.6.5.2 Troubleshooting

Step 31 Open the TCP/IP Properties dialog box in which the instances need to be configured by referring to 6.4.2 Step 1"Check whether the port of SQL Server 2005 is static port." in section 6.4 "How Should I Check Whether the Port Used in the SQL Server 2005 is Static Port?"

Step 32 Disable all the configured TCP dynamic ports, and then change the TCP port number to the specified number.

Step 33 After the configuration, restart the SQL Server.

6.6 How Should I Make the SQL Server 2000 Compatible with the SQL Server 2005?

6.6.1 Symptom6.6.2 Troubleshooting

Step 34 Modify the one-click installation template and use a command instance.

1. Modify the template.ini file in the released MSDE installation package, and then change the value of INSTANCENAM. MSSQLSERVER is the default instance name. If a command instance is to be used, you need to change MSSQLSERVER to a new value, for example, SQLServer2005.

2. Run the install.bat file. Figure 6-4 shows the template.ini file after the modification.

Figure 6-22 template.ini file after the modification

Step 35 Change the port number.

Change the port number to 1434 or other numbers (excluding the port number 1433, which has been used by the default instance) of the command instance by referring to section 6.5 "How Should I Use the Static Port Instead of the Dynamic Port?" after the installation is complete. Figure 6-5 shows the information about the modified ports.

Figure 6-23 Modified port information

6.7 What Should I Do When the System Prompt Me to Use a Strong Password During the One-Click Installation of the SQL Server 2005?

6.7.1 SymptomThe System prompts for a strong password during the one-click installation of the SQL Server 2005, as shown in Figure 6-6.

Figure 6-24 Displayed dialog box asking for a strong password


Step 36 Click Cancel in the dialog box shown in Figure 6-6,

Step 37 Change the password, namely, the SAPWD value in the template.ini file in the one-click installation package. The password must be a combination of uppercase letters, lowercase letters, and numerals, for example, OSScme11111111.

Step 38 Perform the one-click installation again and type the correct password when required.----End6.8 What Should I Do When the SQL Server Installation Program Fails to Install Files to the Compressed or Encrypted Folder?

6.8.1 SymptomThe system displays a dialog box indicating that the SQL Server installation program fails to install files to the compressed or encrypted folder, as shown as below.Figure 6-25 Displayed dialog box


Step 39 Double-click My Computer and find the path where the SQL Server is installed, for example, in disk C.

Step 40 Right-click Local Disk (C), and then choose Properties from the shortcut menu. On the General tab page, check whether Compress drive to save disk space is selected. If it is selected, deselect it, and then click OK, as shown in Figure 6-8.

Figure 6-26 Deselecting Compress drive to save disk space

Step 41 Run the SQL Server installation program again.

----End6.9 How Should I Check the Installation of .net Framework2.0?

Step 42 Choose Start > Control Panel. The Control Panel is displayed.

Step 43 Double-click Add or Remove Programs. The Add or Remove Programs window is displayed.

Step 44 In Currently installed programs, check whether a .net Framework2.0 or a later version is available. If a .net Framework2.0 or a later version is available, it indicates that the .net Framework2.0 is installed on the PC.

----End6.10 How Should I Start and Stop the SQL Server Service?

Step 45 Choose Start > Run, and then type cmd.

Step 46 If you need to stop the SQL Server service, run the net stop MSSQLServer command, as shown in Figure 6-9.

Figure 6-27 Running the net stop MSSQLServer command

Step 47 If you need to start the SQL Server service, run the net start MSSQLServer command, as shown in Figure 6-10.

Figure 6-28 Running the net start MSSQLServer command

----End6.11 How Should I Back Up and Restore the Data of the Standalone Version?

Step 48 Choose Huawei CME > Backup Restore.

Figure 6-29 Starting the backup and restore program

Step 49 In the displayed Backup/Restore cmedb dialog box, click Backup or Restore to perform the relevant operations.

Figure 6-30 Backup/Restore cmedb dialog box

----End6.12 What Should I Do When the Script Engine VBScript Fails to Be Found During the Operation of the Standalone CME?6.12.1 Symptom

When the standalone CME is running, the system displays a dialog box indicating that the Script Engine VBScript file fails to be found.6.12.2 TroubleshootingRun the regsvr32 vbscript.dll command for registration.

Figure 6-31 Running the vbscript.dll program

6.13 What Should I Do When the System Prompts Me to Install Windows Installer 3.1 While Installing .net Framework2.0?

6.13.1 Symptom

While installing .net Framework2.0, the system prompts for the installation of Windows Installer 3.1.

6.13.2 TroubleshootingThe installation path of Windows Installer 3.1 is http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=889482FC-5F56-4A38-B838-DE776FD4138C6.14 How Should I Use Standalone Mode When I Did not Select the Server Components While Installating the CME?

6.14.1 Symptom

The client components rather than the server components are selected for the installation of the CME. A standalone CME, however, is required later on.6.14.2 TroubleshootingUninstall the pre-installed CME and then reinstall the CME. And select the server components while installing the CME.

6.15 What Should I Do When Creating BTSs by Using the CME Takes a Long Time?

6.15.1 Symptom

Creating BTSs by using the CME takes a long time.6.15.2 TroubleshootingStep 50 Enable writing caching on the disk.

1. Right-click the hard disk in which the CME client is installed, and then choose Properties from the shortcut menu. A disk properties dialog box is displayed, as shown in Figure 6-14.Figure 6-32 Disk properties dialog box

2. Click the Hardware tab, and then select the hard disk drive whose writing caching you want to enable.

Figure 6-33 Hardware tab page

3. Right-click the hard disk drive, and then choose Properties from the shortcut menu. In the displayed hard disk drive properties dialog box, click the Policies tab, and then select Enable write caching on the disk.

Figure 6-34 Policies tab page

Step 51 Set Power schemes to Always On to improve the CME performance.

Choose Properties > Screen Saver > Power, and then set Power schemes to Always On in the displayed dialog box, as shown in Figure 6-17.Figure 6-35 Power Options Properties dialog box

6.16 What Should I Do When the System Displays "Provider cannot be found. It may not be properly installed" While Installing the CME?

6.16.1 Symptom

The system displays "Provider cannot be found. It may not be properly installed" during the installation of the CME.

6.16.2 TroubleshootingRun the resgvr32 command to register the sqloledb.dll file in the C:\Program Files\Common Files\System\Ole DB\ path, as shown in Figure 6-18.

Figure 6-36 Registering the sqloledb.dll file

6.17 What Should I Do When the CME Menu Item Is Not on the GUI of the M2000 Client After the CME Is Installed on the Windows 2008?

6.17.1 Symptom

After the CME is installed on the Windows 2008, the CME menu item is not on the GUI of the M2000 client.6.17.2 TroubleshootingSave the following information as a file named thirdtools.ini to the C:\windows\system32 path. You need to replace the contents highlighted in red with the current CME installation path.[CME]

AppPath=C:\Program Files\Huawei Technologies\CME\Bin\CMEMain.exe

AppParam=User,Ip,Port,Token,UserPrivileged

MenuName=CME

MenuShortcut=M

AccessKey=CMECurReadNote: If the local PC runs on the 64-bit Windows 2008 operating system, you need to save the thirdtools.ini file to the C:\Windows\SysWOW64 path.6.18 What Should I Do When the System Displays "Cannot resolve the collation conflict between 'Chinese_PRC_CI_AS' and 'Chinese_PRC_BIN'" While Creating a BTS by Importing the BTS Data to the CME?

6.18.1 Symptom

The system displays "Cannot resolve the collation conflict between 'Chinese_PRC_CI_AS' and 'Chinese_PRC_BIN'" when creating a BTS by importing the BTS data to the CME.

6.18.2 CauseThe Microsoft SQL Server2005 is not installed by strictly following the instructions in the upgrade guide.

6.18.3 TroubleshootingUninstall the Microsoft SQL Server 2005, and then re-install it by referring to section 3.2 "Installing the SQL Server."

6.19 How Should I Check the Version Information of the MSDE?

Step 52 Choose Start > Control Panel. The Control Panel is displayed.

Step 53 Double-click Add or Remove Programs. The Add or Remove Programs window is displayed, as shown in Figure 6-19.

Step 54 Check the version information from the installed programs list in the window.

Figure 6-37 Add or Remove Programs window

6.20 What Should I Do When I Cannot Manually Delete the Help_cme.hdx File in the Installation Directory After Uninstalling the Standalone CME?

6.20.1 Symptom

The Help_cme.hdx file in the installation directory cannot be deleted manually after the standalone CME is uninstalled6.20.2 Cause The Help_cme.hdx file is the material of the standalone CME, and is opened by the Hedex software. Therefore, when you attempt to delete the Help_cme.hdx file in the installation directory after the standalone CME is uninstalled, the system displays a message indicating that the file cannot be deleted because it is in use.6.20.3 TroubleshootingStop the Hedex services, and then delete the Help_cme.hdx file.6.21 What Should I Do When I Cannot Install the msxml6r During the Installation of the SQL Server?

6.21.1 Symptom

The system displays a message indicating that the msxml6r file cannot be installed during the installation of the SQL Server.

6.21.2 CauseThe operating system of the PC is Windows XP SP3, and the msxml6r.dll version of the Windows XP SP3 system is later than the version to be installed. Thus, the msxml6r.dll cannot be replaced by the previous version.6.21.3 Troubleshooting

Click OK.6.22 What Should I Do When Disk Space of the Default Installation Disk C Is Insufficient During One-Click Installation of the SQL Server?

6.22.1 Symptom

The disk space of the default installation disk C is insufficient during one-click installation of the SQL Server.6.22.2 Cause

The default installation path of one-click installation of SQL Server is C:\Program Files\Microsoft SQL Server\. However, the disk space of disk C is usually insufficient. Thus, the installation of the SQL server may fail, or the later installation of the standalone CME may fail.6.22.3 TroubleshootingNavigate to the installation path of the SQL Server, and then modify the INSTALLSQLDIR parameter in the template.ini configuration file.

6.23 What Should I Do When A License Expires Because the System Time in the PC Is Not A.D Time?

6.23.1 Symptom

A license expired because the time adopted by the PC is not A.D. time.6.23.2 CauseLicenses adopt A.D time, for example, 2010-01-01.6.23.3 TroubleshootingChange the system time in the PC to A.D. time.

6.24 What Should I Do When the SQL Server Service Fails to Be Started Because An Error Occurs During the Installation of the SQL Server?

6.24.1 Symptom

The SQL Server Service fails to be started because an error occurs during the installation of the SQL Server.

6.24.2 Cause

The failure to install the SQL Server results in the failure to start the SQL server service. The SQL server may fail to be installed because any of the following causes:

Another version of SQL Server has been installed before.

The files are not deleted completely during the uninstallation of the previous SQL Server.

Registration information cannot be deleted during the uninstallation of the previous SQL Server.6.24.3 TroubleshootingStep 55 Install Windows installer clean up software. Use the Windows installer clean up program to clear all the application related to the SQL Server and MSDE.

Step 56 Uninstall the SQL server by running uninstall.bat.

Step 57 Restart the PC and then install the SQL Server again.

EMBED Package 6.25 What Should I Do When I Cannot Uninstall the CME Program in the Control Panel After the CME Offline Installation Fails?

6.25.1 SymptomAfter the CME offline installation fails, the CME program cannot be uninstalled in the Control Panel.6.25.2 Cause

Errors occur in the registration information because the CME fails to be installed or other exceptions occur during the installation of the CME.6.25.3 TroubleshootingClear the installation directory of the CME, and then re-install the CME.

6.26 What Should I Do When the System Displays "Failed in starting CME service" While Starting the CME?

6.26.1 Symptom

The system displays "Failed in starting CME service" When starting the CME.6.26.2 Cause

The CmeServer service is not registered.6.26.3 TroubleshootingRun Server\Bin\RegisServer.bat to register the CmeServer service, and then restart the CME.

6.27 What Should I Do When the CME Installation Program Cannot Be Complete?

6.27.1 Symptom

The Finish dialog box is not displayed at the end of the CME installation process. The Setup.exe process still runs in the Windows task manager.6.27.2 Cause

A third-party program such as a program for remote access cannot be stopped because the program is suspended. Therefore, the information of the CME cannot be registered through the Setup.exe process.6.27.3 TroubleshootingOpen the Windows task manager and stop suspended programs such as mstsc.6.28 What Should I Do When a BSoD Is Displayed During the Installation of the SQL Server 2005 in Window XP?6.28.1 Symptom

During the installation of the SQL Server 2005 in Windows XP, a blue screen of death (BSoD) is displayed.6.28.2 Cause

According to the explanation of the Microsoft, the SQL Server 2005 software conflicts with the Windows XP operating system.6.28.3 Troubleshooting

Upgrade Windows XP to Windows XP Service Pack 3.7 Version ChangesThis chapter describes the changes in features, MML scripts, alarms, and performance counters.. The Standalone CME includes all the changes in features of Integrated CME by default. This chapter describes the changes in features only in Standalone CME.7.1.1 Feature Changes

New Features

1. The script executor automatically identifies the NEs in the project configuration file exported from the CME in standalone mode.DescriptionThe script executor automatically identifies the NEs in the project configuration file exported from the CME in standalone mode.

ImprovementBy FDN or NE name, the script executor can identify the NEs in the project configuration file exported from the CME in standalone mode.

ImplementationWhen loading scripts, the script executor can identify the NEs by FDN or NE name.

Related Operation1. Export the script.zip, the project of the script executor, from the CME in standalone mode.

2. Replace the name marked in red in "" in the scriptcfg.xml file of the script.zip package with the name of the actual NE to be delivered on the M2000.

3. On the CME in integrated mode, load the project through the script executor and activate the project.

PR NumberDTS2010071601222

Feature IDNone

8 Solved Problems and Unsolved ProblemsThis chapter describes the solved problems and unsolved problems. The Standalone CME includes all the solved problems an unsolved problems of Integrated CME by default. This chapter describes solved problems and unsolved problems only in Standalone CME.8.1 Solved ProblemsNone

8.2 Unsolved Problems

None

9 Appendix9.1 Preparation for the UpgradeItemDescriptionRemarks

Name of the upgrade device

Location of the upgrade device

Upgrade date and period allowed

Requirements for the upgrade

Equipment version before the upgrade

Equipment version after the upgrade

Requirements for versions of other NEs

Upgrade personnelThe persons that execute the upgrade. Generally, personnel of the office and Huawei are involved.

Related assistantsFor example, maintenance engineers of other NEs and network planning engineers required for the drive test.

Person in charge of the upgradeName and contact number of the person in charge of this upgrade.

xliiiHuawei Proprietary and Confidential 01 (2011-3-25)

_1342618535/Uninstall.rar

Uninstall/UINSTALL_SQLSERVER.bat@net stop "MSSQLSERVER"@cls@cscript //nologo uninstall.vbs@pause

Uninstall/uninstall.vbs

MAIN

Function MAINOn Error Resume NextInfo()bRet = ReadContinue()If bRet = False ThenExit FunctionEnd IfUninstall() End Function

Function ReadContinue()WScript.StdOut.Write("Are you sure to continue this operation? Y/N:")Answer = WScript.StdIn.ReadLine

If Answer = "Y" Or Answer = "y" ThenReadContinue = TRUEElseReadContinue = falseEnd IfEnd Function

Function Uninstall()'Set WshShell2 = CreateObject("WScript.Shell")Set fs = CreateObject("Scripting.FileSystemObject")'Set commonExec = WshShell2.Exec(executeStr)strHost = "."Const HKLM = &H80000002Set objReg = GetObject("winmgmts://" & strHost & _ "/root/default:StdRegProv")Const strBaseKey = _ "Software\Microsoft\Windows\CurrentVersion\Uninstall\"objReg.EnumKey HKLM, strBaseKey, arrSubKeys For Each strSubKey In arrSubKeys intRet = objReg.GetStringValue(HKLM, strBaseKey & strSubKey, _ "DisplayName", strValue) If intRet 0 Then intRet = objReg.GetStringValue(HKLM, strBaseKey & strSubKey, _ "QuietDisplayName", strValue) End If intRet = objReg.GetStringValue(HKLM, strBaseKey & strSubKey, _ "UninstallString", strUninstall)noRet = objReg.GetStringValue(HKLM, strBaseKey & strSubKey, _ "InstallLocation" , StrInstallLocation) If noRet 0 Then noRet = objReg.GetExpandedStringValue(HKLM, strBaseKey & strSubKey, _ "InstallLocation" , StrInstallLocation) End If If (instr(1,strValue,"SQL Server",1) > 0 ) and (intRet = 0) Then WScript.StdOut.WriteLine "Uninstall " + strValue strUninstall = Replace(strUninstall,"/", "/qb /", 1, -1, 1) strUninstall = Replace(strUninstall,"/Remove", "Remove=SQL_Engine", 1, -1, 1) strUninstall = Replace(strUninstall,"ARPWrapper.exe", "Setup.exe") strUninstall = Replace(strUninstall,"/i", "/uninstall ", 1, -1, 1) strUninstall = Replace(strUninstall,"/I", "/uninstall ", 1, -1, 1) WScript.StdOut.WriteLine strUninstall Set commonExec = WshShell2.Exec(strUninstall) ' WScript.StdOut.WriteLine strUninstall Do While commonExec.Status = 0Wscript.Sleep(250) Loop WScript.StdOut.WriteLine "Uninstall " + strValue + "Operation Compelete!" Path = ""&StrInstallLocation If fs.FolderExists(Path) Then DeleteFolder(Path) End If End If If (instr(1,strValue,"MSXML 6.0 Parser",1) > 0 ) and (intRet = 0) Then WScript.StdOut.WriteLine "Uninstall " + strValue strUninstall = Replace(strUninstall,"/", "/qb /", 1, -1, 1) strUninstall = Replace(strUninstall,"/i", "/uninstall ", 1, -1, 1) strUninstall = Replace(strUninstall,"/I", "/uninstall ", 1, -1, 1) Set commonExec = WshShell2.Exec(strUninstall) WScript.StdOut.WriteLine strUninstall Do While commonExec.Status = 0Wscript.Sleep(250) Loop Path = ""&StrInstallLocation If fs.FolderExists(Path) Then DeleteFolder(Path) End If

WScript.StdOut.WriteLine "Uninstall " + strValue + "Operation Compelete!" End If Next WScript.StdOut.WriteLine "Remove RegKeys..."RemoveHKLMReg("Software\Microsoft\MSSQLServer") RemoveHKLMReg("Software\Microsoft\Microsoft SQL Server")RemoveHKLMReg("Software\Microsoft\Windows\CurrentVersion\Setup\ExceptionComponents")RemoveHKLMReg("System\CurrentControlSet\Services\MSSQLServer")RemoveHKLMReg("System\CurrentControlSet\Services\SQLSERVERAGENT")RemoveHKLMReg("System\CurrentControlSet\Services\MSSQLServerADHelper")RemoveHKLMReg("System\CurrentControlSet\Services\MSDTC")WScript.StdOut.WriteLine "Remove RegKeys END"

End Function

Function DeleteFolder(folderPath)On Error Resume Next Set fs = CreateObject("Scripting.FileSystemObject") If folderPath="" Then Exit Function End If If fs.FolderExists(folderPath) Then Set f = fs.GetFolder(folderPath) Set sf = f.SubFolders For Each f1 in sf DeleteFolder(f1.Path) Next ' f.attributes = 0 WScript.StdOut.WriteLine "Delete folder :" + folderPath f.Delete TRUE End If End Function

Function RemoveHKLMReg(KeyPath)const HKEY_LOCAL_MACHINE = &H80000002strComputer = "."Set objReg=GetObject("winmgmts:"_ & "{impersonationLevel=impersonate}!\\" &_ strComputer & "\root\default:StdRegProv")lRC = objReg.DeleteKey(HKEY_LOCAL_MACHINE, KeyPath)If lRC = 5 Then ret = objReg.EnumKey(HKEY_LOCAL_MACHINE, KeyPath, arrSubKeys) If ret = 0 Then For Each subkey In arrSubKeys WScript.StdOut.WriteLine "Remove :" + KeyPath+ "\" + subkey RemoveHKLMReg(KeyPath+ "\" + subkey) Next End If lRC = objReg.DeleteKey(HKEY_LOCAL_MACHINE, KeyPath)End IfEnd Function

Function Info()WScript.StdOut.WriteLine "================================================"WScript.StdOut.WriteLine "Author: zkf17673"WScript.StdOut.WriteLine "Date: 2010-2-5"WScript.StdOut.WriteLine "Warning: This script will automatically remove"WScript.StdOut.WriteLine " the Microsoft SQL Server 2005 and "WScript.StdOut.WriteLine " Microsoft SQL Server 2000 and components"WScript.StdOut.WriteLine " related to them. Please be carefull when"WScript.StdOut.WriteLine " running this script!"WScript.StdOut.WriteLine "================================================"End Function

_1342529680/Windows installer clean up .exe

Documents

CME V200R009C02SPC610 Installation Guide (Standalone CME for Windows)