EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB13943: How to change the log destination for the DSSErrors.log recorded by the MicroStrategy Intelligence Server on Linux/Unix


Community Admin

• Strategy


How to change the log destination for the DSSErrors.log recorded by the Intelligence Server on Linux/UNIX

The DSSErrors.log can be configured by using the Strategy Diagnostics Configuration Tool.
 
This utility exposes two configuration choices - the Machine Default configuration and the CastorServer Instance configuration.
 
The CastorServer Instance is the name given to the Intelligence Server and any changes made to the logs for this configuration will affect the Intelligence Server only.
 
The Machine Default and Castor Server Instance configurations both use the same default DSSErrors log file location, chosen at installation time.
 
In order to change the default location for these log files, follow the steps below:

  1. Open the MSIReg.reg file which can be found under the <mstr_home> folder. 
  2. To change the location of the DSSErrors.log recorded by the CastorServer Instance, locate the key below:
     
  3. 
    HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\DSS Server 


    Modify the LogPath string value for the above key to specify the new location for the DSSErrors.log.
     
  4. To change the location of the DSSErrors.log recorded by the Machine Default, locate the key below:
     
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\DSS Suite

     
    Modify the LogPath string value for the above key to specify the new location for the DSSErrors.log. 

 
 
WARNING:
Modifying the registry values incorrectly may cause serious, system-wide problems. Any edit of the registry is done at the user's own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. The user should backup the registry file prior to alteration.


Comment

0 comments

Details

Knowledge Article

Published:

May 24, 2017

Last Updated:

May 24, 2017