Scan2x is designed to be as stable and resilient as possible. However, it is always dependent upon external factors like network connectivity, database access, Active Directory performance and more.
If issues with Scan2x arise, it is important to be able to diagnose where the source of the issues are, in order to deal with them quickly and effectively.
We understand that it is not always possible for us to connect remotely from our offices to help with problem-solving due to security policies, and so Scan2x has a comprehensive troubleshooting mode for administrators to help in identifying issues that may occur. To access this mode, log in as an administrator and hit the Ctrl-Shift-TAB keys simultaneously or press the blue question mark button at the top-right corner of the Home Page. The screen below will appear. By clicking the red “Debug Mode” button, it is possible to toggle debug mode on and off.
Debug Mode will automatically log each of the internal processes of Scan2x to a window that will appear. A screenshot of the first tab of this window is reproduced below.
By performing tasks in Scan2x while in debug mode, we can see exactly how long each internal process is taking and how much memory is being consumed.
In the event of an issue, this information will be invaluable for us to be able to help diagnose the source of the problem and provide solutions or recommendations for resolving the problem.
To facilitate this, an “Export To” facility at bottom left of the above screen facilitates the exporting of the debug information to an Excel file or CSV text file, which then can be emailed to our support team on email@example.com. In the interests of security, data confidentiality and transparency the Excel or CSV file can be examined by your IT staff to verify that no user-related or document-related information is being transmitted prior to sending.