Windows Event Log

ConnectMCAL

By default, the ConnectMCAL component writes error log messages into the Windows Event Log, but by using the following configuration key, logging of errors or warnings can be activated:

[Logger]
WinEventLogSource=ConnectMCAL (Siebel)

[Dynamic]
WinEventLogLevel=3

key renamed

NTEventLogLevel has been renamed to WinEventLogLevel

Key	Ini-Default	Range	Description
WinEventLogLevel	2	0,2,3,4	Write errors, warnings or info to Windows Event Log 0=off 2=Error 3=Warning 4=Info

change without service restart

If WinEventLogLevel was 0 when startup, so logging was set to off, the service needs to be cycled. If logging was enabled when starting the service changes have effect without restart.

In order to render and display the log entries properly, the bsLogLibraryEvents.dll is required. This dll is installed and configured during the installation process.

If the configuration or DLL is missing, the following output is shown in the Windows Event Log:

To fix this, the key below has to be set in the registry:

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\EventLog\\Application\ConnectMCAL (Siebel)]
"EventMessageFile"="C:\\Windows\\SysWOW64\\bsLogLibraryEvents.dll"

Also check that the bsLogLibraryEvents.dll exists in the C:\Windows\SysWOW64\ directory.

Media Manager

By default, the Media Manager component writes error log messages into the Windows Event Log, but by using the following configuration key, logging of errors or warnings can be activated:

[LOGGER]
WIN_EVENT_LOG_LEVEL=2
WIN_EVENT_LOG_SOURCE=MediaManager (Siebel)

Key	Ini-Default	Range	Description
WIN_EVENT_LOG_LEVEL	2	0,2,3,4	Write errors, warnings or info to Windows Event Log 0=off 2=Error 3=Warning 4=Info

change without service restart

If WinEventLogLevel was 0 when startup, so logging was set to off, the service needs to be cycled. If logging was enabled when starting the service changes have effect without restart.

In order to render and display the log entries properly, the bsLogLibraryEvents.dll is required. This dll is installed and configured during the installation process.

If the configuration or DLL is missing, the following output is shown in the Windows Event Log:

To fix this, the key below has to be set in the registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\BucherSuter MediaManager
(Siebel)] 
"EventMessageFile"="C:\\Windows\\SysWOW64\\bsLogLibraryEvents.dll"

Also check that the bsLogLibraryEvents.dll exists in the C:\Windows\SysWOW64\ directory.

DataStore

By default, the DataStore doesn't write log messages into the Windows Event Log, but by using the following configuration key, logging of errors or warnings can be activated:

[Dynamic]
NTEventLogLevel=

Key	Ini-Default	Range	Description
NTEventLogLevel	0	0,2,3	Write errors or warnings to Windows NT Log 0 = Off 2 = Error 3 = Warning

In order to render and display the log entries properly, the bsLogLibraryEvents.dll is required. This dll is installed and configured during the installation process.

If the configuration or DLL is missing, additional lines are written in the Windows Event View entry as outlined below: