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

KB13940: How to change the log destination for the DSSErrors.log recorded by the MicroStrategy Diagnostics Configuration Tool on a Microsoft Windows machine in MicroStrategy Intelligence Server 9.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


How to change the log destination for the DSSErrors.log recorded by the MicroStrategy Diagnostics Configuration Tool on a Microsoft Windows machine in MicroStrategy Intelligence Server 9.x

In Strategy Intelligence Server 9.x , the DSSErrors.log recorded by the Strategy Diagnostics Configuration Tool (CastorServer Instance and Machine Default) on a Microsoft Windows machine is by default located in Program Files\Common Files\Strategy\Log folder.
 
In order to change the default location for these log files, follow the steps below:
 

  1. Open the Windows registry editor from the Start -> Run menu (regedit).
     
  2. To change the location of the DSSErrors.log recorded by the CastorServer Instance, locate the key below:
     
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Strategy\DSS Server\LogPath 


    Right-click on the LogPath key to modify it and specify the new location for the DSSErrors.log.
     
  3. To change the location of the DSSErrors.log recorded by the Machine Default, locate the key below:
     
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Strategy\DSS Suite\LogPath

     
    Right-click on the LogPath key to modify it and 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 11, 2017

Last Updated:

May 31, 2020