TROUBLESHOOTING

Here are some tips for troubleshooting problems with your database. If you cannot resolve the issue, customer support can be reached M - F 10:00 am to 5 pm Eastern Time at 619-284-8013, or by email at support@libertylabs.com. Support is free for the first year after you purchase your license, and you may extend your support by purchasing an annual support contract after the first year.

 

Installation

If you are having trouble installing your application, please follow the installation instructions provided. The instructions include a checklist for you to complete as you install the application. If you are getting an error message from your network or from SQL Server, try searching online for the text of the error message, or checking the Microsoft site for information. If you are unable to find a solution, and do not see the answer below, below or contact us for assistance.

 

Opening the Desktop or Client File

In order to open the desktop application or the user interface for the client/server edition, you need to have Microsoft Access 2010, Service pack 1, or Microsoft Access 2013. If you do not have the full version of Access, you can install the free run-time edition.

 

Citrix

When setting up the database using a Citrix server, you need to set up a User Profile for the application.

 

Multiple Users

For the standalone desktop edition only:

If multiple users are unable to open the database at the same time, please check the following:

  1. All users need to have full permissions for the folder where the database is stored. They need to be able to create a file in that folder in order to create the .ldb file needed to run the application.
  2. If you have an Adobe® Acrobat® add-in installed in Access®, you will need to remove it.
  3. Microsoft® Access® needs to be set to open in shared mode. Go to each computer, open Access®, and go to Tools > Options > Advanced.  Make sure the “Default open mode” is set to “shared”.
  4. When everyone has the database closed, look in the folder where the database is stored and see if there is a file called “TRAINTRACKx.ldb. This will be a very small file. If you see this file, delete it. This is the database locking file that should disappear when everyone closes the database. IMPORTANT: Make sure the file you are deleting has the "ldb" file extension. If you can't see the file extensions, go to your Windows® Explorer options screen and un-check the box "hide extensions for known file types".
  5. If the users are opening the program using a shortcut, try browsing to the file instead. If this works, you can try deleting the existing shortcut and then creating a new separate shortcut for each user (don’t copy and paste it, it has to be a new one for each user).
  6. If you are unable to use a shortcut, open Access® first and go to File > Open, then open the application.
  7. In some cases, all users need to have the exact same permissions for the Windows® folder where the database is stored.
  8. If you are still unable to share the file, you might want to consider upgrading to the client/server edition, where each user has their own copy of the user interface connected to a shared back-end database. The client/server model is the preferred way to share the database.

 

Linked Files

If you are unable to open hyperlinks to .pdf files, follow these steps:

This is a Windows® setting. Set .pdf file types to be opened using Internet Explorer® and you will be able to open the files. You will need to locate this setting based on the Windows® version you are using.

 

SQL Server®

For the Client/Server edition only:

If you are unable to connect from the client to the server:

  1. Make sure SQL Server® is running.
  2. Stop and re-start your SQL Server if you have made any changes.
  3. Make sure you have correctly identified the server name in the ODBC connection.
  4. From Linked Table Manager, try creating a NEW ODBC connection, and over-writing the original one.
  5. Make sure the user is listed as a user in SQL Server® 

    1. On your server, start SQL Server® Management Studio.
    2. Click Connect (top left) and connect to your server.
    3. From the tree at the left, select Security > Logins.
    4. Right-click and select New Login.
    5. Add the windows group that contains the users of your TRAIN TRACK® application. If you do not have an appropriate group, then you will have to add the users individually.
    6. In 'default database', select the database you want to have them automatically log into (this will be “TRAINTRACK” if you installed it using the default name).
    7. In user mapping, check the TRAIN TRACK® database. In database role membership, check db_datareader and db_datawriter. This will give them read and write access to that database. 
    8. To set up the ODBC connection, go to the client computer and set it up using Windows authentication.
    9. Now everyone in that windows group should be able to connect using windows authentication. In the future when someone needs to have access, just add them to the windows group and set up the ODBC connection on their workstation.

  6. If you are using a group for login permissions and it is not working, try creating a login for an individual user.
  7. Make sure SQL Server® is set to accept remote connections.

    1. Open SQL Server® > Configuration Tools > SQL Server® Surface Area Configuration.
    2. Under Surface Area Configuration for Services and Connections, click on remote connections, and select to allow both TCP/IP and named pipes.

  8. Make sure the database is set to allow both Windows and SQL authentication.
  9. If you get an error “SQL State 08001 SQL Server Error 2 Could not open a connection to SQL Server (2)”, check your Windows firewall settings and make sure the application is not being blocked.
  10. Make sure there is not a firewall blocking port 1433 or 1434.
  11. Check to see if you have an error log file located at %ProgramFile%Microsoft SQL Server/MSSQLxx.xxx/MSSQL/Log.
  12. Check your ODBC driver. Verify that you are using the SQL Native Client driver, 10 for SQL 2008 or 11 for SQL 2012.
  13. Make sure your ODBC DSN is “TTSERV”.
  14. Make sure the user has full permissions under your Windows security settings for the folder where the client database is stored.
  15. Open a new Access database and attempt to link to and open the data tables with your ODBC connection. If this fails, then the problem is with your connection and not with the application.

 

Web

For the web edition only:

  1. Make sure the web server is running.
  2. Make sure it is set to allow 32-bit applications.
  3. Make sure .asp pages have been enabled.
  4. Check your ODBC connection or your connection string.
  5. Make sure there is not a firewall blocking port 1433 or 1434.
  6. Make sure your users have permission as datareader/datawriter in the database.
  7. Make sure you have "ttuser" with permission as datareader/datawriter in the database.
  8. Make sure the IUSR account has permission as datareader/datawriter in the database.
  9. Check to see if you have an error log file located at c:/ProgramFiles/Microsoft SQL Server/MSSQLxx.xxx/MSSQL/Log.
  10. Try using SQL authentication. To connect using SQL authentication, add a user to the SQL database, set up the ODBC with SQL authentication, then add the user name and password to the connection file.
  11. Try using a connection string.
    1. If you are unable to view any data, you can replace the ODBC connection with a connection string. To do this:
    2. Open the folder where you installed the web pages.
    3. Open the file Connections/TTSERV.asp. You can open it using Notepad or your web authoring tool.
    4. Replace the existing text with your connection string. Connection strings will vary depending on your configuration. Below are some example strings

Example A:
<%
Dim MM_TTSERV_STRING
Set MM_TTSERV_STRING = Server.CreateObject("ADODB.Connection")
MM_TTSERV_STRING.Open "Provider=SQLOLEDB;Data Source=MYSERVER\MYSQL;" _
    & "Initial Catalog=TRAINTRACK;User Id=ttuser;Password=22user;" _
    & "Connect Timeout=15;Network Library=dbmssocn;"
%>
Substitute the name of your actual server and SQL instance for MYSERVER\MYSQL. If you don’t know what this is, open the SQL Management studio. A box will open asking you what database to connect to. This is what you need to use in the string. For example, for the server shown in the box below:

SQL Login

The string would be:
<%
Dim MM_TTSERV_STRING
Set MM_TTSERV_STRING = Server.CreateObject("ADODB.Connection")
MM_TTSERV_STRING.Open "Provider=SQLOLEDB;Data Source=BESSIE\SQL2008;" _
    & "Initial Catalog=TRAINTRACK;User Id=ttuser;Password=22user;" _
    & "Connect Timeout=15;Network Library=dbmssocn;"
%>

Example B:
<%
Dim MM_TTSERV_STRING
Set MM_TTSERV_STRING = Server.CreateObject("ADODB.Connection")
MM_TTSERV_STRING.Connectionstring = "Provider = SQLOLEDB; Data Source = MYSERVER\MYSQL; Initial Catalog = TRAINTRACK; User Id=ttuser; Password=22user"
MM_TTSERV_STRING.Open
%>


Save the file, and test your web pages.

Error Messages

No records found or there was an error printing your report

If you are sure there should be data for the report (you have training set up as required and completed) it may be caused by not having a printer configured. You need to have a printer set up even if you only want to view and not actually print the reports, because the program needs to know how to set up the report on the page.

Overflow

If you get an "overflow" error when importing data, this may be caused by having some dates in your database that the computer can't recognize, such as a date of "1/1/122".

The VBA Project Cannot be Read

If you get a message that the VBA project cannot be read, verify that you have Microsoft Access 2010 with Service pack 1, or Microsoft Access 2013. If you do not have the full version of Access, you can install the free run-time edition.