The spanner at the bottom left of the log on window opens the diagnostics window. It is meant for the moment something does not work and the question is what the device, the licence or the installation actually says, and it is reachable before logging on precisely because logging on is what often fails. It is the same window in every Invantive product for Microsoft Windows, and it carries six tabs. ## Actions The first tab is a list of buttons, each of which opens something rather than reporting something. The upper four belong to the product: - "Agreement": the licence window, so that a licence can be registered or replaced; see [[Invantive UniversalSQL/General/License Registration|License Registration]]. - "Preferences": the settings of the product. - "Settings": the [[Settings]] file with the databases. - "Stay informed": the choices about news and announcements. ![[20260809-diagnostics-actions.png]] Under those sit the ones which open something outside the product: "Open Invantive settings folder" opens the configuration folder in Windows Explorer, "Save Microsoft DebugView executable" writes out the tool with which the [[Trace]] messages can be watched, and "Programs and Features", "Network Connections", "Windows Firewall", "Regional Settings", "Registry Editor", "Task Manager" and "Performance Monitor" open the corresponding part of Windows. "NET Garbage Collection" asks the .NET runtime to free memory now. It is a measurement aid rather than a repair: it tells whether memory is actually held, not whether something is wrong. ## System The second tab reports what a support case needs first: which version is installed, on what, and since when. ![[20260809-diagnostics-system.png]] It states the product and its version, the build tag and the build date, whether Microsoft Office is integrated and which VSTO version is present, the operating system, whether it runs on a terminal server or in a virtual machine, the name of the device, the site, the Invantive Installation ID, the user, the physical memory, the uptime and the version of Microsoft .NET. The Invantive Installation ID identifies this installation in the messages Invantive receives, so quoting it in a support case saves a round of questions. ## Authorizations The third tab lists every function the product knows, with per function whether it is licensed, whether changing is allowed, whether changing is licensed, whether it appears in the menu, in which module language it sits and its description. ![[20260809-diagnostics-authorizations.png]] This is the tab which answers "why does this button not work": a function which is not licensed, or not allowed, is absent from the menu rather than present and refusing. The list carries the grouping bar, the sorting and the filters described in [[Lists]], so the function in question can be found by typing part of its name into the filter of the "Function" column. ## Data The fourth tab lists what the product has stored on this device and lets it be thrown away, one topic at a time, with the bin behind it. ![[20260809-diagnostics-data.png]] The topics are the use of the [[Invantive Keychain]], the passwords remembered, and the images cached. "Elements" states how many there are. Removing a topic costs nothing but the convenience it provided: the keychain and the remembered passwords are asked again on the next log on. ## Logging The fifth tab holds one action: "Copy" places the trace log of the current session on the clipboard, ready to be pasted into a support case. ![[20260809-diagnostics-logging.png]] Only what has been collected in this session is copied. Tracing has to be switched on for there to be anything to copy, and how that is done is described in [[Trace]]. ## Event Log The sixth tab shows the Windows event log itself, with a selector at the top for which log to read; "Application" is where the entries of the Invantive products end up. Per entry it shows the identifier, the type, the source, the moment, the message, the user and the device. There is no screenshot of this tab here, since it shows the events of whichever device it runs on. The tab exists so that the Windows event viewer does not have to be opened separately when an Invantive product reports a problem: the entries of the product stand between those of Windows itself, which is often what makes clear whether the cause lies with the product or with the device.