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