none
Changing the Message Analyzer Temp Files Location RRS feed

  • Question

  • GREAT BUY WHY I HAVE TO CHANGE THIS UNDER OPTIONS IN GUI OR COMMAND LINE

    ??????

    Easy way to modify this so I don't have to install Visual Studio IDE to perform this task, when I modify in notepad the application fails to start

    Changing the Message Analyzer Temporary Files Location

    Message Analyzer enables you to specify a location on a non-system drive for Message Analyzer temporary files. You might do this for the following reasons:

    • Better management of disk space — avoids excessive use of memory space from Message Analyzer writing to your c:\ drive over a period of time.

    • Better performance — Message Analyzer has better performance when writing to a non-system drive.

    • Improve performance on Windows 8 and later — Message Analyzer performs better on the Windows 8 operating system and later if the destination disk is formatted to the Resilient File System (ReFS), instead of the enforced NTFS format of your default system drive.

    Although the main application that benefits from reconfiguration of the temporary files location is usually server components, you still have the option change the location. If you want to do this you will need to open the MessageAnalyzer.exe.config file from the following location (or the installation folder location that you specified when installing Message Analyzer), and modify it as indicated below. Note that you could open this XML file in the Visual Studio IDE for the convenience of auto-formatting:

    C:\Program Files\Microsoft Message Analyzer\MessageAnalyzer.exe.config

    Under the <configuration/> node in the MessageAnalyzer.exe.config XML file contents, enter the following and specify an appropriate value for  the drive location.

    Configuration <button aria-label="Copy code" class="action" data-bi-name="copy"> Copy </button>
    <code  data-author-content="
    <add key="TempFolderPath" value="<driveLocation>\temp\matemp" />
    </appSettings>
    "><appSettings>
    <add key="TempFolderPath" value="<driveLocation>\temp\matemp" />
    </appSettings>

    Thursday, September 12, 2019 6:18 PM

All replies

  • Hello MaxVista,

    Using notepad should be fine - it may be the case that the changes that you made to MessageAnalyzer.exe.config resulted in some invalid XML. Can you show the entire contents of that file after editing by pasting them into an XML code block? The image below shows the button to press in order to insert a code block into your reply.

    Gary

    Thursday, September 12, 2019 8:12 PM
  • Hi,

    Replace <driveLocation> with a specific driver. The XML may looks like below:

    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
      <appSettings>
        <add key="TempFolderPath" value="C:\temp\matemp" />
      </appSettings>
      <runtime>
        <useLegacyJit enabled="1" />  
        <gcServer enabled="true"/>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <probing privatePath="extensions"/>
          <!--
              The problem is that whenever we are running MA through debugger we get several FileLoadExceptions 
              for may user control initialization. It seems that the assembly version referred in BAML 
              (compiled binary version of XAML) is 0.0.0.0, whereas the assembly version attached to the assembly 
              is 4.0.0.0. Since there's a mismatch of the major version, the exceptions are raised. Running 
              through the debugger gets extremely slow for cases when several new user controls are created while 
              visualizing a virtualized collection, like in Message Stack, Gantt chart, etc.
    
              We don't specify the 0.0.0.0 version and not all BAMLs have that. It's probably because of some build 
              setting or something else.
              
              The fix (maybe temporary for now) is to add a dependent assembly directive in application.exe.config 
              to redirect the binding from 0,0.0.0 to 4.0.0.0. Each such entry is added for the following assemblies...
              
              Microsoft.Protocols.Tools.UI.Controls 
              DockingLibrary 
              MessageAnalyzer assemblies.
          -->
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.CommonControls" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.Controls" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="DockingLibrary" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="MessageAnalyzer" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="System.Windows.Controls.DataVisualization.Toolkit" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.DataSourceConfigUI" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
        </assemblyBinding>
        <ThrowUnobservedTaskExceptions enabled="true"/> 
      </runtime>
    </configuration>
    

    Best regards,

    Drake


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, September 13, 2019 5:56 AM
    Moderator
  • <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
      <appSettings>
        <add key="TempFolderPath" value="Z:\temp\matemp" />
      </appSettings>
      <runtime>
        <useLegacyJit enabled="1" />  
        <gcServer enabled="true"/>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <probing privatePath="extensions"/>
          <!--
              The problem is that whenever we are running MA through debugger we get several FileLoadExceptions 
              for may user control initialization. It seems that the assembly version referred in BAML 
              (compiled binary version of XAML) is 0.0.0.0, whereas the assembly version attached to the assembly 
              is 4.0.0.0. Since there's a mismatch of the major version, the exceptions are raised. Running 
              through the debugger gets extremely slow for cases when several new user controls are created while 
              visualizing a virtualized collection, like in Message Stack, Gantt chart, etc.
    
              We don't specify the 0.0.0.0 version and not all BAMLs have that. It's probably because of some build 
              setting or something else.
              
              The fix (maybe temporary for now) is to add a dependent assembly directive in application.exe.config 
              to redirect the binding from 0,0.0.0 to 4.0.0.0. Each such entry is added for the following assemblies...
              
              Microsoft.Protocols.Tools.UI.Controls 
              DockingLibrary 
              MessageAnalyzer assemblies.
          -->
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.CommonControls" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.Controls" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="DockingLibrary" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="MessageAnalyzer" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="System.Windows.Controls.DataVisualization.Toolkit" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.DataSourceConfigUI" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
        </assemblyBinding>
        <ThrowUnobservedTaskExceptions enabled="true"/> 
      </runtime>
    </configuration

    Friday, September 13, 2019 6:31 PM
  • Friday, September 13, 2019 6:33 PM
  • <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
      <appSettings>
        <add key="TempFolderPath" value="Z:\temp\matemp" />
      </appSettings>
      <runtime>
        <useLegacyJit enabled="1" />  
        <gcServer enabled="true"/>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <probing privatePath="extensions"/>
          <!--
              The problem is that whenever we are running MA through debugger we get several FileLoadExceptions 
              for may user control initialization. It seems that the assembly version referred in BAML 
              (compiled binary version of XAML) is 0.0.0.0, whereas the assembly version attached to the assembly 
              is 4.0.0.0. Since there's a mismatch of the major version, the exceptions are raised. Running 
              through the debugger gets extremely slow for cases when several new user controls are created while 
              visualizing a virtualized collection, like in Message Stack, Gantt chart, etc.
    
              We don't specify the 0.0.0.0 version and not all BAMLs have that. It's probably because of some build 
              setting or something else.
              
              The fix (maybe temporary for now) is to add a dependent assembly directive in application.exe.config 
              to redirect the binding from 0,0.0.0 to 4.0.0.0. Each such entry is added for the following assemblies...
              
              Microsoft.Protocols.Tools.UI.Controls 
              DockingLibrary 
              MessageAnalyzer assemblies.
          -->
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.CommonControls" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.Controls" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="DockingLibrary" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="MessageAnalyzer" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="System.Windows.Controls.DataVisualization.Toolkit" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.Protocols.Tools.UI.DataSourceConfigUI" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0" newVersion="4.0.0.0"/>
          </dependentAssembly>
        </assemblyBinding>
        <ThrowUnobservedTaskExceptions enabled="true"/> 
      </runtime>
    </configuration

    Friday, September 13, 2019 6:34 PM
  • Thank you Gary
    Friday, September 13, 2019 6:34 PM
  • Hello MaxVista,

    It may just be a problem with how you cut and paste the data, but the updated file seems to end with:

    </configuration

    It should end with

    </configuration>

    Everything else looks fine - I can't imagine how just adding the appSettings element near the top of the file with notepad could have caused this to happen.

    Gary

    Friday, September 13, 2019 7:05 PM
  • As Gary metioned, Your .config file format is incorrect which needs to end with "</configuration>".

    The only difference from my example. 

    Check for access to the target directory as well, although the odds are small.

    Best regards,

    Drake


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, September 17, 2019 8:57 AM
    Moderator