KB18230: Maximum Report Execution Time does not take effect in MicroStrategy Intelligence Server 10.x

SYMPTOM:
The administrator implemented a routine via some Strategy Command Manager scripts in order to set some report execution limits as -1 in order to run the biggest reports during the night and another routine in order to set the report execution limits back during the day period; however, the administrator realizes that some reports are still appearing as executing in the Job Monitor even after reaching the 'Report execution time (sec).'
For example:

• The following Strategy Command Manager script is executed everyday at 11:00PM:
  ALTER PROJECT CONFIGURATION MAXREPORTEXECTIME -1 MAXNOREPORTRESULTROWS -1 MAXNOELEMROWS -1 IN PROJECT `Strategy Tutorial`;
  
• Another script is executed everyday at 8:00AM in order to avoid a peak of usage during a certain period of hours:
  ALTER PROJECT CONFIGURATION MAXREPORTEXECTIME 600 MAXNOREPORTRESULTROWS 32000 MAXNOELEMROWS -1 IN PROJECT `Strategy Tutorial`;
  
• In order to confirm the alteration the administrator accesses the Project Configuration GUI and checks the all parameters under the TAB GOVERNING as shown and the values were really altered:
  

• Then some users submit some reports and even after the report execution reaches the limit of 'Report execution time (sec)' some reports are still appearing with the status 'Executing' in the 'Job Monitor' queue, as shown below:
  

CAUSE:
Changes made at the server level take effect only after restarting the Strategy Intelligence Server. For the list of changes that requires server to be restarted, refer to the following Strategy Knowledge Base technical note:
KB16760 (KB5300-8X-2704): Which setting changes require Strategy Intelligence Server 8.x to be restarted
 
ACTION:
Create a post routine that it is executed just after altering these parameters; this routine should restart the Strategy Intelligence Server service.