Gleb.Zaborshchikov at 12:27, 26 August 2026

2026-08-26T12:27:16Z

← Older revision		Revision as of 12:27, 26 August 2026
Line 141:		Line 141:

	: '''Why disable logging?''' Leaving logging active causes the <code>Solver.log</code> file to grow uncontrolled over time, consuming disk space and potentially slowing down file operations. Restoring the default (commented) state is a best practice once diagnostics are complete.		: '''Why disable logging?''' Leaving logging active causes the <code>Solver.log</code> file to grow uncontrolled over time, consuming disk space and potentially slowing down file operations. Restoring the default (commented) state is a best practice once diagnostics are complete.
			[[Category:Manual]]
			[[Category:SMath Studio]]

Andrey.Ivashov at 11:53, 26 August 2026

2026-08-26T11:53:47Z

← Older revision		Revision as of 11:53, 26 August 2026
Line 117:		Line 117:
	=== 6. Retrieve the log file ===		=== 6. Retrieve the log file ===

	Navigate to the log folder (no administrator access required): ~~{{nowrap\|~~%APPDATA%\SMath\}}		Navigate to the log folder (no administrator access required): <nowiki>%APPDATA%\SMath\</nowiki>

	: To open it quickly, press '''Win+R''', type <code>%APPDATA%\SMath\</code>, and press '''Enter'''.		: To open it quickly, press '''Win+R''', type <code>%APPDATA%\SMath\</code>, and press '''Enter'''.

Andrey.Ivashov: Created page with "= Enabling Logging in SMath Studio = When you experience a challenge or unexpected behavior in SMath Studio, enabling built-in logging helps diagnose the issue. The log file captures detailed trace information that you (or your software vendor) can use to identify the root cause. == Prerequisites == Locate where SMath Studio is installed: * '''Per-machine installation''': `C:\Program Files (x86)\SMath\` (or similar) * '''Per-user installation''': your user..."

2026-08-26T11:52:08Z

Created page with "= Enabling Logging in SMath Studio = When you experience a challenge or unexpected behavior in SMath Studio, enabling built-in logging helps diagnose the issue. The log file captures detailed trace information that you (or your software vendor) can use to identify the root cause. == Prerequisites == Locate where SMath Studio is installed: * '''Per-machine installation''': <code>C:\Program Files (x86)\SMath\</code> (or similar) * '''Per-user installation''': your user..."

New page

= Enabling Logging in SMath Studio =

When you experience a challenge or unexpected behavior in SMath Studio, enabling built-in logging helps diagnose the issue. The log file captures detailed trace information that you (or your software vendor) can use to identify the root cause.

== Prerequisites ==

Locate where SMath Studio is installed:
* '''Per-machine installation''': <code>C:\Program Files (x86)\SMath\</code> (or similar)
* '''Per-user installation''': your user profile folder (e.g., <code>C:\Users\<YourName>\...</code>)

== Steps ==

=== 1. Close all SMath Studio instances ===

Make sure every SMath Studio process is closed before editing the configuration file.

=== 2. Open <code>Solver.exe.config</code> for editing ===

Navigate to the SMath Studio installation folder and open the file '''Solver.exe.config''' with a text editor (e.g., Notepad).

: '''Note:''' Administrator permissions may be required to modify this file if SMath Studio was installed per-machine. Right-click your text editor and choose '''Run as administrator'''.

=== 3. Uncomment the logging blocks ===

The file contains two blocks that are '''commented out''' by default. You need to remove the XML comment markers (<code></code>) so that the configuration becomes active.

Below is the '''default (commented)''' content — both the <code><source></code> elements and the <code><add></code> listener element are wrapped in comments:

<pre>
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.diagnostics>
<sources>


</sources>
<sharedListeners>


</sharedListeners>
<trace autoflush="true" indentsize="4" />
</system.diagnostics>
</configuration>
</pre>

'''Uncomment''' the two XML blocks that contain actual configuration (the <code><source></code> elements and the <code><add></code> listener element), while '''keeping the description comment''' (the first <code></code> block that contains explanatory text).

After uncommenting, the file should look like this:

<pre>
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.diagnostics>
<sources>

<source name="root">
<listeners>
<add name="file" />
</listeners>
</source>
<source name="SMath.Controls" newSwitch="true" switchValue="Error" />
<source name="SMath.Environment" newSwitch="true" switchValue="Error" />
<source name="SMath.Document" newSwitch="true" switchValue="Error" />
<source name="SMath.Manager" newSwitch="true" switchValue="Error" />
<source name="SMath.UI" newSwitch="true" switchValue="Error" />
</sources>
<sharedListeners>

<add name="file"
type="SMath.Manager.Logging.FileTraceListener, SMath.Manager"
traceOutputOptions="DateTime,ProcessId,ThreadId"
initializeData="%APPDATA%\SMath\Solver.log"/>
</sharedListeners>
<trace autoflush="true" indentsize="4" />
</system.diagnostics>
</configuration>
</pre>

: '''Tip:''' Only uncomment XML elements that contain nested XML structures (the <code><source></code> and <code><add></code> elements). Keep pure description text as comments.

=== 4. Save the file ===

Save the modified <code>Solver.exe.config</code> file and close the text editor.

=== 5. Reproduce the issue ===

Open SMath Studio and perform the steps that triggered the problem. The application will now write trace output to the log file.

=== 6. Retrieve the log file ===

Navigate to the log folder (no administrator access required): {{nowrap|%APPDATA%\SMath\}}

: To open it quickly, press '''Win+R''', type <code>%APPDATA%\SMath\</code>, and press '''Enter'''.

The log file is <code>'''Solver.log'''</code>.

=== 7. Examine the log ===

# Open <code>Solver.log</code> in a text editor.
# Scroll to the '''last lines''' — the most recent entries are where the relevant challenge is typically recorded.
# Either:
## Identify the error/exception message yourself, or
## Attach the log file (or its meaningful section) to a support request to your software vendor.

=== 8. Disable logging (recommended when finished) ===

After the issue is resolved or the log has been shared:

# Close SMath Studio.
# Re-comment the two XML blocks in <code>Solver.exe.config</code> (restore the original state shown in Step 3).
# Save the file.
# Optionally delete <code>%APPDATA%\SMath\Solver.log</code> to clean up.

: '''Why disable logging?''' Leaving logging active causes the <code>Solver.log</code> file to grow uncontrolled over time, consuming disk space and potentially slowing down file operations. Restoring the default (commented) state is a best practice once diagnostics are complete.

Enabling Logging in SMath Studio - Revision history

Gleb.Zaborshchikov at 12:27, 26 August 2026

Andrey.Ivashov at 11:53, 26 August 2026