Troubleshooting

Common and/or unexpected errors, troubleshooting

No results showing or results from the wrong language (SL, TL)

When you get no results (or wrong results) for a particular search even with all the correct parameters, sometimes you just need to refresh the values of Source Language and Target Language. To do this click Source Language, then click Target Language and back on Source Language. Do the opposite if the initial selection is Target Language.

In addition, you may want to reselect the search type: Normal, Full Text or Fuzzy.

Another simple solution when no results are showing is to simply use the opposing arrows icon ⇅ to reverse SL and TL.

In all other cases, that information being searched most likely does not exist in the Termbase.

Language name missing while exporting by date

In some rare instances when exporting data by date, in the Language column you will see "---?---" instead of a language name. This is not a Tb-Scout v3.3 error but rather an internal inconsistency in the XML data for some records in which, for an unknown reason, instead of a language name there is either a number or there is no value.

We decided to code this error as "X ---?---" when there is a value X, instead of a language name, and as
"---?---" for null values.

Although the name of the language is missing, the rest of the information in the other columns is correct.

XML settings file cannot be accessed

Error message: "The process cannot access the file 'C:\Users\[UserName]\AppData\[…] \BaseSettings.xml […] being used by another process." Click OK and ignore. See explanation in the table below.

Discard backup files

You can safely remove this useless file as well as other leftover files called database.mdb or database[N].mdb. See explanation in the table below.

List of other known issues and errors

While this list may not be comprehensive, it does include the issues that might occur, though not expected, when running Tb-Scout v3.3. Considerable time and effort have been devoted to prevent these issues from creeping in. However, some errors, very few of them (practically none), might persist in any given circumstance or simply they are unavoidable.

Issue	Error text, description	What to do, comments
Application creates a backup copy	When the application fails mostly due to the limitations of Microsoft Access, it tries to save a backup copy.	Do not save that backup file. That file, as well as a temporary file that sometimes remains in the folder, called database.mdb, or databaseN.mdb (N= number) is useless. You can safely delete them all.
Application does not close completely	Sometimes Tb-Scout v3.3 closes but leaves behind the Microsoft Access window open.	In the Windows taskbar hover over the application icon, and then move the pointer to the upper right‑hand corner of the tiny window and click the X to close the application.
Date format	In some locales 3-Sep-17 may be interpreted as 9-Mar-17, given that 03/09/17 and 09/03/17 are similar.	Be aware of this issue when selecting data to export by date.
File access, settings	"The process cannot access the file 'C:\Users\[UserName]\AppData\[…] \BaseSettings.xml […] being used by another process".	It seldom occurs. Ignore and continue. It is not known, at least not to the developer, what is the use of the BaseSettings.xml file, which sometimes is just an "empty" XML file. See also below "Unable to open..."
File access, settings	"Couldn't use <filename>; file already in use."	Try again to open the application. This may happen after you opened a second instance, which is not allowed.
DDE channel message	"The source application is not responding. Do you want to continue waiting? […] The DDE channel […]"	The application has been opened for a while without any action. Press "No". Ignore. Dynamic Data Exchange (DDE) is how Tb-Scout v3.3 interacts with SDL Termbases.
Read-only Termbases	Marked with a red asterisk to the left of their names.	Read-only Termbases may have an unexpected behavior if you try to export data. However, just searching through them may work normally. See Scope and limitations. See also Other Useful Functions.
Selecting an item in a list	"The text you entered isn't an item in the list."	Make sure you select an item that you can see in the pull-down list. You will not be able to continue unless you select an item in the pull-down list.
Selecting records to export	"You selected more records than can be copied onto the Clipboard at one time. Divide the records […]"	Export to PDF format instead of Excel format. Excel may open, though, but with truncated data.
Potential security concern	"A potential security concern has been identified. Hyperlinks can be harmful […]when trying to access the history file or, seldom, under other circumstances.	The application is safe. Ignore and continue by pressing 'Yes'.
Unable to open the application	"Couldn't use 'TbScout.v20_20xx.accde'; file already in use."	Make sure all instances of Microsoft Access are closed. If need be, open Windows Task Manager and go to the Details tab. Search for MSACCESS.EXE, select it and then click "End task".
Random error message	"We're sorry, but Access has run into an error that is preventing it from working correctly [...]"	Another Microsoft Access random error, though it seldom occurs. There is nothing to repair, so ignore "Repair Now". Just click on Close. Restart the application if need be.
The application is requesting "Select Data Source" in a separate form...	A dialog box opens up after you selected "Tb" and then clicked the Open button. This is a very rare occurrence. Possible cause: when switching back and forth between the Tb and TM modules.	Cancel. Ignore subsequent messages. Then, select "TM", click Open and then again select "Tb" and click Open. If the error persists, you may need to close and reload the application.
Error 2501	"The Open Report Action was canceled."	When a huge dataset cannot be exported because somehow exceeds the capacity of the application. This is one of the limitations of the application. You may want to try and create a PDF report (a bilingual dictionary) instead.
Error 2908	Unable to open the application: "The database cannot be opened because the VBA project contained in it cannot be read […]"	Make sure you have either the correct and most recent Microsoft Access full version or the free Microsoft Access run-time version installed. No need to create backup copies.
Error 3021	"No current record."	This error occurs when, for instance, there is a discrepancy between a Descriptive Field registered in the Termbase and non-existent data "linked" to that Descriptive Field. In the Export Module, verify this with the "All Descriptive Fields" pull-down list.
Error 3035	"System resources exceeded."	It might happen when trying to process data for the Export Module. If you press [OK] and continue, you may still see the Export Module form, but from there performance is not guaranteed.
Error 3046	"Could not save; currently locked by another user."	This is a transient situation. Press OK. Ignore and continue. The Export Module form will still open in most cases.
Error 3049	"Cannot open database ''. It may not be a database that your application recognizes, or the file may be corrupt."	It may be a number of issues. Mainly data exceeds Microsoft Access 2 GB limit. Retry opening the Termbase. Ignore and continue. It may also be a false positive.
Error 3059	"Operation canceled by user."	Ignore and continue.
Error 3420	"Object invalid or no longer set"	Seldom occurs. Restart the application.
Error 3531	"The wait period for an event has timed out."	Try again to see if the process completes. In most cases the Export Module will open next. Otherwise, restart the application. You may want to use process 3a. only or the application definitely cannot handle that Termbase.
Error 70	"Run-time error '70': Permission denied"	This seldom, if ever, happens. When you try to open another instance of Tb-Scout. Remember, only one instance is allowed at a time. Close any open instance. Restart.
Error 94	"Invalid use of Null."	Please report this error to the developer.
An old MultiTerm error message	"This Termbase cannot be opened because it was created with an unsupported version of MultiTerm."	Please note this is an MultiTerm issue, not a Tb‑Scout v3.3 issue. Consult RWS Support.
Error 3001	Unable to export a multimedia item	This may only happen when a Termbase is encrypted and/or read-only.
Error 3078	"...Microsoft Access database engine cannot find the input table or query..."	(Random) run-time error with no consistent explanation. Ignore and continue working. Try the same search and most likely this error will not show up again.
"Cannot Open Termbases"	"This Termbase has been created with an older version of MultiTerm and needs to be updated. This can take several minutes. Continue opening Termbases?"	A very unusual and odd error, directly related to MultiTerm, not to Tb-Scout v3.3. It may happen with any MultiTerm version. Whether you say "Yes" or "No" the selected Termbase will not open. Also, ignore that long warning. However, if you try to open the Termbase directly using MultiTerm Desktop, it will work.
"Cannot Open Termbases"	"[...] cannot open or write to the file Files [...] already opened exclusively by another user [...]	This rare, long and confusing message has to do with the Termbase itself. It may also be related to the the error below. Try again. This quirky and random error is a false positive.
"Cannot Open Termbases"	"This Termbase cannot be opened because it has been created with an unsupported version of MultiTerm."	This is a MultiTerm Desktop error, not a Tb-Scout v3.3 error. Another false positive.
"Microsoft Access was unable to open the file [...].accde [...]"	"The file may not be an Access file [...] To repair the file manually [...]"	This random and very long error message does not apply to Tb-Scout v3.3. It's a false positive. Nothing to repair. Ignore. Restart the application.
"Error -nnnnnnn [Microsoft][ODBC Driver Manager]..."	"...Data source name not found and no default driver specified"	An ODBC driver for SQLite is missing. Install it to be able to use the TM module.
The Termbases Module loses connection ("...problem with the connection to the Termbases Explorer...")	In rare occasions the Main module (the Termbases Explorer, by default) loses database connections after the Translation Memories Explorer is or has been opened.	You can ignore this error and then try to open the same or a different Termbase again. If the error persists, close and restart the application. As a secondary effect of this loss of connectivity, connecting to MultiTerm Desktop will also fail.