KB39348: MicroStrategy Object Manager 9.4.x-10.x does not appear to be writing events to a new log file despite configuring it through MicroStrategy Diagnostics and Performance Logging 9.2.x - 9.3.x

SYMPTOM:
By default, Strategy Object Manager 9.4.x-10.x logs events into the DSSErrors.log file. Consider that Strategy Object Manager 9.4.x-10.x needs to be configured to log events to a new log file. In order to do so, user goes into Tools > Object Manager Preferences:

Then Object Manager > Events > Configure Logging, and enables logging to a new file called 'SMLog' from Strategy Diagnostics and Performance Logging 9.4.x-10.x as shown:

 
A new file called 'SMLog.log' gets created in the <MSTR_LOG> directory, but the Strategy Object Manager 9.4.x-10.x events continue to be logged into the DSSErrors.log file.
CAUSE:
The user should consider two things here:

• The Client Services > Source Manipulator entry in Strategy Diagnostics and Performance Logging 9.4.x-10.x needs to be changed for the 'Machine Default' configuration on the Strategy Object Manager 9.4.x-10.x client machine (and not 'CastorServer instance' configuration) as shown:
  

• This is irrespective of whether the Strategy Object Manager 9.4.x-10.x operations are to be carried out in 2-tier or 3-tier mode. The log entries are written by the client Strategy Object Manager 9.4.x-10.x machine.
   
  
• Once the change is made, Strategy Object Manager 9.4.x-10.x needs to be restarted for it to take effect. 

ACTION:
The user should ensure that the above two points were considered for the logging to the new file to take place successfully.