forked from SkylineCommunications/dataminer-docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request SkylineCommunications#3906 from SkylineCommunicati…
…ons/41068 RN 41068
- Loading branch information
Showing
3 changed files
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
18 changes: 18 additions & 0 deletions
18
.../SLNetClientTest_tool_diagnostic_procedures/SLNetClientTest_query_hint_paths.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
uid: SLNetClientTest_query_hint_paths | ||
--- | ||
|
||
# Querying the assembly resolution hint paths | ||
|
||
To troubleshoot assembly resolution issues, from DataMiner 10.4.12/10.5.0 onwards, you can use the SLNetClientTest tool to query the hint paths used to look up QAction dependencies: | ||
|
||
1. [Connect to the DMA using the SLNetClientTest tool](xref:Connecting_to_a_DMA_with_the_SLNetClientTest_tool). | ||
|
||
1. In the *Diagnostics* menu, select *DMA* > *SLScripting AssemblyResolve HintPaths*. | ||
|
||
1. Go to the *Output* tab to view the current list of hint paths used by the DataMiner AssemblyResolveHelper. | ||
|
||
If [multiple SLScripting processes are configured](xref:Configuration_of_DataMiner_processes), the output will show the hint paths for each process per process ID. | ||
|
||
> [!NOTE] | ||
> To help with the troubleshooting of assembly resolution issues, from DataMiner 10.4.12/10.5.0 onwards, an entry is also added in the *SLManagedScripting.txt* log file each time DataMiner has loaded or failed to load an assembly. This log entry will include both the requested version and the actual version of the assembly. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters