CMS.exe is not automatically started

[Former Member]

Dear Experts,

I have BOE installed in my VMware. Os is windows server 2003, DB is Mysql. The BOE can work fine before, but after one day, I cannot logon infoview and CMS.I checked the CCM every services are running.

But when i check the task manager, i cannot find CMS.exe. I also checked the dependency on SIA properties, and BOE120Mysql is in there.

And i went to check the trace log under Logging, i found some error as below:

file:SvcMgr_xx_trace.log:

.\DatabaseSubsystem_impl.cpp:2923: TraceLog message 1

2010/05/06 08:20:33.062|>>|A| | 3776|3780| |||||||||||||||assert failure: (.\DatabaseSubsystem_impl.cpp:2923). (0 : Can't create table 'c:\windows\temp\#sql568_e_11.frm' (errno: 121)).

d:\mira_rtm\src\framework\dbutilities\dbutils_lib\subsysmgrhelper.h:163: TraceLog message 2

2010/05/06 08:20:33.109|>>|A| | 3776|3780| |||||||||||||||assert failure: (d:\mira_rtm\src\framework\dbutilities\dbutils_lib\subsysmgrhelper.h:163). (false : DBUtils::Subsystem Init: Failed to init subsystem manager. Reason: CDatabase::Open failure.).

In CMS_xx_trace.log:

.\DatabaseSubsystem_impl.cpp:2923: TraceLog message 1

2010/05/06 08:00:27.593|>>|A| | 2732|2268| |||||||||||||||assert failure: (.\DatabaseSubsystem_impl.cpp:2923). (0 : Can't create table 'c:\windows\temp\#sql568_d_e.frm' (errno: 121)).

As the format is ugly, so i split my trace log, to be continued.

Edited by: Sophie Xu on May 6, 2010 12:35 PM

[Former Member · Accepted solution]

Actually i found a workaround, but it's very inconvenient and not practical.

Everytime CMS.exe cannot be started even restarted the SIA, i can stop the SIA and go to SIA properties->dependency, then remove the BOE120Mysql and add it again. After that i restart the SIA, the CMS.exe shows up.

[joshua_kuhn · Accepted solution]

Hi Sophie,

The errors you posted were referring to problems with the files: "c:\windows\temp\#sql568_e_11.frm". I believe these are just temporary files used by MySQL on startup. Are you shutting Windows down before exiting the vmware? If not, then MySQL is probably not shutting down properly which is causing it to leave behind some of these frm files. In addition, it could be causing problems when trying to restart it. To clean up the system, try this:

Stop both MySQL and the SIA

then delete any files leftover in the temp directory.

Start MySQL first, give it a few mins and then start the SIA.

Before shutting down your vmware image, stop both the SIA and MySQL services first, then Windows, then VMware.

[Former Member · Accepted solution]

Hi Kuhn,

Thanks for your reply.

Everytime I shutdown the BOE without stopping SIA in CCM and Mysql, but does that mean I didn't follow the routine way to close it? I thought it will be shutdown and monitored by windows automatically.

And i checked the temp folder, i cannot find any rfm file in it. But i feel your way is more careful, i will try that.

thanks.

[Former Member · Accepted solution]

Hi Kuhn,

I have followed your suggestion these days, and the problem occured seldom or randomly, so i think this way can solve this kind of problem.

Many thanks,

Sophie

[Former Member]

Even restart the SIA cannot help, last time i remove the DB dependency then add it again, after restart SIA, CMS.exe shows up.

Here attached the netstat -anb which included the CMS.exe and which didn't:

without CMS.exe

C:\Documents and Settings\Administrator>netstat -anb

Active Connections

Proto Local Address Foreign Address State PID

TCP 0.0.0.0:21 0.0.0.0:0 LISTENING 1520

[inetinfo.exe]

TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4

[System]

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 752

RpcSs

[svchost.exe]

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4

[System]

TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING 500

[lsass.exe]

TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 1520

[inetinfo.exe]

TCP 0.0.0.0:2393 0.0.0.0:0 LISTENING 1596

[msmdsrv.exe]

TCP 0.0.0.0:2394 0.0.0.0:0 LISTENING 1596

[msmdsrv.exe]

TCP 0.0.0.0:2725 0.0.0.0:0 LISTENING 1596

[msmdsrv.exe]

TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING 1344

[mysqld-nt.exe]

TCP 0.0.0.0:6190 0.0.0.0:0 LISTENING 4

[System]

TCP 0.0.0.0:6410 0.0.0.0:0 LISTENING 3916

[sia.exe]

TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 4020

[tomcat5.exe]

TCP 0.0.0.0:8098 0.0.0.0:0 LISTENING 4

[System]

TCP 0.0.0.0:8099 0.0.0.0:0 LISTENING 4

[System]

TCP 127.0.0.1:1046 0.0.0.0:0 LISTENING 3232

[ccApp.exe]

TCP 127.0.0.1:8005 0.0.0.0:0 LISTENING 4020

[tomcat5.exe]

TCP 192.168.0.129:139 0.0.0.0:0 LISTENING 4

[System]

TCP 127.0.0.1:1335 127.0.0.1:8005 TIME_WAIT 0

TCP 127.0.0.1:1336 127.0.0.1:8080 TIME_WAIT 0

UDP 0.0.0.0:445 : 4

[System]

UDP 0.0.0.0:500 : 500

[lsass.exe]

UDP 0.0.0.0:4500 : 500

[lsass.exe]

UDP 0.0.0.0:3456 : 1520

[inetinfo.exe]

UDP 127.0.0.1:123 : 836

UDP 127.0.0.1:1027 : 836

UDP 127.0.0.1:3456 : 1520

[inetinfo.exe]

UDP 127.0.0.1:1054 : 3568

[iexplore.exe]

UDP 192.168.0.129:138 : 4

[Former Member]

with CMS.exe:

C:\Documents and Settings\Administrator>netstat -anb

Active Connections

Proto Local Address Foreign Address State PID

TCP 0.0.0.0:21 0.0.0.0:0 LISTENING 1520

[inetinfo.exe]

TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4

[System]

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 752

RpcSs

[svchost.exe]

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4

[System]

TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING 500

[lsass.exe]

TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 1520

[inetinfo.exe]

TCP 0.0.0.0:2393 0.0.0.0:0 LISTENING 1596

[msmdsrv.exe]

TCP 0.0.0.0:2394 0.0.0.0:0 LISTENING 1596

[msmdsrv.exe]

TCP 0.0.0.0:2725 0.0.0.0:0 LISTENING 1596

[msmdsrv.exe]

TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING 1344

[mysqld-nt.exe]

TCP 0.0.0.0:6190 0.0.0.0:0 LISTENING 4

[System]

TCP 0.0.0.0:6410 0.0.0.0:0 LISTENING 1632

[sia.exe]

TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 4020

[tomcat5.exe]

TCP 0.0.0.0:8098 0.0.0.0:0 LISTENING 4

[System]

TCP 0.0.0.0:8099 0.0.0.0:0 LISTENING 4

[System]

TCP 127.0.0.1:1046 0.0.0.0:0 LISTENING 3232

[ccApp.exe]

TCP 127.0.0.1:8005 0.0.0.0:0 LISTENING 4020

[tomcat5.exe]

TCP 192.168.0.129:139 0.0.0.0:0 LISTENING 4

[System]

TCP 127.0.0.1:1458 127.0.0.1:3306 ESTABLISHED 3508

[CMS.exe]

TCP 127.0.0.1:3306 127.0.0.1:1458 ESTABLISHED 1344

[mysqld-nt.exe]

TCP 127.0.0.1:1450 127.0.0.1:3306 TIME_WAIT 0

TCP 127.0.0.1:1452 127.0.0.1:3306 TIME_WAIT 0

TCP 127.0.0.1:1454 127.0.0.1:3306 TIME_WAIT 0

TCP 127.0.0.1:1456 127.0.0.1:3306 TIME_WAIT 0

UDP 0.0.0.0:445 : 4

[System]

UDP 0.0.0.0:500 : 500

[lsass.exe]

UDP 0.0.0.0:4500 : 500

[lsass.exe]

UDP 0.0.0.0:3456 : 1520

[inetinfo.exe]

UDP 127.0.0.1:123 : 836

W32Time

[svchost.exe]

UDP 127.0.0.1:1027 : 836

W32Time

[svchost.exe]

UDP 127.0.0.1:3456 : 1520

[inetinfo.exe]

UDP 127.0.0.1:1054 : 3568

[iexplore.exe]

UDP 192.168.0.129:138 : 4

[System]

UDP 192.168.0.129:123 : 836

W32Time

[svchost.exe]

UDP 192.168.0.129:137 : 4

[System]

And some of my colleagues also met the same problem with the BOE installed based on Mysql, hope someone can help me.

Best Regards,

Sophie

[BasicTek]

Check windows event viewer as well. There seems to be an issue with the account running the SIA and either access to the CMS DB or the local file system. You may ge more details in event viewer. With the SIA off recheck the connection information in the properties - configuration page of the SIA. If still stuck open an incident with the Admin team boj-bip-adm component

Based on some of your errors i also found the following

1309681 - Can't log on to CMC after installing VB6 on the same server where Visual Studio 2005 is already installed

It appears that VB can corrupt libraries needed for the CMS. It may not be VB but the errors you are receiving seem to indicate the same type of library corruption. You should open a message with admin if the KB does not address your issue.

Regards,

Tim

[joshua_kuhn]

The assert errors look like your VMware may have run out of space on the C:\ drive. For whatever reason the CMS is unable to write to temp space. In order for the CMS to start, MySQL must be running and the CMS must have the means to connect to the database successfully. The SIA should automatically start the CMS automatically. Unless you have a clustered environment, the CMS should always attempt to start by the SIA.

Assuming permissions haven't changed on the db side, I would look at resources on your Vmware. Is it possible the image wants to expand but can't because of the host?

Here are a couple things you can do to test:

install the MySQL Admin tool from the mysql website. (http://dev.mysql.com/downloads/gui-tools/5.0.html)

Create a new SIA and point it to the new empty database.

If this new SIA works, your vmware image clearly has space on the C:\ drive, so the problem must have been elsewhere.

[Former Member]

Thanks, but i checked my laptop, in the VM, C driver still have 12 GB free space.

But I can check the way you mentioned to narrow down the problem.

Thanks.