Professional Documents
Culture Documents
V200R010C00SPC220
Installation Guide (Standalone CME for Windows)
Document
Version
01
Release Date
2010-11-20
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 the warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Telephone:
0755-28560000 4008302118
Fax
0755-28560111
Issue 01 (2010-11-20)
Page 3 of 65
Wang XiaoKang
Date
2010-11-20
Reviewed
By
Date
2010-11-20
Tested By
Cao JiaWu
Date
2010-11-20
Approved
By
Zhang Xiaomao
Date
2010-11-20
Organization
It is recommended that you read the installation guide of this version before using the
iManager M2000-CME (CME for short) V200R010C00SPC220. The following table lists the
contents contained in this document.
Chapter
Description
1Overview
2Preparations
3Installation of the
Standalone CME
4LTE Component
Installation
5GU Component
Installation
6Uninstallation of the
Standalone CME
Issue 01 (2010-11-20)
Page 4 of 65
Chapter
Description
7FAQs
History
Versio
n
Description
Release
Date
V1.00
2010-11-20
Issue 01 (2010-11-20)
Prepared
By
Approve
d By
Page 5 of 65
Contents
1 Overview.................................................................................... 10
1.1 Impacts of the Installation Process on the Existing Program..........................................................................10
1.2 Match Standalone Mode Version.....................................................................................................................10
1.2.1 OS Versions............................................................................................................................................10
1.2.2 Database Version....................................................................................................................................10
1.2.3 Microsoft Office Version........................................................................................................................11
1.2.4 NE Versions............................................................................................................................................11
1.2.5 Mapping Between Software Packages and Versions..............................................................................15
2 Preparations............................................................................... 16
2.1 Obtaining the Software Required for the Installation......................................................................................16
2.2 Installation Precautions....................................................................................................................................16
5 GU Component Installation.........................................................5-1
5.1 Installing a CME Component Corresponding to a GU NE Version...............................................................5-1
7 FAQs......................................................................................... 7-5
7.1 What Should I Do When the System Displays ".Net Framework 2.0 Is not installed" While Installing the
Microsoft SQL Server 2005 Express?..................................................................................................................7-5
7.1.1 Symptom...............................................................................................................................................7-5
7.1.2 Troubleshooting.....................................................................................................................................7-6
7.2 What Should I Do When the System Displays 0x8007007e Error Message While Starting the SQL Server
Configuration Manager?.......................................................................................................................................7-6
7.2.1 Symptom...............................................................................................................................................7-6
Issue 01 (2010-11-20)
Page 6 of 65
Issue 01 (2010-11-20)
Page 7 of 65
Issue 01 (2010-11-20)
Page 8 of 65
8 Version Changes.........................................................................28
8.1.1 Feature Changes.....................................................................................................................................28
10 Appendix..................................................................................32
10.1 Preparation for the Upgrade...........................................................................................................................32
Issue 01 (2010-11-20)
Page 9 of 65
Overview
If the CME V200R010 standalone or integrated mode is installed before, you need to
uninstall it.
You must familiarize yourself with the CME V200R010C00SPC220 Release Notes.
The client software of the standalone mode is also applicable to the integrated mode.
Version Description
Client: Windows XP
Version Description
Issue 01 (2010-11-20)
Page 10 of 65
Version Description
CME client
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
1.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 Type
NE Version
BSC6900
Issue 01 (2010-11-20)
Page 11 of 65
NE Type
NE Version
BSC6900V900R012C01SPC500
BSC6810
BSC6810V200R011C00SPC100
BSC6810V200R010C01B061
BSC6800V100R012C00SPC100
TGW
TGW1000V100R002C01SPC000
MBTS
BTS3900V100R002C00SPC030
BTS3900V100R002C00SPC060
BTS3900V100R002C00SPC070
BTS3900V100R002C00SPC080
BTS3900V100R002C00SPC100
BTS3900V100R002C00SPC120
BTS3900 V100R002C00SPC121
BTS3900 V100R002C00SPC130
BTS3900V100R003C00SPC050
BTS3900V100R003C00SPC060
BTS3900 V100R003C00SPC070
BTS3900 V100R003C00SPC080
BTS3900 V100R003C00SPC100
NodeB
BTS3812E-12AC-12AE-BTS3812AV100R010C01SPC100
BTS3812E-12AC-12AE-BTS3812AV100R011C00SPC200
BTS3812E-12AC-12AE-BTS3812AV100R011C00SPC300
BTS3812E-12AC-12AE-BTS3812AV100R012C00
BTS3812E-12AC-12AE-BTS3812AV100R012C00SPC100
BTS3812E-12AC-12AE-BTS3812AV100R012C00SPC200
DBS3800V100R010C01SPC100
DBS3800V100R010C01SPC200
DBS3800V100R011C00SPC100
DBS3800V100R011C00SPC200
DBS3800V100R011C00SPC300
DBS3800V100R011C00SPC500
DBS3800V100R012C00
DBS3800V100R012C00SPC100
DBS3800V100R012C00SPC200
BTS3900-BTS3900A WCDMA V200R010C01SPC300
BTS3900-BTS3900A WCDMA V200R010C01SPC500
BTS3900-BTS3900A WCDMA V200R011C00SPC100
BTS3900-BTS3900A WCDMA V200R011C00SPC200
Issue 01 (2010-11-20)
Page 12 of 65
NE Type
NE Version
BTS3900-BTS3900A WCDMA V200R011C00SPC300
BTS3900-BTS3900A WCDMA V200R011C00SPC500
BTS3900-BTS3900A WCDMA V200R011C00SPC600
BTS3900-BTS3900A WCDMA V200R011C00SPC700
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC050
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC100
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC200
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC300
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC400
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC500
BTS3900-BTS3900A-BTS3900L WCDMA V200R012C00
BTS3900-BTS3900A-BTS3900L WCDMA V200R012C00SPC100
BTS3900-BTS3900A-BTS3900L WCDMA V200R012C00SPC200
DBS3900 WCDMA V200R010C01SPC300
DBS3900 WCDMA V200R010C01SPC500
DBS3900 WCDMA V200R011C00SPC100
DBS3900 WCDMA V200R011C00SPC200
DBS3900 WCDMA V200R011C00SPC300
DBS3900 WCDMA V200R011C00SPC500
DBS3900 WCDMA V200R011C00SPC600
DBS3900 WCDMA V200R011C00SPC700
DBS3900 WCDMA V200R011C01SPC050
DBS3900 WCDMA V200R011C01SPC100
DBS3900 WCDMA V200R011C01SPC200
DBS3900 WCDMA V200R011C01SPC300
DBS3900 WCDMA V200R011C01SPC400
DBS3900 WCDMA V200R011C01SPC500
DBS3900 WCDMA V200R012C00
DBS3900 WCDMA V200R012C00SPC100
DBS3900 WCDMA V200R012C00SPC200
BTS3900-1U WCDMA V200R010C01SPC300
BTS3900-1U WCDMA V200R010C01SPC500
BTS3900-1U WCDMA V200R011C00SPC100
BTS3900-1U WCDMA V200R011C00SPC200
BTS3900-1U WCDMA V200R011C00SPC300
BTS3900-1U WCDMA V200R011C00SPC500
BTS3900-1U WCDMA V200R011C00SPC600
BTS3900-1U WCDMA V200R011C00SPC700
BTS3900-1U WCDMA V200R012C00
BTS3900-1U WCDMA V200R012C00SPC100
Issue 01 (2010-11-20)
Page 13 of 65
NE Type
NE Version
BTS3900-1U WCDMA V200R012C00SPC200
DBS3900-1U WCDMA V200R010C01SPC300
DBS3900-1U WCDMA V200R010C01SPC500
DBS3900-1U WCDMA V200R011C00SPC100
DBS3900-1U WCDMA V200R011C00SPC200
DBS3900-1U WCDMA V200R011C00SPC300
DBS3900-1U WCDMA V200R011C00SPC500
DBS3900-1U WCDMA V200R011C00SPC600
DBS3900-1U WCDMA V200R011C00SPC700
DBS3900-1U WCDMA V200R012C00
DBS3900-1U WCDMA V200R012C00SPC100
DBS3900-1U WCDMA V200R012C00SPC200
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC600
BTS3900-BTS3900A-BTS3900L WCDMA V200R011C01SPC700
BTS3900-BTS3900A-BTS3900L WCDMA V200R012C00SPC300
DBS3900 WCDMA V200R011C01SPC600
DBS3900 WCDMA V200R011C01SPC700
DBS3900 WCDMA V200R012C00SPC300
BTS3900-1U WCDMA V200R012C00SPC300
DBS3900-1U WCDMA V200R012C00SPC300
LTE
Issue 01 (2010-11-20)
Page 14 of 65
NE Type
NE Version
need to be installed.)
BTS3900L LTE V100R002C00SPC200 (Corresponding components
need to be installed.)
DBS3900 LTE V100R002C00SPC210 (Corresponding components
need to be installed.)
BTS3900 LTE V100R002C00SPC210 (Corresponding components
need to be installed.)
BTS3900A LTE V100R002C00SPC210 (Corresponding components
need to be installed.)
BTS3900L LTE V100R002C00SPC210 (Corresponding components
need to be installed.)
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, BSC600, BSC6810, MBTS, and NodeB.
The logic based on which the CME manages eNodeBs rests in the LTE mediation. For details about how
to install the LTE mediation, see 4LTE Component Installation.
Version
Setup.exe
CME V200R010C00SPC220
SQLEXPR32_sp3_ENU.EXE
Install.bat
CMEComponent_MBSC6900V9R11SPC700.e
xe
BSC6900V900R011C00SPC700
CMEComponent_BSC6900V900R012C01SPC
300.exe
BSC6900V900R012C01SPC300
CMEComponent_BSC6000V901R008C00T.ex
e
BSC6000V901R008C00T
CME_COMPONENT_LTE_V200R010C00SP
C002.tar.gz
CME_COMPONENT_LTE_V200R010C00SP
C003.tar.gz
Issue 01 (2010-11-20)
Page 15 of 65
CME_COMPONENT_LTE_V200R010C00SP
C004.tar.gz
CME_COMPONENT_LTE_V200R010C00SP
C005.tar.gz
Preparations
Description
CME
Software
setup.exe
\MSDE_Install\
MSDE
Software
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.
Issue 01 (2010-11-20)
Page 16 of 65
Apply license file from Huawei Technology Support Website http://support.huawei.com. The
detailed path is SUPPORT > NOTICE > Software Bulletin. Then, search for the WCDMA
RNC&NodeB&CME product common license notice.
The CME standalone version can be installed only on an operating system of simplified
Chinese or English version.
Before installing the standalone CME V200R010C00, 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. The .net Framework2.0 installation package is
available in the dotNet Framework 2.0 folder in the installation CD-ROM of the
Microsoft SQL Server 2005 Express.
If you have installed the standalone or integrated CME client on the local PC, uninstall
the CME client first.
PC type
Configuration
Windows XP (The
recommend configuration)
Issue 01 (2010-11-20)
Page 17 of 65
It takes about three minutes to install the SQL Server. After the installation, it takes about
eight minutes to install the standalone CME client.
Issue 01 (2010-11-20)
Page 18 of 65
----End
Issue 01 (2010-11-20)
Page 19 of 65
The standalone CME can be installed only in the Windows operating system. Therefore,
do not install the standalone CME in other environments.
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.
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.
If you change the default port to another port, you need to add the port number when run the
Double-click Setup.exe in the folder of the Windows resource manager. Do not use tools
such as Total commander.
Step 1 Copy the installation package from the installation disk to a drive on the local PC.
Step 2 Open the installation package of the CME client, and then double-click
CME_Install /setup.exe. A dialog is displayed, prompting you to select the language of the
program. Choose Chinese (Simplified) or English, as shown in Figure 1.1.
Figure 1.1 Selecting the language
Step 3 After you click Next, the dialog box is displayed, as shown in Figure 1.1, prompting you to
confirm the installation.
Issue 01 (2010-11-20)
Page 20 of 65
Step 4 Click Next. The License Agreement dialog box is displayed, as shown in Figure 1.1.
Issue 01 (2010-11-20)
Page 21 of 65
Step 5 If you accept the terms in the license agreement, click Yes. Then, a dialog box shown in
Figure 1.1 is displayed, prompting you to enter the user information which includes User
Name, Company Name, and Serial Number. If you do not accept the terms, click Cancel to
cancel the installation.
Issue 01 (2010-11-20)
Page 22 of 65
Issue 01 (2010-11-20)
Page 23 of 65
Step 6 Click Next. A dialog box shown in Figure 1.1 is displayed, prompting you to specify the
destination folder.
Figure 1.1 Specifying the destination folder
Issue 01 (2010-11-20)
Page 24 of 65
Step 7 Specify the destination folder and then click Next. A dialog box shown in Figure 1.1 is
displayed, prompting you to confirm the installation of the components. Select both of CME
Client and Client Assistant Daemon. Click Next.
Figure 1.1 Components to be installed
Step 8 Enter the MSDE database user name and password and port (default value is sa,
emsems,1433), and then click Next, as shown in Figure 1.1.
Issue 01 (2010-11-20)
Page 25 of 65
Step 9 A dialog box is displayed, indicating that the wizard is ready to begin the installation.
Figure 1.1 Wizard ready for the installation
Issue 01 (2010-11-20)
Page 26 of 65
Step 10 Click Install to start the installation. The progress of installing the data files is displayed, as
shown in Figure 1.1.
Figure 1.1 Installation progress
Step 11 After the installation, the mediation model initialization is displayed, as shown in Figure 3-12.
The system will install database automatically.
Figure 1.1 Mediation Model Initialization
Step 12 Click Finish to complete the installation and restart the computer.
When you need use F1 Help, Download the Hedex of the Windows version from software site
http://support.huawei.com/support/pages/editionctrl/catalog/ShowVersionDetail.do?
actionFlag=clickNode&p_line=&node=000001442079&colID=ROOTENWEB|
CO0000000174&
which interface is HedEx V100R002C00SPC002 for Windows.zip.
If you require the NE parameter reference, download the reference from CME release
document site which interface is like NE Parameter Reference, and copy to the CME
Issue 01 (2010-11-20)
Page 27 of 65
----End
Issue 01 (2010-11-20)
Page 28 of 65
Note:
If you need to configure LTE NEs on the standalone CME, you need to install the LTE
Component. If you do not need to configure LTE NEs, you can skip this chapter.
Do not terminate the install component application to guarantee LTE mediation datas consistency.
Issue 01 (2010-11-20)
Page 29 of 65
Step 2 Click Add Files and then select a component file in the displayed window.
Step 3 After a component file is selected, click Install in the displayed dialog box.
Issue 01 (2010-11-20)
Page 30 of 65
Issue 01 (2010-11-20)
Page 31 of 65
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.4NE Versions.
Issue 01 (2010-11-20)
Page 1 of 65
Step 3 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.
Issue 01 (2010-11-20)
Page 2 of 65
Issue 01 (2010-11-20)
Page 3 of 65
Step 2 Select the CME, and then click Change or Remove and confirm the operation.
Figure 1.1 Confirmation for removing the CME
Step 4 After the uninstallation is complete, check that the CME is removed from Control Panel.
Issue 01 (2010-11-20)
Page 4 of 65
----End
Issue 01 (2010-11-20)
Page 5 of 65
FAQs
7.1.2 Troubleshooting
Install the NetFx20SP1_x86.exe program in the MSDE_Install\dotNet Framework 2.0
directory.
7.2.2 Troubleshooting
Copy the framedyn.dll file from C:\WINDOWS\system32\wbem\ to
C:\WINDOWS\system32\.
Issue 01 (2010-11-20)
Page 6 of 65
Note: If the root disk of Windows installation directory is in other disks, copy the file to the
system32 directory in the corresponding disk.
7.3.2 Troubleshooting
Run the Database Parameter Management.exe file in the \CME\Bin directory to modify
the configuration parameters.
Issue 01 (2010-11-20)
Page 7 of 65
7.4.2 Troubleshooting
Step 1 Check whether the port of SQL Server 2005 is static port.
1.
2.
Select the used instance, as shown in Figure 1.2. Then, double-click TCP/IP.
Figure 1.2 Selecting the used instance
3.
Issue 01 (2010-11-20)
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 7.5"How Should I Use the Static Port Instead."
Page 8 of 65
----End
Step 2 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."
Issue 01 (2010-11-20)
Page 9 of 65
7.5.2 Troubleshooting
Step 1 Open the TCP/IP Properties dialog box in which the instances need to be configured by
referring to 7.4.2 IStep 1"Check whether the port of SQL Server 2005 is static port." in
section 7.4"How Should I Check Whether the Port Used in the SQL Server 2005 is Static
Port?"
Step 2 Disable all the configured TCP dynamic ports, and then change the TCP port number to the
specified number.
Step 3 After the configuration, restart the SQL Server.
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 1.1 shows the template.ini file after the modification.
Issue 01 (2010-11-20)
Page 10 of 65
Issue 01 (2010-11-20)
Page 11 of 65
Issue 01 (2010-11-20)
Page 12 of 65
7.7.2 Troubleshooting
Step 1 Click Cancel in the dialog box shown in 7.7.1 IStep 1Figure 1.1,
Step 2 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 3 Perform the one-click installation again and type the correct password when required.
----End
7.8.2 Troubleshooting
Step 1 Double-click My Computer and find the path where the SQL Server is installed, for example,
in disk C.
Step 2 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 1.1.
Issue 01 (2010-11-20)
Page 13 of 65
Issue 01 (2010-11-20)
Page 14 of 65
Step 3 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.
----End
Step 3 If you need to start the SQL Server service, run the net start MSSQLServer command, as
shown in Figure 1.1.
Figure 1.1 Running the net start MSSQLServer command
----End
Step 2 In the displayed Backup/Restore cmedb dialog box, click Backup or Restore to perform the
relevant operations.
Issue 01 (2010-11-20)
Page 15 of 65
----End
7.12.2 Troubleshooting
Run the regsvr32 vbscript.dll command for registration.
Figure 1.1 Running the vbscript.dll program
Issue 01 (2010-11-20)
Page 16 of 65
7.13.2 Troubleshooting
The installation path of Windows Installer 3.1 is
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=889482FC5F56-4A38-B838-DE776FD4138C
7.14.2 Troubleshooting
Uninstall the pre-installed CME and then reinstall the CME. And select the server components
while installing the CME.
7.15.2 Troubleshooting
Step 1 Enable writing caching on the disk.
1.
Issue 01 (2010-11-20)
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 1.1.
Page 17 of 65
2.
Issue 01 (2010-11-20)
Click the Hardware tab, and then select the hard disk drive whose writing caching you
want to enable.
Page 18 of 65
3.
Issue 01 (2010-11-20)
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.
Page 19 of 65
Issue 01 (2010-11-20)
Page 20 of 65
Issue 01 (2010-11-20)
Page 21 of 65
7.16.2 Troubleshooting
Run the resgvr32 command to register the sqloledb.dll file in the C:\Program Files\Common
Files\System\Ole DB\ path, as shown in Figure 1.1.
Figure 1.1 Registering the sqloledb.dll file
7.17.2 Troubleshooting
Save 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=CMECurRead
Issue 01 (2010-11-20)
Page 22 of 65
Note: 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.
7.18.2 Cause
The Microsoft SQL Server2005 is not installed by strictly following the instructions in the
upgrade guide.
7.18.3 Troubleshooting
Uninstall the Microsoft SQL Server 2005, and then re-install it by referring to section
3.2"Installing the SQL Server."
Issue 01 (2010-11-20)
Page 23 of 65
7.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.
7.20.3 Troubleshooting
Stop the Hedex services, and then delete the Help_cme.hdx file.
Issue 01 (2010-11-20)
Page 24 of 65
7.21.2 Cause
The 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.
7.21.3 Troubleshooting
Click OK.
Issue 01 (2010-11-20)
Page 25 of 65
7.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.
7.22.3 Troubleshooting
Navigate to the installation path of the SQL Server, and then modify the INSTALLSQLDIR
parameter in the template.ini configuration file.
7.23.2 Cause
Licenses adopt A.D time, for example, 2010-01-01.
7.23.3 Troubleshooting
Change the system time in the PC to A.D. time.
Issue 01 (2010-11-20)
Page 26 of 65
7.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:
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.
Issue 01 (2010-11-20)
Page 27 of 65
7.24.3 Troubleshooting
Step 1 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 2 Uninstall the SQL server by running uninstall.bat.
Step 3 Restart the PC and then install the SQL Server again.
7.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.
7.25.3 Troubleshooting
Clear the installation directory of the CME, and then re-install the CME.
7.26.2 Cause
The CmeServer service is not registered.
Issue 01 (2010-11-20)
Page 28 of 65
7.26.3 Troubleshooting
Run Server\Bin\RegisServer.bat to register the CmeServer service, and then restart the
CME.
7.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.
7.27.3 Troubleshooting
Open the Windows task manager and stop suspended programs such as mstsc.
7.28.2 Cause
According to the explanation of the Microsoft, the SQL Server 2005 software conflicts with
the Windows XP operating system.
7.28.3 Troubleshooting
Upgrade Windows XP to Windows XP Service Pack 3.
Issue 01 (2010-11-20)
Page 29 of 65
Version Changes
New Features
1.
The function of exporting EDS files of LTE NEs is added to the CME in standalone
mode.
Description
The function of exporting EDS files of LTE NEs is added to the CME
in standalone mode.
Improvement
The CME in standalone mode can export EDS files of LTE NEs.
Implementati
on
Related
Operation
PR Number
None
Feature ID
Basic feature.
2.
The function of importing EDS files of LTE NEs is added to the CME in standalone
mode.
Description
The function of importing EDS files of LTE NEs is added to the CME
in standalone mode.
Improvement
The CME in standalone mode can import EDS files of LTE NEs.
Implementati
on
Issue 01 (2010-11-20)
Page 30 of 65
Related
Operation
PR Number
None
Feature ID
Basic feature.
3.
The function of adding an LTE NE through an XML file is added to the CME in
standalone mode.
Description
Improvement
Implementati
on
Related
Operation
Select the XML file of an LTE NE, and then add the LTE NE.
PR Number
None
Feature ID
Basic feature.
4.
The script executor automatically identifies the NEs in the project configuration file
exported from the CME in standalone mode.
Description
Improvement
The script executor can identify the NEs by FDN or NE name in the
project configuration files exported from the CME in standalone
mode.
Implementati
on
When loading scripts, the script executor can identify NEs by FDN
and by NE name.
Related
Operation
1. Export the project of the script executor, that is, script.zip, from the
CME in standalone mode.
2. Replace dss170 in "<Script taskId="1" neName="dss170" ...>" 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 then activate the project.
PR Number
DTS2010071601222
Feature ID
Basic feature.
5.
Issue 01 (2010-11-20)
Page 31 of 65
PR Number
Feature ID
Parameter comparison.
Issue 01 (2010-11-20)
Page 32 of 65
10
Appendix
Descriptio
n
Remarks
Related assistants
Issue 01 (2010-11-20)
Page 33 of 65