The Diagnostic Tool is a software designed to collect relevant system information and detailed JChem for Excel and/or Office logs to help better understand the nature of various problems the user might encounter.
The tool is part of the standard JChem for Office and JChem for Excel installation and can be accessed in one of the following folders (depends on the bit-version of the user’s operating system):
C:\Program Files (x86)\Chemaxon\Tools\Diagnostic Tool (32-bit)
C:\Program Files (x64)\Chemaxon\Tools\Diagnostic Tool (64-bit)
Some options are only available in Administrator mode, so it is recommended to run the tool as an administrator. The figure below shows the Diagnostic Tool window. The tool consists of the following tabs:
The figure below shows the System Information tab.
{info} It depends on the user and the installed programs which parameters are displayed on this tab.
The following system information can appear on this tab:
Operating System: The name and bit-version of the operating system.
User: Lists all users that can use the system.
{info} The Diagnostic Tool collects log files from all users.
.NET Framework(s) and Runtimes: Lists all installed .Net Frameworks and Runtimes. JChem for Office requires .NET Framework 4.6.2 and Visual C++ 2013 SP1 Redistributable. For more information about prerequisites, see Installation.
D3d11.dll version: The version of the Direct3D 11 Runtime.
DirectX Version: The version of the installed DirectX.
Microsoft Office(s): The name, the bit-version, and the version number of the installed Microsoft Office software. In the case of multiple installs on the same machine, all Offices are listed.
Installed Excel Addins read from Registry: The installed Excel add-ins which can be read from the registry.
Installed Excel Addins: The installed Excel add-ins are listed under this.
Installed Excel COM Addins: The installed Excel COM add-ins are listed under this.
MarvinOLEServer.exe Process information: The user name and the associated user id are listed here.
Installed Chemaxon Product(s): All installed Chemaxon products are listed along with their version number and installation folder.
By using the Validate button on this tab, the Diagnostic Tool scans the system and checks if all of the prerequisites are met. The following options are mandatory and always checked:
DirectX version
COM dlls register
Redistributable
Marvin OLE
It is also possible to check for registry errors related to JChem for Office and determine if the correct bit-version is installed or not. Use the following optional options:
JChem for Excel
JChem for Word
JChem for Outlook
JChem for PowerPoint
32 vs 64 bit installation
It is also possible to select all JChem products wit a single click.
In the case of Windows 7 or Microsoft Windows Server 2008 R2, the Diagnostic Tool checks whether the MS Update KB2670838 is installed or not. Without this update, JChem for Excel and JChem for Office cannot be installed, as the update is needed for DirectX technology-based molecule drawing.
After the validation process, the tool lists all registry errors and missing components. The figure below shows a system without the required Redistributable.
In the case of registry-related errors, it is possible to fix them through the Diagnostic Tool, but admin rights are needed for this operation.
The figure below shows a registry-related error, an incorrect LoadBehavior
value.
The figure below shows the Log Settings tab.
This tab consists of the following three parts:
By using the checkboxes, the user can switch the logging level of JChem for Excel and JChem for Office to ALL.
For more information about the logging level options in JChem for Excel and JChem for Office, see the following sections:
General Options in JChem for Excel
General Options in JChem for Office
It is also possible to set the logging level for all users on this computer, by simply using the designated button. The Office application must be restarted after setting the logging level in the Diagnostic Tool.
This option is persistent between sessions.
This tool is installed as part of Visual Studio and is not available otherwise. Displays details for failed assembly binds or missing dependencies.
The fusion log is useful when getting Could not load file or assembly and similar errors as more details are needed to find out the assembly that causes the issue. The fusion log is disabled by default and only can be enabled when the Diagnostic Tool is running in Administration mode.
When the fusion log is turned on the following options became available:
Failures
Enable
Resource Binds
Force
Use the corresponding checkboxes to enable or disable the options.
The fusion logging is automatically turned off when the diagnostic tool is closed.
By using these options, it is possible to enable detailed Visual Studio Tools for Office (VSTO) error messages when loading VSTO add-ins.
Consists of the following options:
Display: Sets the VSTO_SUPPRESSDISPLAYALERTS
variable to 0
. Now the user is presented with a full error of why an add-in is not loading.
Logs: Sets the VSTO_LOGALERTS
variable to 1
. This environment variable allows you to write the error messages to a log file.
The figure below shows the Archive Logs tab.
On this tab, two actions can be initiated, the compressing of the collected logs and the decompressing of the previously compressed files. The log files created by Fusion log are also included in the created archive.
The Diagnostic Tool compresses all collected log files into a single GZip archive.
Specify the destination folder either by using the button or by typing the folder path manually to the field.
Click Compress.
When the process is completed a green checkmark appears near the Compress button.
The Diagnostic Tool extracts the contents of the chosen .gz
archive to the selected folder.
Specify the archive which you would like to be extracted.
Specify the destination folder of the extracted files.
Click Compress.
When the process is completed a green checkmark appears near the Compress button.