Skip to main content
Version: 2.5.0

Memory Dump

b+s ConnectMCAL

In the event of a component crash, the ConnectMCAL component generates a memory dump (a.k.a. minidump) file.

By default, the minidump-file generated by the Connector is stored into the log directory:

[Logger]
Path= C:\ProgramData\BucherSuter\logfiles\MCAforSiebelCC\ConnectMCAL_Siebel.log

A minidump-file can be triggered manually during installation to ensure that a minidump will be written properly in case of emergency. To do this, the test mode must be activated first in the config file:

[Config]
TestMode=1

As this config is not dynamic, the ConnectMCAL has to be restarted.

For manually triggering a minidump-file, the corresponding command can be executed on the remote console of ConnectMCAL:

Command for opening a telnet session:

C:\>telnet localhost <RemoteConsolePort>

Command for triggering a minidump-file:

Welcome to b+s MCAL (ConnectMCAL)
remote> CrashTheApp

Please check that a minidump-file is written into the log path mentioned above and that the file has a size greater than 0 bytes. If this is not the case, the application may not have write permissions in the log path directory.

Attention

Please remove the test mode parameter "TestMode=1" from the config file after the test.