Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page i, Total 38

Product Name Confidentiality
OMStar INTERNAL
Product Version
38 Pages OMStar V500R006


Maintenance Guide to OMStar V500R006
(For internal use only)



Prepared by: Jia Xiaorun Date: 2011-07-24
Reviewed by: Date:
Approved by: Date:



Huawei Technologies Co., Ltd.
All Rights Reserved





Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page ii, Total 38

Contents
Huawei Technologies Co., Ltd. .................................................................................................. i
1 Problems Related to the SQL Server ..................................................................................... 5
1.1 Problems Related to the SQL Server Installation ........................................................................................ 5
1.1.1 Version Mapping Between the Operating System and the Database .................................................... 5
1.1.2 Can the MSDE 2000 Be Used? ......................................................................................................... 5
1.1.3 Can the OMStar Share the Database with the CME? .......................................................................... 5
1.1.4 How Do I Install SQL Server 2000 on a Server That Is Installed with SQL Server 2005? ................... 6
1.1.5 What Are the Precautions for Installing the SQL Server in the Windows 7 Operating System? ........... 8
1.1.6 What Do I Do When the System Displays the Message "A previous program installation created
pending file operations on the installation machine"? ................................................................................10
1.1.7 What Do I Do When the System Displays the Message "The installation program fails to configure the
server"? ....................................................................................................................................................10
1.1.8 What Do I Do When the System Displays the Message "command line option syntax error"?............ 11
1.1.9 What Do I Do If the GUI is Suspended During Installation? ............................................................. 11
1.1.10 Confirming the Patch Version and Checking Whether the Collation Setting Is Correct ..................... 11
1.2 Problems Related to the SQL Server Connection .......................................................................................13
1.2.1 SQL Server Service Not Started .......................................................................................................13
1.2.2 Incorrect Database Instance Being Selected When the OMStar Is Logged In To ................................14
1.2.3 Incorrect Server Name for Logging In to the Database ......................................................................14
1.2.4 Incorrect User Name or Password for Logging In to the Database .....................................................15
1.2.5 Invalid Connection or Common Network Error ................................................................................16
1.2.6 SQL Server Start Failure After the Domain Password Is Changed .....................................................17
2 Problems Related to the NIC ................................................................................................ 19
2.1 How Do I Handle the NIC Install Failure? .................................................................................................19
2.2 How Do I Handle the NIC Startup Failure? ...............................................................................................19
2.3 How Do I Handle the Failure of Adding NEs to the NIC? ..........................................................................19
2.4 Why Does the System Display the Message "Adaptation layer does not match the C version of the NE"
When the User Adds an NE?...........................................................................................................................20
2.5 Data Collection Failure Scenarios (Configuration Data, Traffic Statistics Data, and MML Data) ................20
2.6 Why Does It Take Time for the NIC to Collect Inspection Data?................................................................20
2.7 How Do I Add NEs More Efficiently by Using the Batch Import Function? ...............................................21
2.8 Why Does the System Display the Message "Please check whether the NIC application services and the
database services run normally." During Batch Management of NEs? ..............................................................23
2.9 What Is the Maximum Number of NEs Whose Data Is Collected Concurrently on the NIC? ......................23
2.10 What Do I Do If the Data Collection Fails? .............................................................................................24
2.11 What Do I Do If the Internet Explorer Does Not Respond? ......................................................................24
3 Problems Related to the Transdata ...................................................................................... 25
3.1 System Prompting Incorrect Program Configuration at Startup of the Transdata .........................................25
3.2 System Prompting Project Information Loading Failure and Invalid Parameters at Startup of the Transdata 25
3.3 Exceptions That May Occur During the Data Import of the Transdata ........................................................25
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page iii, Total 38

3.4 Alarm Data Failing to Be Imported ...........................................................................................................26
3.5 Transdata task dose not respond in Windows 7 ............................................ Error! Bookmark not defined.
3.6 Supported Format of Imported NodeB Traffic Statistics .............................................................................27
4 Problems Related to Mini_OMStar ..................................................................................... 28
4.1 How Do I Handle the Failure to Start the Mini-OMStar Because vcredist.exe Is Not Installed? ..................28
4.2 Why Does the System Display the Information Indicating That Transdata Is Started or Fails to Be Started
After the Mini_OMStar Starts a Task? ............................................................................................................28
4.3 Why Does the Mini-OMStar Fail to Create a Project? ................................................................................29
4.4 How Do I Handle the Problem That the Task Is in the Stopping State for a Long Time After the
Mini-OMStar Stops the Task? .........................................................................................................................32
4.5 How Do I Back Up Tasks Created by the Mini-OMStar After the OMStar Program Is Uninstalled? ............32
5 Problems Related to OMStar ................................................................................................ 33
5.1 The Map Cannot Be Displayed Correctly ..................................................................................................33
5.2 Failure to Load Report Node .....................................................................................................................33
5.3 What Do I Do If a Task Fails to Be Executed Because the Word Program Is Abnormal? .............................34
5.4 Task Manager Popping Up Occasionally When the Tool Is Generating Reports ..........................................34
5.5 Why Am I Not Allowed To Use the Copy/Paste Function of Windows During the Process of OMStar Word
Report Generation? ........................................................................................................................................34
5.6 Is the OMStar Compatible with Office 2007? ............................................................................................35
6 Miscellaneous ......................................................................................................................... 36
6.1 What Are the Precautions for Installing the OMStar in the Windows 7 Operating System? .........................36
6.2 OMstar running stop caused by automatic sleep in Windows 7 ..................................................................37
6.3 Problems of Using OMStar V500R006 on Windows 2003 Server ..............................................................38
6.4 Obtaining OMStar Logs in One-Key Mode ...............................................................................................38
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 4, Total 38



Operation Guide to the OMStar V500R006 for Maintenance
Key Word
SQL server, NIC, Transdata, Mini_OMStar, OMStar
Abstract
This document describes the FAQs that occur during the installation and using of OMStar
V500R006 and the NE information collector (NIC). In addition, this document provides the
solutions on the FAQs. In case of any question during the installation and the using of the
tools, see the maintenance manual. If the question cannot be handled by using the
maintenance manual, contact tool maintenance personnel Jia Xiaorun (ID: 00151470) for
assistance.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 5, Total 38

1 Problems Related to the SQL Server
1.1 Problems Related to the SQL Server Installation
1.1.1 Version Mapping Between the Operating System and the
Database
OS Version Database Version Remarks
Windows Server 2003
Standard Edition
SQL Server 2000, Standard
Edition (SP4)
The installation and upgrade
can be performed.
Windows Server 2003
Enterprise Edition
SQL Server Enterprise
Edition (SP4)
The installation and upgrade
can be performed.
Windows XP SQL Server 2000
personalized edition (SP4)
The installation and upgrade
can be performed.
Windows 7 SQL Server 2000
personalized edition (SP4)
The installation and upgrade
can be performed.


The preceding configuration is the recommended standard configuration.
1.1.2 Can the MSDE 2000 Be Used?
1. The MSDE 2000 is equivalent to a lite edition of SQL Server 2000 with the limited
specification (the performance decreases abruptly when the size of a single table exceeds
2 GB). The MSDE 2000 is not recommended especially when the performance
measurement data collected from a single BSC exceeds 150 MB.
2. If the conditions for installing the SQL Sever 2000 are not met but users can take the low
efficiency risks caused by the MSDE, the GENEX MSDE program must be installed.
The GENEX MSDE program can be downloaded from the following URL:
http://support.huawei.com/support/pages/editionctrl/catalog/ShowVersionDetail.do?actio
nFlag=getDetail&node=000001423430&colID=ROOTENWEB|CO0000000174.
3. The MSDEs of other vendors may not be applicable to normal analysis of the OMStar.
1.1.3 Can the OMStar Share the Database with the CME?
The database for the OMStar is incompatible with that for the CME.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 6, Total 38

Cause:
The CME uses SQL Server 2005 Express. SQL Server 2005 Express does not support the
import of multiple threads. Therefore, the OMStar cannot use it.
Solution:
The OMStar supports that SQL Server2000 and SQL Server 2005 are installed on the same
server. For details about the installation method and precautions, see section 1.1.4 "How Do I
Install SQL Server 2000 on a Server That Is Installed with SQL Server 2005?"
Except SQL Server 2000, the OMStar can support the SQL Server 2005 Standard and SQL
Server 2005 Express, which is only compatible with the Windows Server 2003 and later
versions.
1.1.4 How Do I Install SQL Server 2000 on a Server That Is
Installed with SQL Server 2005?
SQL Server2000 and SQL Server 2005 must use different instance names. When installing
SQL Server 2000, you must specify an instance name under Instance name, as shown the
following figure.


If the server is installed with the SQL Server 2005 database, check whether SQL Server 2005
uses the default port, 1433.
To check the port used by SQL Server 2005, choose Start > All Programs > Microsoft SQL
Server 2005 > Configuration Tools > SQL Server Configuration Manager > SQL Server
2005 Network Configuration > Protocols for MSSQLSERVER.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 7, Total 38



Double-click TCP/IP and click the IP Address tab in the displayed dialog box.


SQL Server 2000 must use a port different from that used by SQL Server 2005. For example,
set Port number to 1434 for SQL Server 2000.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 8, Total 38



After SQL Server 2000 is installed, the SQL Server 2005 instance maps the MSSQL.1 folder
and the SQL Server 2000 instance maps the MSSQL$mss folder in the SQL Server
installation directory. Set the SQL Server instance name in the Login Server dialog box, as
shown in the following figure.


1.1.5 What Are the Precautions for Installing the SQL Server in
the Windows 7 Operating System?
The SQL Server 2000 that is compatible with the Windows XP operating system may not be
installed properly in the Windows 7 operating system. Do not install the SQL Server by
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 9, Total 38

double-clicking autorun.exe in the installation package; otherwise the following error message
is displayed:


To solve the problem, do as follows: Double-click setup.bat in the installation package. The
Program Compatibility Assistant dialog box is displayed twice informing that this program
has known compatibility issues. Click Run program. The follow-up operations are the same
as those performed in the Windows XP operating system. The error message displayed during
installation can be ignored. Database errors are not encountered temporarily.


Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 10, Total 38

1.1.6 What Do I Do When the System Displays the Message "A
previous program installation created pending file operations on
the installation machine"?


Cause:
This error usually occurs when the SQL Server is uninstalled and then reinstalled.
Solution:
Delete the key value "PendingFileRenameOperation" in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager of
the registry.
1.1.7 What Do I Do When the System Displays the Message "The
installation program fails to configure the server"?
Cause 1:
The previously installed SQL Server 2000 is uninstalled incompletely.
Solution:
Delete the Microsoft SQL Server folder in C:\Program Files.
Find "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server"
in the registry and delete it.
Cause 2:
The name of the PC running Windows contains lower-case letters.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 11, Total 38

Solution:
The SQL Server 2000 fails to be installed when the name of the PC running Windows
contains some or only lower-case letters, with the message of general network error in the
sqlstp.log file.
To solve this problem, change the lower-case letters to upper-case letters. For example, to
change the PC name from jys0800964 to JYS0800964, do as follows:
Open the registry (by running the regedit command in the Run window), find
"HKEY_LOCAL_MACHINE\System\CurrenControlSet\Control\ComputerName\ComputerN
ame" and
"HKEY_LOCAL_MACHINE\System\CurrenControlSet\Control\ComputerName\ActiveCom
puterName", and then change the primary key value of 'ComputerName' from jys0800964 to
JYS0800964. Then, log out the user or restart the system to make the modification take effect.
1.1.8 What Do I Do When the System Displays the Message
"command line option syntax error"?


Cause:
The cause of this error is that the name of the directory for saving the source files of the SQL
Server installation package contains Chinese characters. In this case, the SQL Server can be
installed successfully after you click OK, but the OMStar fails to connect to the database.
Solution:
Ensure that the name of the directory for saving source files of the SQL Server does not
contain any Chinese character.
1.1.9 What Do I Do If the GUI is Suspended During Installation?
Cause:
The version of the database does not match with that of the operating system.
Solution:
The SQL Server 2000 Personal Edition should be installed for Windows XP. Check whether
the SQL Server Standard Edition or Enterprise Edition is installed on Windows XP (the two
editions can be installed only on Windows Server 2000 or Windows Server 2003).
1.1.10 Confirming the Patch Version and Checking Whether the
Collation Setting Is Correct
To check the patch version and collation setting, perform the following steps:
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 12, Total 38

Step 1 Choose Start > Program > Microsoft SQL Server > Enterprise Manager.
The Console Root window is displayed, as shown in Figure 1-1.
Figure 1-1 Console Root window


In the Console Root window, choose Tree > SQL Server Group > xxxx (Windows NT).
Right-click xxxx (Windows NT), and choose Properties.
The SQL Server Properties window is displayed, as shown in Figure 1-2.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 13, Total 38

Figure 1-2 SQL Server Properties window


In the SQL Server Properties dialog box, check whether the Product version and Server
collation fields are correct..
----End
1.2 Problems Related to the SQL Server Connection
1.2.1 SQL Server Service Not Started
Solution:
Check whether the server is started in the SQL Server Service Manager window. If the
server is not started, start it.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 14, Total 38



1.2.2 Incorrect Database Instance Being Selected When the
OMStar Is Logged In To
Solution:
Multiple database instances are configured on certain devices. Check whether the name of the
selected database instance is correct when logging in to the OMStar. You can view all
installed database instances by using the SQL server service manager to ensure that the
incorrect database instance is selected when you log in to the OMStar.


1.2.3 Incorrect Server Name for Logging In to the Database
Solution:
Verify that the typed server name is correct. Note that the only the slash "\" can be contained
in the server name. The following figure shows the incorrect server name:
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 15, Total 38



1.2.4 Incorrect User Name or Password for Logging In to the
Database
Solution:
Solution 1: Verify that the user name or password for logging in to the database is correct.
Solution 2: If you forget the user name or password, perform the following steps to modify
the user name or password:
Step 1 Choose Microsoft SQL Server > Enterprise Manager.


Step 2 In the SQL Server Enterprise Manager window, choose Microsoft SQL Servers >
SQL Server Group > (local) (Windows NT) > Security > Logins from the left
navigation tree to view the names of users that have logged in to the database. To modify
the password of a user, right-click a user in the right pane and choose Properties from the
shortcut menu. To create a new user, right-click a user in the right pane and choose New
Login from the shortcut menu.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 16, Total 38



----End
1.2.5 Invalid Connection or Common Network Error
Either of the following log is recorded in the WCDMA\UNP\Log\...\ofc.log file:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]invalid connection or
[Microsoft][ODBC SQL Server Driver][DBNETLIB]common network error.
Solution:
Solution 1: Open the configuration manager, and then double-click TCP/IP to view the
TCP/IP configuration.


Check that the TCP dynamic port is left blank.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 17, Total 38



Solution 2: Restart the service by using the service manager. Note that you need to perform
this operation several times to solve this problem.
1.2.6 SQL Server Start Failure After the Domain Password Is
Changed
Solution:
Choose Control Panel > Management Tools > Services. In the displayed window,
right-click MSSQLSERVER and choose Properties from the shortcut menu. Then, click the
Login tab and change the password to the password of the current domain user.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 18, Total 38



Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 19, Total 38

2 Problems Related to the NIC
2.1 How Do I Handle the NIC Install Failure?
1. The NIC tool can only support installed in Chinese or English operating system, and
other small language operating systems do not support.
2. Installation user must have Administrator privileges
2.2 How Do I Handle the NIC Startup Failure?
1. At present, the ports conflict between the M2000 client and the NIC. Therefore, disable
the M2000 client before starting the NIC.
2. For other causes, send the log information to R&D engineers for troubleshooting.
2.3 How Do I Handle the Failure of Adding NEs to the
NIC?
1. Check whether the user name and password are correct, that is, check whether the login
by using the LMT succeeds.
2. Check whether the IP address in FTP Server Configuration is consistent with the IP
address of the PC.
If the IP addresses are inconsistent, modify them and restart the NIC to make the
modification take effect. (Caution: Restart the NIC program without restarting the
Internet Explorer.)
3. Check Mediation layer manager to ensure that mediation matching the version of the
NE whose data needs to be collected has been installed.
4. For other causes, send the log information to development engineers for troubleshooting.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 20, Total 38

2.4 Why Does the System Display the Message
"Adaptation layer does not match the C version of the
NE" When the User Adds an NE?
1. This error is a type of NE adding failures. Check whether the mediation matching the NE
version is installed.
2. If the mediation matching the NE version is installed, the possible cause is that the NIC
of Chinese version has been manually installed with the mediation of English version.
2.5 Data Collection Failure Scenarios (Configuration
Data, Traffic Statistics Data, and MML Data)
1. If the NIC fails to be connected to NEs, check whether the FTP Server of the NIC is
disabled.
Do not disable the FTP Server during startup or running of the NIC.
2. Check whether the IP address in FTP Server Configuration is consistent with the IP
address of the PC.
If the IP addresses are inconsistent, modify them and restart the NIC to make the
modification take effect. (Caution: Restart the NIC program without restarting the
Internet Explorer.)
3. Check whether the user has the operation right.
It is recommended to collect data as user admin; otherwise, the collection may fail due
to lack of rights for certain collection items.
Check whether the user is authorized to operate MML commands. If the user is not
authorized to operate MML commands, collecting configuration data and MML data
may fail.
Check whether the user is authorized to back up configuration files. If the user is not
authorized to back up configuration files, collecting configuration files may fail.
Check whether the user is authorized to run the BIN command. If the user is not
authorized to run the BIN command, collecting traffic statistics data may fail.
2.6 Why Does It Take Time for the NIC to Collect
Inspection Data?
1. Check whether the BSC6000 mediation of the NIC V100R006C00T downloaded from
http://support.huawei.com.
2. Check whether the default SOP scenario of the NIC is used for collection (it is
unnecessary to collect the massive data such as logs for inspection or SOP).
3. At present, the NIC reports the progress according to collection items. The execution
sequence of the collection items may change each time a task is created. If the amount of
the data collected by the first collection item is large, the required time is longer and
displayed as X%.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 21, Total 38

4. The execution sequence of collection items may change each time a task is created.
When the items with a small amount of data are collected in priority, it seems that the
collection becomes faster.
5. If the collection progress does not change for a long time, send the log information to
R&D engineers to check whether the NIC still collects data.
2.7 How Do I Add NEs More Efficiently by Using the
Batch Import Function?
1. Choose NE Management > NE Information Maintenance, and click Batch Manage.


2. In the Batch Manage window, click Download Template to save the template to the
local PC.


3. Open the batch import template (XLS file) downloaded to the local PC and generate an
XML file according to the description.
The generated XML file is saved in the NE List folder in the same-level directory as the
XLS template.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 22, Total 38



4. In the Batch Manage window, click Browse, select the .xml file, and then click Import.


5. After the XML file is imported, click OK.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 23, Total 38



2.8 Why Does the System Display the Message
"Please check whether the NIC application services
and the database services run normally." During
Batch Management of NEs?
It is a bug of the NIC V100R005C00SPC200. This error occurs when the imported .xml file
contains Chinese characters because the default XML code is UTF-8. You can use either of
the following methods to solve this problem:
Modify the NE name to contain only English characters.
Modify the XML code to GB2312.
If you have any question, contact R&D engineers.
2.9 What Is the Maximum Number of NEs Whose
Data Is Collected Concurrently on the NIC?
NIC V100R006C00T and earlier versions:
1. The maximum number of multiple collection tasks running concurrently on the NIC is
10.
2. The maximum number of NEs whose data is collected concurrently in a single collection
task is 5.
3. The maximum number of NEs (including BSCs/RNCs and BTSs/NodeBs) created in a
single collection task is 100.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 24, Total 38

Versions later than the NIC V100R006C00T:
1. The maximum number of multiple collection tasks concurrently running on the NIC is 5.
2. The maximum number of NEs whose data is collected concurrently in a single collection
task is 10.
3. The maximum number of NEs (including BSCs/RNCs and BTSs/NodeBs) created in a
single collection task is 250.
To sum up, the maximum number of NEs whose data is collected concurrently on the
NIC is 50.

Currently, the data for maintenance SOP is collected only from BSCs or RNCs.
2.10 What Do I Do If the Data Collection Fails?
If the acquisition task has been completed, but some of the network element or part of
the data collection fails, you can use the fill mining function acquisition.
In the Task Manager screen, select the task to make mining and choose to make mining.

This feature NIC V1R6C00SPC100T and later versions, NIC V1R6C00T and earlier do not have this
feature.
2.11 What Do I Do If the Internet Explorer Does Not
Respond?
Cause:
This problem occurs because users installed other versions of NIC, and the buffer information
in the Internet Explorer is not cleared.
Solution:
Clear the buffer information in the Internet Explorer as follows:
Step 1 Start the Internet Explorer.
Step 2 On the main menu, choose Tool > Internet Options.
Step 3 On the General tab page in the Internet Options dialog box, click Delete in the Internet
Temporary File area.
Step 4 Log in to the network information collection page once again.
----End
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 25, Total 38

3 Problems Related to the Transdata
3.1 System Prompting Incorrect Program
Configuration at Startup of the Transdata
Cause:
The possible cause is that the OS of an earlier version is installed on the PC.
Solution:
Install the vcredist_x86.exe patch.
vcredist_x86.exe

3.2 System Prompting Project Information Loading
Failure and Invalid Parameters at Startup of the
Transdata
Cause:
This error occurs when the Nastar CS Transdata or the CDMA Transdata was deployed on the
PC but the project library was directly deleted from the PC.
Solution:
This prompt does not affect other project operations. You can directly click OK and then
proceed according to the normal procedure.
3.3 Exceptions That May Occur During the Data
Import of the Transdata
The import data format or the import data content is incorrect, as shown in Figure 3-1.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 26, Total 38

Figure 3-1 Prompt of incorrect data format or content


The disk space is insufficient, as shown in Figure 3-2.
Figure 3-2 Prompt of insufficient disk space


3.4 Alarm Data Failing to Be Imported
Cause:
The same alarm data can be imported on certain devices but fails to be imported on a certain
device.
This problem occurs because the ordering rules during the installation of the database are
incorrect.
Solution:
For details about the method of checking whether ordering rules of the database are correct,
see section 1.1.10 "Confirming the Patch Version and Checking Whether the Collation Setting
Is Correct."
If ordering rules are incorrect, make correct ordering rule of the database. Then, the problem
is solved.
3.5 Windows 7 installed with SQL Server 2000 does
not support the large amount of data imported
Windows 7 system installed with SQL Server 2000 ,and when imported large amount of
data into the Transdata ,the Transdata will be no response occasionally.
Cause:
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 27, Total 38

Windows 7 system installed with SQL Server 2000,the course will be occasional virtual
memory overflow(when imported large amount of data into the Transdata,about 25 BSC,and
each BSC the data about 800M),resulting in Transdata data import task not working.
Solution:
The problem is occasional, usually by restarting the SQL Server to circumvent.Restart the
SQL Server services,then restart the Transdata task.
3.6 Supported Format of Imported NodeB Traffic
Statistics
Currently, NodeB traffic statistic files only in CSV format exported from the M2000 can be
imported and analyzed.
NodeB traffic statistic files are named as follows: pmresult_counter set_granularity_start
time_end time_csv.
For example:
The following shows an example of a traffic statistic file related to HSDPA:
pmresult_50331648_15_200709150000_200709150015.csv

The following shows an example of a traffic statistic file related to Iub:
pmresult_50331649_15_200709150000_200709150015.csv

The following shows an example of a traffic statistic file related to the CE interface:
pmresult_50331650_15_200709150000_200709150015.csv

The following shows an example of a traffic statistic file related to HSUPA:
pmresult_50331651_15_200709150000_200709150015.csv

The following shows an example of a traffic statistic file related to OPERATOR:
pmresult_50331652_15_200807012300_200807012315.csv

The following shows an example of a traffic statistic file related to the CPC cell:
pmresult_50331653_15_200807012300_200807012315.csv
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 28, Total 38

4 Problems Related to Mini_OMStar
4.1 How Do I Handle the Failure to Start the
Mini-OMStar Because vcredist.exe Is Not Installed?
Cause:
When you run the Mini-OMStar, the following message is displayed because the vcredist.exe
is not installed.


Solution:
After the vcredist.exe is installed, restart the Mini-OMStar.
The directory for saving the vcredist.exe is as follows: \OMStar V500R006_ENG \OMStar
V500R006\Mini_OMStar\vcredist_x86.exe.
4.2 Why Does the System Display the Information
Indicating That Transdata Is Started or Fails to Be
Started After the Mini_OMStar Starts a Task?
Cause:
Transdata is manually started or Transdata is stopped abnormally, but the Transdata process
still exists in the task manager.
Solution:
If Transdata is started, stop Transdata and then restart the Mini task.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 29, Total 38

In case of other situations, check whether the Transdata process exists in the task manager. If
the Transdata process exists in the task manager, stop the process and then restart the Mini
task.
4.3 Why Does the Mini-OMStar Fail to Create a
Project?
Cause 1:
1. If the version is earlier than OMStarV500R006C03SPC400, by default, the automatic
import and analysis tasks created by the Mini-OMStar in one key mode are saved in
disk D. If disk D is unavailable on the PC, the data cannot be imported automatically.
Solution:
Check the versions of OMStar and whether disk D is available on the PC.
Step 2 Open the config.ini file in the installation directory\OMStar
V500R006\Mini_OMStar\config.ini directory.
Step 3 Find the DBPATH field and change D behind the equal mark (=) to a disk label available on
a local PC. At least 2 GB free space is required in the available disk.


----End
Cause 2:
The disk space is insufficient.
Solution:
Check the size of the disk space. If the disk space is insufficient, configure a disk with
sufficient space (based on experience, size of disk space = size of data package x 25). In case
of a task involving multiple NEs, the required disk space is subject to the NE that has the
largest amount of data.
Cause 3:
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 30, Total 38

The user does not have permission on the associated disk files.
Solution:
Check whether the disk for project creation has the write property. If the disk does not have
the write property, set the write property or configure a disk that has the write property.
Cause 4:
The SQL Server Patch Version and the Collation Setting are incorrect.
Solution:
Firstly confirming the Patch Version and checking whether the Collation Setting is correct,
you can follow to section 1.1.10 "Confirming the Patch Version and Checking Whether the
Collation Setting Is Correct." If the Patch Version or the Collation Setting is not correct,
please reinstall the SQL Server.
Cause 5:
The database is removed and then installed. Commonly, SQL 2005 database is installed
before the removal but SQL 2000 database is installed after the removal. Certain database
files are not cleared when the database is removed.
Solution:
Step 1 Open the SQL Server Enterprise Manager.
Choose Start > Program > Microsoft SQL Server > Enterprise Manager.
Check whether the file that is named beginning with Nastar exists. If the file exists,
right-click the file and choose Delete.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 31, Total 38



Step 2 Check whether the file that is named beginning with Nastar exists in the installation directory
of the database. If the file exists, delete it.


Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 32, Total 38

Step 3 Start the SQL service and restart the Mini_OMStar.
----End
4.4 How Do I Handle the Problem That the Task Is in
the Stopping State for a Long Time After the
Mini-OMStar Stops the Task?
The Mini-OMStar supports periodic stopping of tasks. After you stop a task that is running on
the Mini-OMStar, the task is waiting for being stopped until it runs to a certain stage. You
need to wait with patience.
4.5 How Do I Back Up Tasks Created by the
Mini-OMStar After the OMStar Program Is
Uninstalled?
The automatic tasks are saved in the project folder in the root directory of the OMStar
program. When the OMStar is uninstalled, the project folder is also deleted. Therefore, you
need to back up the project folder before uninstalling the OMStar. After the OMStar of a new
version is installed, you need to copy the project folder to the directory of the OMStar
program.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 33, Total 38

5 Problems Related to OMStar
5.1 The Map Cannot Be Displayed Correctly
Cause:
Project parameter data is not imported or GenexShare components are not installed.
Solution:
Check whether project parameter data is imported.
If the project parameter data is imported, check whether GenexShare components are installed.
If GenexShare components are not installed, install the components. Then the map can be
displayed normally.
5.2 Failure to Load Report Node
When the report node is loaded, a dialog box shown in Figure 5-1 is displayed, indicating that
the report is locked by IT DIVISION and cannot be edited. After users click OK, this node
still cannot be loaded successfully.
Figure 5-1 File In Use dialog box


Cause:
This problem occurs because the template file is closed abnormally last time. As a result, a
word process exists in the process list.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 34, Total 38

Solution:
After users close such word process, this problem is solved.
5.3 What Do I Do If a Task Fails to Be Executed
Because the Word Program Is Abnormal?
After you run a task, the Fail to execute task dialog box is displayed. If the problem persists
after the OMStar V500R006 NetworkEvaluate is restarted, you can infer that the cause is that
the Word program on the PC is abnormal.


Solution:
In this case, you need to run FixTool (2).bat in the \OMStar V500R006\WCDMA directory
and restart the PC.
5.4 Task Manager Popping Up Occasionally When the
Tool Is Generating Reports
Solution:
The task manager pops up occasionally when the tool is generating reports.
Solution:
The popped task manager, however, does not affect the functions and execution results of the
tool. Engineers are working on this problem.
5.5 Why Am I Not Allowed To Use the Copy/Paste
Function of Windows During the Process of OMStar
Word Report Generation?
When the OMStar is generating a DOC report, a lot of charts and pictures will be copied from
the temporary Excel file and pasted to the DOC report, so using the copy/paste function
something of Windows may cause a DOC report generate failure. Therefore, you are not
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 35, Total 38

recommended to use the copy/paste function of Windows during the generation of a DOC
report.
5.6 Is the OMStar Compatible with Office 2007?
The OMStar V500R006C01T and later versions can support Office 2007.
The OMStar cannot be used if both Office 2003 and Office 2007 are configured on the same
computer.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 36, Total 38

6 Miscellaneous
6.1 What Are the Precautions for Installing the
OMStar in the Windows 7 Operating System?
The installation and usage of the OMStar that is developed based on the Windows XP
operating system may be affected because the security control in the Windows 7 operating
system is different from that in the Windows XP operating system.
The known issues are as follows:
License verification is not performed for reinstalling the OMStar. This occurs because you
have set the UAC to a high level. In this case, you do not need to import the license again for
reinstalling the OMStar. However, the validity period and authority are still controlled by the
license that is imported previously. It is recommended that you set the UAC to the lowest
level.
To change UAC settings, do as follows: Choose Start > Control Panel > User Accounts. In
the displayed User Accounts page, click Change User Account Control Settings.
The OMStar may fail to read or write files in the installation directory, which causes that
OMStar runs abnormally. For example, the OMStar fails to read or write logs or create
necessary temporary folders.
This occurs because you have not logged in to the Windows 7 operating system as user
Administrator and the OMStar is installed on the drive C.
It is recommended that you log in to the operating system as user Administrator. In addition,
to start the OMStar, do as follows: Right-click the OMStar icon and choose Properties from
the shortcut menu. In the displayed SETUP Properties dialog box, click Compatibility,
select Run this program as an administrator, and click OK.
The OMStar fails to be uninstalled even through the message is displayed indicating that the
software is uninstalled successfully. However, some files cannot be deleted and the OMStar
fails to be reinstalled. This occurs because you have set the UAC to a high level. If the
security level is set too high, the OMStar is not authorized to delete all files. It is
recommended that you set the UAC to the lowest level.
To change UAC settings, do as follows: Choose Start > Control Panel > User Accounts. In
the displayed User Accounts page, click Change User Account Control Settings.
Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 37, Total 38

6.2 OMstar running stop caused by automatic sleep in
Windows 7
The automatic sleep function is started in default; OMSTAR will be stopped by system
automatic sleep during the running.
To change automatic sleep setting, do as follow: Choose Start > Control Panel > Hardware
Sound > Power Options, click Change when the computer sleeps.
Figure 6-1 Select Change when the computer sleeps in Power Option


Maintenance Guide to OMStar V500R006 Confidentiality:

2012-04-12 Huawei Confidential Page 38, Total 38

Figure 6-2 Select Never in the Put the computer to sleep, then click Save changes


6.3 Problems of Using OMStar V500R006 on Windows
2003 Server
The standalone OMStar V500R006 NetworkEvaluate does not support the operations of
multiple users at the same time when it is installed on a Windows 2003 server.
If the OMStar V500R006 NetworkEvaluate uses the database on the server, the operating
efficiency of the NetworkEvaluate will be affected when multiple users access the database at
the same time.
6.4 Obtaining OMStar Logs in One-Key Mode
Run the GetInfo.exe tool in the installation path of the OMStar, for example, D:\Program
Files\OMStar V500R006\OMStar V500R006\GetInfo.exe
In the path, the log folder named All_log_files is generated.