No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


U2000 LCT abnormal display on Win7

Publication Date:  2012-07-25 Views:  708 Downloads:  0
Issue Description
1.     It was requested an investigation  of LCT startup status, because some time after start this application the “main topology” is not displayed.

2.     Expected menu is displayed below:

3.     Related software information
OS: Windows 7 Professional 64bit + MSSQL Server 2008 Express 64bit

Alarm Information

Handling Process
R&D investigated with Microsoft and found no confirmative conclusion why user database not start automatically will affect the connection on the first try sometimes. Now Microsoft has provided several possibilities. And they have given a workaround to force start user databases when sql2008 express startup, which has been tested and proven workable. R&D will add this implement mechanism into our next version. Some function will be performed when the SQL startup, which will start the user database.

Root Cause

1. The phenomenon was reproduced at lab, the probability of its occurrence is around 20%.
2. After sending the operation log collected from U2000 LCT and database to H&Q for analysis, from the log files some exception info can be found as below:
1) MCDB process start log
      vendorError2[-1]=[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "MCDB"  requested  by the login. The login failed.
      (Remark: MC is a process about interprocess message distribution.)
      2) Client log
      [pool-5-thread-50]5-8-2012 20:32:14 | ERROR | CommonDataMgr | getProcessInfoList(char) | Message not success send , result :184549395
      (Remark: It shows “Message not success send”.)
      Till then, we draw a conclusion that the MC process failed to connect to the MCDB, which affect the interprocess communication, and this caused the behavior. 
      The below diagram shows the analysis result, how this phenomenon occurs when the user start Win7 OS and login the U2000LCT client.

3.    R&D setup the mirror environment at H&Q, and the behavior also was reproduced. And the behavior can not be observed at windows XP&SQL Edition environment.
4.    From the DB log, we found some records about the DB connection, which can support the previous conclusion. 
     2012-05-18 19:03:49.64 spid73      Starting up database 'imaptempdb'.
     2012-05-18 19:03:49.68 spid109     Starting up database 'imapsmdb'.
     2012-05-18 19:03:53.16 Logon       Error: 18456, Severity: 14, State: 38.
     2012-05-18 19:03:53.16 Logon       Login failed for user 'NMSuser'. Reason: Failed to open the explicitly specified database. [CLIENT:].
5.     Based on the database log, R&D found that the start mode of “SQL2008 Express edition” is different with other “SQL Edition”.

6.     Microsoft confirmed that the user database (such as MCDB) start mode in latest SQL2008 express edition is different from other SQL edition; the user database will not start with the SQL process in Express edition, which may bring in the DB connection failure.The user database will be triggered to start by DB visit on it.

The workaround can be done as follows:
One way: 
If the behavior occurs during the operation, then follow the steps below to restart all NMS processes:
1)  From the main menu of System Monitor Client, choose Administration > Stop All NMS Process to close all processes of the U2000 LCT server.
2)  From the main menu of System Monitor Client, choose Administration > Start All NMS Process to start all processes of the U2000 LCT server.
3)  Logout and login the LCT client again.
(since the user database will be notified to start when the first LCT startup.)

Another way:  
Execute the following script on the machine with U2000 LCT(just one time).
execute method】Put ‘startupon.rar’ in the LCT installation directory(such as D:\U2000 LCT). Right click it and choose "Exact here" to decompress it. And then double-click ‘startupon.bat’, then follow the prompt to input the DB servevice name and password of ‘sa’.
If the following message was displayed,it means success.
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Configuration option 'scan for startup procs' changed from 1 to 1. Run the RECONFIGURE statement to install.
After this ,when the sql2008 express starts,the user database will be also started.
The workaround provided by Microsoft will be added into next LCT version.