Error: (399 [HYT00]) Error in ProcessClientSync. System.Data.Odbc.OdbcException... Connection login timed out. at GFR_LookuplistSync.Database.Execute...

Scenario

You may get an email with either of the following error messages multiple times per day. You may also notice the Lookup List Sync is not working properly and find these errors in the log files.
Error message
(
399
) Error in ProcessClientSync. System.Data.Odbc.OdbcException: ERROR [
HYT00
] [IBM][iSeries Access ODBC Driver]
Connection login timed out
. at GFR_LookuplistSync.Database.Execute(String strSQL, String strDelimiter) at GFR_LookuplistSync.SyncLookuplist.ProcessClientSync(IniFile& objIniFile)
(
399
) Error in ProcessClientSync. System.Data.Odbc.OdbcException: ERROR [
HYT00
] [Microsoft][ODBC SQL Server Driver]
Login timeout expired at GFR_LookuplistSync.Database.Execute
(String strSQL, String strDelimiter) at GFR_LookuplistSync.SyncLookuplist.ProcessClientSync(IniFile& objIniFile)

Cause

These errors may be caused by any of the following:
  • The server hosting the time and billing database is offline.
  • The time and billing database has moved to a different server than where it was when lookup list and the ODBC data source were originally set up.
  • A change to the firewall is not allowing the connection to the time and billing database.
  • Settings for the time and billing database server have changed and no longer allow remote connections.
  • The name of the time and billing database has changed.
  • The login defined in the ODBC connection to the time and billing database has failed.

Solutions

Try these recommended solutions in the following order.
  • Verify that the server hosting the time and billing client database is online.
  • Verify that you are connected to the time and billing program database server.
    Review the Practice CS SQL server troubleshooting article for some resources and information on configuring the Practice CS SQL database.
  • Verify that there is an entry for GoFileRoom under System DSN for ODBC connections.
  • Test the ODBC datasource and update passwords or database names as necessary.
    Review the ODBC Connection to a Database article for resources and information on ODBC connections.

error-icon

error-close