Access Violation Reports
When SBN runs into an access violation, it saves the details of the error to its log file and offers to open the log folder so the file can be sent to Innovative support. Available in SBN 92, build 08.92.0106 and later, and in SBN 95, build 08.95.0028 and later.
The message
SBN shows this message when an access violation occurs:
SBN ran into an unexpected error and saved the details. To help us fix it, click Open Log Folder and send the highlighted file to Innovative support via the SR website.
The original error text appears under the message when there is one.
| Button | What it does |
|---|---|
| Open Log Folder | Opens the log folder in Windows Explorer with the log file for this SBN session highlighted. |
| OK | Closes the message. |
Some errors happen in the background and would otherwise go unnoticed. SBN saves those the same way and shows the message once you pause: no other message or menu is open, SBN is the active window, and the keyboard and mouse have been still for two seconds. SBN shows it once for each error in a session, and at most once every ten minutes for background errors.
When the same error happens again in the same session, SBN shows the standard error message for it. The details are still saved.
Sending the file to support
- Click Open Log Folder in the message.
- Attach the highlighted file, named
pid_<number>.log, to a Service Request on the SR website. - Add what you were doing when the message appeared: the screen, the field, and the last button or key pressed.
To find the file later, choose View > Open Log Folder in SBN. Sort by Date modified and send the files from the time of the error.
If SBN closed on its own with no message, start SBN again, choose View > Open Log Folder, and send the most recent files from before it closed. Include any file named pid_<number>_fault.log.
What the file contains
| Detail | Notes |
|---|---|
| The error | The kind of error and where in SBN it happened. |
| Open screens | The SBN screens that were open and which field had the focus. |
| Recent actions | The last buttons, menus and fields used, by name. |
| Timers | The background timers that were running. |
| Loaded components | The program files SBN had loaded. |
| Windows Event Log | Entries from the 30 minutes before the error. Crash entries that name SBN include their text. System and Microsoft Defender entries are listed by time, source, event number and level. |
SBN leaves typed characters, field contents and window titles out of the file.
Limits
- SBN saves full details for the first three occurrences of the same error in a session and counts the rest.
- SBN saves up to 40 errors per session.
- When SBN closes without being able to save the error and the workstation uses SBN Tunnel, one line noting that SBN ended unexpectedly, with its exit code, is added to the log file.
- SBN deletes log files older than seven days.
Where the log folder is
SBN writes its log files to the log folder beside SBN.exe. When SBN cannot write there, it uses a log folder under %LOCALAPPDATA%\IBS\. View > Open Log Folder always opens the folder in use.
The folders that hold SBN's settings files are listed in Settings File Locations.