The following section explains the error messages that can appear in the error log file and how to resolve them.
Access the error log
-
The log file location and name are $FASLOGDIR/newhire3Boh.log.
-
Each error entry includes:
-
Error message from err_get(status).
-
User ID that ran the report.
-
Server name and process ID.
-
Database information (version, path, name).
-
Stack trace showing the function call sequence.
-
Error log messages
The following table lists the error log messages, their descriptions, and how to resolve them.
|
Error Code and Message |
Description |
How to Resolve |
|---|---|---|
|
A FATAL ERROR OCCURRED; PROCESS IS TERMINATING FOR USER [username] |
A critical runtime or database error occurred, causing the program to crash. |
Review the full error log entry, which includes the specific error code, server name, process ID, and stack trace. Contact your system administrator with this information. Common causes include database connectivity issues, memory problems, or data corruption. |
|
Error Code: -206 Error Message: The specified table is not in the database |
The program is attempting to access a nonexistent database table. |
Verify that the database schema is correct and that all required tables (employee, person, empuser, vendor, vnduser, hrmstate, hrm_prof, fam_prof) exist. Run database verification scripts if needed. |
|
Error Code: -217 Error Message: Column not found in any table in query |
A database column referenced in the query doesn't exist. |
Verify database schema version matches the program version. Check that all required user-defined columns exist (e.g., empuser.ftext10, vnduser.ftext1-ftext9, vnduser.tcode1-tcode3). |
|
Error Code: -239 Error Message: Could not insert new row - duplicate value in a UNIQUE INDEX column |
Attempting to insert a duplicate record. |
Check for duplicate employee numbers or SSNs in the source data. Verify the data hasn't already been processed. |
|
Error Code: -243 Error Message: Could not position within a file via an index |
Database index corruption detected. |
Contact your DBA to rebuild the affected indexes on the employee, empuser, vendor, or vnduser tables. |
|
Error Code: -244 Error Message: Could not do a physical-order read to fetch next row |
Database table or data corruption. |
Contact your DBA to run database consistency checks and repair utilities. |
|
Error Code: -271 Error Message: Could not insert new row into the table |
Cannot insert a new record, possibly due to constraint violation or disk space. |
Check disk space on the database server. Verify all required fields have valid data. Check for constraint violations. |
|
Error Code: -310 Error Message: Table is locked |
Another process has locked the required table. |
Wait for the other process to complete, or contact your DBA to identify and resolve the lock. Ensure no other Ohio New Hire reports are running concurrently. |
|
Error Code: -346 Error Message: Cannot connect to database server |
Database connection failed during processing. |
Verify the database server is running and accessible. Check network connectivity. Verify database credentials are correct. |
|
Error Code: -391 Error Message: Cannot open file |
Unable to create or open the output report file. |
Verify that the output directory exists and that the user has write permissions. Check disk space on the server. Verify the $FASLOGDIR and report output paths are accessible. |
|
Error Code: -1204 Error Message: Cannot lock the row |
Unable to obtain a row lock for update. |
Wait and retry the operation. If the issue persists, contact the DBA to check for blocking processes or deadlocks. |
|
Error Code: -1213 Error Message: Deadlock detected |
A deadlock occurred between database processes. |
Retry the report. If recurring, contact the DBA to analyze deadlock patterns and optimize the database. |
|
SQL VERSION: [version] DB NAME: [dbname] |
An informational message that indicates the SQL Server version and database name. Used for troubleshooting to identify the environment. |
Not applicable |
|
DBPATH: [path] DB NAME: [dbname] |
An informational message that displays the path to Informix databases. Used for troubleshooting to identify the environment. |
Not applicable |
|
The error occurred on the server [servername] and the process ID was: [pid] |
An informational message that identifies which server and process encountered the error. Use this to locate the specific process for further investigation. |
Not applicable |
|
Stack Trace: [detailed trace] |
A diagnostic message that shows the program execution path leading to the error. |
Provide this information to support/development for debugging. It shows which function calls led to the failure. |
|
Error Code: -674 Error Message: Routine not found |
A required library function is missing. |
Verify all required library files are installed and accessible. Contact the system administrator to reinstall or update the application. |
|
Error Code: -8000 to -8100 Various network errors |
Network communication errors with the database. |
Check network connectivity, firewall rules, and database listener configuration. |
|
Error Code: -111 Error Message: ISAM error: no free disk space |
Disk space exhausted. |
Free up disk space on the database server and file system where reports are generated. |
|
Error Code: -104 Error Message: Illegal database name or path specification |
Invalid database configuration. |
Verify that the environment variables SPIDBNAME and DBPATH are correctly configured. |
|
Error Code: -329 Error Message: Database not found or no system permission |
Cannot access the finplus database. |
Verify that the database exists and that the user has appropriate permissions. Check SCHEMA finplus connectivity. |
General troubleshooting steps
-
Check the log file at $FASLOGDIR/newhire3Boh.log immediately after the error.
-
Note the error code: negative numbers indicate SQL/database errors.
-
Review the stack trace to identify which operation failed.
-
Verify database connectivity and user permissions.
-
Check disk space on both the database server and the application server.
-
Ensure no concurrent processes are locking the same tables.
-
Contact your DBA for database-related errors (-200 to -400 range).
-
Contact support with the full log entry for unresolved issues.