Foxhound 5.0 FAQ
search engine by freefind advanced
Foxhound 5.0 FAQ Home      Foxhound Home      RisingRoad      Breck.Carter@gmail.com     


Messages


-1066, SQLSTATE = WO027, ERRORMSG() = File system error: ..., @batch_is_ok = "Y", @batch_number = "0", @sampling_id = "0"
-1188 LOAD TABLE error: The data to load is not encrypted
-307: All threads are blocked
-308 Connection was terminated
-602 Cannot access file ... Permission denied SQLCODE=-602
-757 Modifications not permitted for read-only database
-81: DBSPAWN ERROR: -81
-840 Incorrect or missing encryption key
-851 Decryption error: Missing encryption key
0: dbspawn/dbsrv17 set ERRORLEVEL = 0
011c-irpl1(011c-irpl1) Info: Unique index collision avoided: ping_id = ... ping_log_inserted_at = ... sampling_id = ...
015a-a1d: Unacceptable SQL Anywhere server edition: The database engine is stopping.
1: Client address backtrace: ::1
1: dbspawn/dbsrv17 set ERRORLEVEL = 1
1: Error - File output check failed with return code 1
1: ERRORLEVEL from dbstop: Unable to stop database server -- Request to start/stop database denied.
121;42501;Permission denied: you do not have permission to execute the procedure "sa_server_option"
1730: You must be an Administrator to remove this application. - Error 1730.
206b2a(206eh4) SQLCODE = -196, SQLSTATE = "23505", ERRORMSG() = "Index 'ix_ping_inserted' for table 'rroad_ping_log' would not be unique"
2203: Internal Error 2203: C:\Windows\Installer\597604a.ipi,-2147287035
23: I/O error Fatal error: A disk read from file "...\foxhound5.db" failed with error code: (23) -- transaction rolled back --
255: dbspawn/dbsrv17 set ERRORLEVEL = 255
3: dbspawn/dbsrv17 set ERRORLEVEL = 3
404: Not Found
408: Request Time-Out
40W06: All threads are blocked
503: Service Temporarily Unavailable
532 ... Info: ... out of range ...
532 ... Limit of 100 "Info: out of range" messages per Foxhound connection to one target database has been exceeded
57014: Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
660 Incorrect syntax near the keyword 'TRANSACTION'
9: ERRORLEVEL from dbstop: Unable to stop database server -- Database server not found.
9 Mini-Restore ... foxhound5.db not found
990xx: Internal error
A disk read from file "...\foxhound5.db" failed with error code: (23) -- transaction rolled back --
A subdirectory or file backup already exists.
Access is denied.
Activation exception: SQLCODE = ... SQLSTATE = ... ERRORMSG() = ...
ALERT ...
ALL CLEAR ...
All threads are blocked
An attempt to start sample loop event ... for sampling id ... failed because event ... was already running for that sampling id.
Another version of this product is already installed.
architecture mismatch between the Driver and Application
bad call to rroad_update_rroad_global_options: column = "...", value = "..."
CANCELLED ...
Cannot access file '...' -- The system cannot find the file specified
Cannot access file ... Permission denied SQLCODE=-602
Cannot access ... foxhound5.db ... another process may be using the file
Cannot convert '...' to a timestamp
Cannot CREATE PROCEDURE rroad_...
Cannot open transaction log file
Can't open Message window log file: foxhound5_debug.txt
Can't start HTTP listener on address 0.0.0.0:80
Can't start HTTP listener on address 127.0.0.1:80
Can't start HTTP listener on address (::):80
Can't use log file
Choose a connection string.
Choose an ODBC DSN.
Client address backtrace: ::1
CollectStatistics
conn file was missing
Connection "..." by user id "..." rejected during post-setup data upgrade process.
Connection error: No IP address found for ...
Connection was dropped
Connection was terminated
CONNECTION_PROPERTY ... out of range ...
Could not bind to address 0.0.0.0:80
Could not execute statement. Modifications not permitted for read-only database SQLCODE=-757
CREATE PROCEDURE rroad_..._properties failed ... Modifications not permitted for read-only database
Data cannot be copied from an old Foxhound database that has never been activated.
Data cannot be upgraded from ... to ...
Database server connection limit exceeded
Database server shutdown due to startup error
DB_PROPERTY ... out of range ...
DBSPAWN ERROR: -81
dbspawn/dbsrv17 set ERRORLEVEL = 0
dbspawn/dbsrv17 set ERRORLEVEL = 1
dbspawn/dbsrv17 set ERRORLEVEL = 255
dbspawn/dbsrv17 set ERRORLEVEL = 3
dbsrv -k
Decryption error: Missing encryption key
Decryption error: Missing encryption key SQLCODE -851
DIAG ... Data cannot be copied from an old Foxhound database that has never been activated.
Do not attempt to UPDATE rroad_connection_string.connection_string_name
DUMMY' could not be found
Email not sent because Alert Emails were disabled.
Email not sent because no Alert email address was provided.
Email not sent because of the Alert Email Schedule.
Email not sent because sampling is offline.
Error - File output check failed with return code 1
Error 1730. You must be an Administrator to remove this application.
Error: Cannot access file '...' -- The system cannot find the file specified
ERROR ... DIAG ... Data cannot be copied from an old Foxhound database that has never been activated.
Error in syntactical analysis: Invalid or missing keyword near 'CPOOL‘.
Error in TCPIP port options
Error: Procedure rroad_connection__properties build number ... is more recent than Foxhound build number ... on ...
Error: Procedure rroad_connection_properties build number ... is different from the Foxhound build number ... on ...
Error: Procedure rroad_database_properties build number ... is different from the Foxhound build number ... on ...
Error: Procedure rroad_database_properties build number ... is more recent than Foxhound build number ... on ...
Error: Procedure rroad_engine_properties build number ... is different from the Foxhound build number ... on ...
Error: Procedure rroad_engine_properties build number ... is more recent than Foxhound build number ... on ...
ERROR SQLANY17 environment variable not set properly.
Error: SQLCODE = ..., SQLSTATE = ..., ERRORMSG() = ...
ERROR The $post_setup.bat file could not MOVE the new foxhound5.db file to the FOXHOUND5 folder
Error! The connection to the database was closed by the server. Connection was terminated SQLCODE=-308
ERRORLEVEL = 0 from dbspawn/dbsrv17
ERRORLEVEL = 1 from dbspawn/dbsrv17
ERRORLEVEL = 1 from dbstop: Unable to stop database server -- Request to start/stop database denied.
ERRORLEVEL = 255 from dbspawn/dbsrv17
ERRORLEVEL = 3 from dbspawn/dbsrv17
ERRORLEVEL = 9 from dbstop: Unable to stop database server -- Database server not found.
EXCEPTION in EVENT rroad_... at ...: SQLCODE = ..., SQLSTATE = ..., ERRORMSG() = ...
EXCEPTION in PROCEDURE rroad_... at ...: SQLCODE = ..., SQLSTATE = ..., ERRORMSG() = ...
EXCEPTION SQLCODE = ..., SQLSTATE = .., ERRORMSG() = ... in patch file "..."
Extended Edition already activated ... Unexpected situation
failed to delete a file after it was processed
failed to move a leftover file to the rejected subfolder
File access denied.
file is unavailable
File output check failed with return code 1
File system error: ... SQLCODE=-1066
Fill in the "Connection Strings file:" field and press Save before clicking on ...
Foxhound:-121;42501;Permission denied: you do not have permission to execute the procedure "sa_server_option"
Foxhound can only be started with the SQL Anywhere database name set to "f".
Foxhound Extended edition is required for ...
Foxhound needs JavaScript to be enabled.
Foxhound now accepting requests
Foxhound requires target PROPERTY ( CollectStatistics ) = Yes; i.e., do not specify dbsrv -k - sampling stopped at
Foxhound supports 100 sessions
Foxhound was not available yet, probably because the Foxhound engine had not finished starting up.
foxhound5.db not found ... 9 Mini-Restore
Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
Handler for event 'rroad_scheduled_purge' caused SQLSTATE '57014'
Hash error in patch file "..."
However, version ... is actually being used.
HTTPValidityCheck failed on the Monitor Options page; input values ignored
I/O error Fatal error: A disk read from file "...\foxhound5.db" failed with error code: (23) -- transaction rolled back --
Incorrect or missing encryption key ... Exception in load_OFSS_samples
Incorrect syntax near the keyword 'TRANSACTION'
Index 'ix_ping_inserted' for table 'rroad_ping_log' would not be unique
Info: HTTPValidityCheck failed on the Monitor Options page; input values ignored.
Info: Mini-restore succeeded using file ...
Info: Option 1 displayed: Activate Foxhound with a Registration Key
Info: Option 2: Activate Foxhound with a Mini-Restore is not offered because Foxhound is already activated.
Info: Option 2: Activate Foxhound with a Mini-Restore is not offered because no mini-backup files matching build number ... were found.
Info: Option 2: Activate Foxhound with a Mini-Restore is not offered because the Foxhound folder was not found.
Info: Option 2: Activate Foxhound with a Mini-Restore is not offered because the sampling tables are not empty.
Info: Option 2 displayed: Activate Foxhound with a Mini-Restore
Info: Procedure rroad_connection_properties has been upgraded [from build number ...] to build number ... on ...
Info: Procedure rroad_database_properties has been upgraded [from build number ...] to build number ... on ...
Info: Procedure rroad_engine_properties has been upgraded [from build number ...] to build number ... on ...
Info: Unable to execute ... rroad5 ...
Info: Unable to read ... rroad5 ...
Info: Unique index collision avoided: ping_id = ... ping_log_inserted_at = ... sampling_id = ...
input schema version ... is not compatible with the Foxhound build number ...
input values ignored
Internal Error 2203: C:\Windows\Installer\597604a.ipi,-2147287035
Internal error 999xx
Internal error; bad call to rroad_update_rroad_global_options: column = "...", value = "..."
Internal error: Do not attempt to UPDATE rroad_connection_string.connection_string_name
Internal error: No code exists to validate connection-level property ...
Internal error: Retry loop failed to find a Top Sample or Most Recent Sample to display.
Invalid database engine command line
Invalid database server command line
Invalid or missing keyword near 'CPOOL‘
Invalid server and/or database name: The database engine is stopping.
Invalid user ID or password
LOAD TABLE error: The data to load is not encrypted
LOAD TABLE error: The data to load is not encrypted SQLCODE -1188
Management of procedure rroad_ ... _properties failed on ...: SQLCODE = ..., SQLSTATE = ..., ERRORMSG() = ...
Mini-restore exception: SQLCODE = ... SQLSTATE = ... ERRORMSG() = ...
Mini-restore failed: the build number was different
Mini-restore failed: the DB_PROPERTY ( FILE ) was unavailable
Mini-restore failed: the sampling tables were not empty
Mini-Restore ... foxhound5.db not found
Mini-restore succeeded using file ...
Missing encryption key
Missing encryption key SQLCODE -851
Modifications not permitted for read-only database ... CREATE PROCEDURE rroad_..._properties failed
Modifications not permitted for read-only database SQLCODE=-757
Modify, repair, or remove the program.
moved a leftover file to the rejected subfolder
No code exists to validate connection-level property "..."
No complete sample data is available for display in the "Top Sample" section for this database.
No detailed information about blocked connections is recorded for the sample taken at ...
No detailed information about the ... connection(s) is recorded for the sample taken at ...
No information about ... connections has been gathered yet.
No information about ... connections is available for the sample lost at ...
No information about this database is available for display in the "Monitor Status Area".
No information about this database is available for display in the "Sample History Status Area".
No IP address found for ...
No OFSS batches were found
No patches were processed.
Not Found - 404
OFSS batch (file "...") was rejected because the OFSS build number ... is not compatible with the Foxhound build number ...
OFSS batch number ... (file "...") was rejected because it had been previously processed.
OFSS batch number ... (file "...") was rejected because it was received out of order (after batch number ...).
OFSS Cannot access file ... Permission denied SQLCODE=-602
OFSS File system error: ... SQLCODE=-1066
OFSS is supported for SQL Anywhere versions 12, 16 and 17, not version ...
OFSS Modifications not permitted for read-only database SQLCODE=-757
OFSS sampling id is zero for batch file "..."
Older samples purged at ...
Only the Extended edition of Foxhound can be started with a SQL Anywhere server name other than "foxhound5".
Option 1 displayed: Activate Foxhound with a Registration Key
Option 2: Activate Foxhound with a Mini-Restore is not offered because ...
Option 2 displayed: Activate Foxhound with a Mini-Restore
out of range for destination
overlapping sample timestamp
Page not found
Parse error: Invalid or missing keyword near 'CPOOL‘
Patch file OK "..."
Permission denied Cannot access file ... SQLCODE=-602
Permission denied: Cannot CREATE PROCEDURE rroad_...
Permission denied: you do not have permission to execute a statement of this type
Permission denied: you do not have permission to execute the procedure "sa_server_option"
Permission denied: you do not have permission to use the "CREATE PROCEDURE" statement
Pick a valid ODBC DSN, and specify the user id and password on the Foxhound DSN tab or inside the DSN itself
Please fill in both User Id and Password, or leave both empty.
Please install version ... or later. See www.sap.com.
Please report this error ... Unexpected situation
Preparing monitor sample sessions...
Procedure rroad_ ... _properties build number ... is more recent than Foxhound build number ... on ...
Procedure rroad_connection_properties build number ... is different from the Foxhound build number ... on ...
Procedure rroad_connection_properties has been upgraded [from build number ...] to build number ... on ...
Procedure 'rroad_connection_properties' not found
Procedure rroad_database_properties build number ... is different from the Foxhound build number ... on ...
Procedure rroad_database_properties has been upgraded [from build number ...] to build number ... on ...
Procedure rroad_engine_properties build number ... is different from the Foxhound build number ... on ...
Procedure rroad_engine_properties has been upgraded [from build number ...] to build number ... on ...
Program Maintenance - Modify, repair, or remove the program.
PROPERTY ... out of range ...
proxy_rroad_..._properties returned a result set with a different schema than expected
Purge run ... which started at ... has been cancelled because it was running too long.
Request Time-Out (408)
Retry loop failed to find a Top Sample or Most Recent Sample to display.
rroad_OFSS_load failed to delete a file after it was processed
rroad_OFSS_load failed to move a leftover file to the rejected subfolder
rroad_OFSS_load moved a leftover file to the rejected subfolder
rroad_OFSS_load rejected a batch because of an overlapping sample timestamp
rroad_OFSS_load rejected a batch because the "conn" file was missing
rroad_OFSS_load rejected a batch because the input schema version ... is not compatible with the Foxhound build number ...
rroad_OFSS_load rejected batch ... because it was not timestamped later than existing samples
Sample Schedule in effect
Service Temporarily Unavailable - 503
Setup error: DIAG yyyy-mm-dd hh:nn:ss.sss ...
Specified database file already in use
Specified database not found
SQL Anywhere database server ... not supported
SQL Anywhere database version ... not supported
SQL Anywhere version ... not supported.
SQL Anywhere version ... or later is required to run this application.
SQL error: User-defined exception signaled
SQLANY17 environment variable not set properly.
SQLCODE = -1066, SQLSTATE = WO027, ERRORMSG() = File system error: ..., @batch_is_ok = "Y", @batch_number = "0", @sampling_id = "0"
SQLCODE = -1188, SQLSTATE = WL013, ERRORMSG() = LOAD TABLE error: The data to load is not encrypted
SQLCODE = -196, SQLSTATE = "23505", ERRORMSG() = "Index 'ix_ping_inserted' for table 'rroad_ping_log' would not be unique"
SQLCODE = -307, SQLSTATE = 40W06, ERRORMSG() = All threads are blocked
SQLCODE = -308, SQLSTATE = 40W07, ERRORMSG() = Connection was dropped
SQLCODE = -660, SQLSTATE = WO005, ERRORMSG() = Server 'p001': [Microsoft][ODBC SQL Server Driver][SQL Server] Incorrect syntax near the keyword 'TRANSACTION'
SQLCODE = -757 Modifications not permitted for read-only database
SQLCODE = -851, SQLSTATE = 08W63, ERRORMSG() = Decryption error: Missing encryption key
SQLCODE=-602 Cannot access file ... Permission denied
start_OFSS_monitor() procedure has already been called on a different connection.
Statement interrupted by user
Statement interrupted by user - Handler for event 'rroad_scheduled_purge' caused SQLSTATE '57014'
Status: proxy_rroad_connection_properties returned a result set with a different schema than expected
Syntax error: syntax error near ...
SYS.DUMMY' could not be found
Target SQL Anywhere server version ... not supported
TCP/IP link, function bind, error code 10048
The $backup_foxhound5_log.bat file did not find an existing full backup of the database and log files in the folder ...
The $post_setup.bat file could not MOVE the new foxhound5.db file to the FOXHOUND5 folder
The activation upgrade was not successful: The registration key has been used before.
The connection was refused when attempting to contact localhost
The data to load is not encrypted
The data to load is not encrypted SQLCODE -1188
The data upgrade process has begun: to build ... from ...
The data upgrade process has failed: to build ... from ...; diagnostics = "..."
The data upgrade process has succeeded: to build ... from ...
The Foxhound database must run on its own SQL Anywhere engine.
The Foxhound Standard Edition supports 10 sessions
The initial activation was not successful: The registration key did not work.
The page cannot be displayed
The process cannot access the file because it is being used by another process.
The remote table 'pxxx..SYS.DUMMY' could not be found
The specified DSN contains an architecture mismatch between the Driver and Application
The start_OFSS_monitor() procedure has already been called on a different connection. Use that connection, or drop it and use this connection.
The system cannot find the file specified.
The system cannot find the path specified.
The system could not find the environment option that was entered.
The table ... has more than one index on columns ( ... )
The table ... has no primary key or unique constraint, but does have a unique index.
The table ... has no primary key, unique constraint or unique index.
The table or view ... was not found, probably because it has been recently dropped.
There are no user tables to display.
This monitor session has been stopped and the samples have been deleted.
This view has no column definitions in SYSCOLUMN; it may contain a syntax error.
To help protect your security, Internet Explorer has restricted this file from showing active content that could access your computer.
Too many sampling sessions in progress. Stop one and try again.
transaction rolled back: I/O error Fatal error: A disk read from file "...\foxhound5.db" failed with error code: (23)
Unable to execute ... rroad5 ...
Unable to read ... rroad5 ...
Unable to stop database server -- Database server not found.
Unable to stop database server -- Request to start/stop database denied.
Unacceptable SQL Anywhere server edition: The database engine is stopping.
UNC Cannot access file ... Permission denied SQLCODE=-602
UNC File system error: ... SQLCODE=-1066
Unexpected exception from SET TEMPORARY OPTION DEDICATED_TASK = ... ignored: ...
Unexpected operation: "..."
Unexpected situation. Extended Edition already activated.
Unexpected situation. Please report this error.
Unique index collision avoided: ping_id = ... ping_log_inserted_at = ... sampling_id = ...
Use that connection, or drop it and use this connection.
User "DBA" dropped event connection ... ("rroad_scheduled_purge")
User-defined exception signaled
Value 18446744073709551615 out of range for destination
Value '...' out of range for destination
Wrong length data in patch file "..."
you do not have permission to execute a statement of this type
You must be an Administrator to remove this application. - Error 1730.

[ Top ]
Message: 404: Not Found
Message: Not Found - 404
Message: Page not found
Message: The page cannot be displayed

Explanation: One reason for a "page not found" message is that the Foxhound database didn't start properly, and the most common reason for that is some other process is already using HTTP port 80 so Foxhound couldn't start.

Another reason is that Foxhound is using some port other than 80 for HTTP and you forgot to code that port in the URL. For example, if you started Foxhound on port 12345, then you need to use this URL:

http://localhost:12345

See also...
Can't start HTTP listener on address 127.0.0.1:80
How do I tell Foxhound to use an HTTP port other than 80?


[ Top ]
Message: 503: Service Temporarily Unavailable
Message: Service Temporarily Unavailable - 503

Explanation: If this condition persists, try stopping and restarting Foxhound.


[ Top ]
Message: 532 ... Info: ... out of range ...
Message: 532 ... Limit of 100 "Info: out of range" messages per Foxhound connection to one target database has been exceeded
Message: CONNECTION_PROPERTY ... out of range ...
Message: DB_PROPERTY ... out of range ...
Message: PROPERTY ... out of range ...

Explanation: Each time an input SQL Anywhere property value is modified (e.g., set to zero) by the Foxhound Monitor process because it is out of range, an information diagnostic message is recorded to show the original value.

These messages are not expected, so if they are causing you any grief, please contact breck.carter@gmail.com.

Duplicate messages are suppressed:

  • Only one message is recorded for the same property value, type and name, and the same Foxhound connection to the same target database.

  • A limit of 100 distinct messages are recorded for each Foxhound connection to one target database.

  • To see recent messages that are being suppressed, try stopping and restarting the Foxhound Monitor process for that target database.
  • Here's what they look like in Foxhound Options - Diagnostics:

                                                                                                                                                                                                                      
    Exception                                    Foxhound    Foxhound                                                                                                                                                     
    Number                                       Internal    Internal                                                                                                             
    |     Exception              Foxhound        Connection  Location                                                                                                             Target sampling_id             
    |     Timestamp              Build           To Target    |       Message                                                                                                      | Target Name             
    |     |                       |                |          |        |                                                                                                           | |                
    V     V                       V                V          V        V                                                                                                           V V
    ----  ----------------------- ---------------- ---------- ------- -----------------------------------------------------------------------------------------------------------  - --------------
    622 - 2020-05-17 16:13:14.877 Full Build 5456a 1000002936 532b-a1 Limit of 100 "Info: out of range" messages per Foxhound connection to one target database has been exceeded [4-partner2_demo]
    621 - 2020-05-17 16:13:14.769 Full Build 5456a 1000002938 532b-a1 Limit of 100 "Info: out of range" messages per Foxhound connection to one target database has been exceeded [6-secondary_demo]
    620 - 2020-05-17 16:13:14.617 Full Build 5456a 1000002934 532b-a1 Limit of 100 "Info: out of range" messages per Foxhound connection to one target database has been exceeded [2-copy_demo]
                                                                              SQL Anywhere                                        
    Exception                                     Foxhound                    Property Type                                              
    Number                                        Internal    Foxhound        PROPERTY                                               
    |     Exception              Foxhound         Connection  Internal        DB_PROPERTY                             Out Of Range               Minimum Value                 Target sampling_id             
    |     Timestamp              Build            To Target   Location        CONNECTION_PROPERTY  Property Name      Property Value              |          Maximum Value      | Target Name             
    |     |                       |                |          |                |                   |                   |                          |           |                 | |                
    V     V                       V                V          V                V                   V                   V                          V           V                 V V
    ----  ----------------------- ---------------- ---------- ----------       ------------------- ------------------  ------------               --------    ----------------  - --------------
    619 - 2020-05-17 15:48:58.501 Full Build 5456a 1000002934 532b-a2(1) Info: CONNECTION_PROPERTY ApproximateCPUTime "-491.9476224" out of range 0.000000 to 100000000.000000 [2-copy_demo]
    618 - 2020-05-17 14:56:28.877 Full Build 5456a 1000002934 532b-a2(1) Info: CONNECTION_PROPERTY ApproximateCPUTime "-491.9632896" out of range 0.000000 to 100000000.000000 [2-copy_demo]
    617 - 2020-05-17 14:56:28.699 Full Build 5456a 1000002938 532b-a2(1) Info: CONNECTION_PROPERTY ApproximateCPUTime "-1022.1858816" out of range 0.000000 to 100000000.000000 [6-secondary_demo]
    616 - 2020-05-17 14:56:28.559 Full Build 5456a 1000002936 532b-a2(1) Info: CONNECTION_PROPERTY ApproximateCPUTime "-1022.1858816" out of range 0.000000 to 100000000.000000 [4-partner2_demo]
    615 - 2020-05-17 14:56:18.908 Full Build 5456a 1000002934 532b-a2(1) Info: CONNECTION_PROPERTY ApproximateCPUTime "-488.0881664" out of range 0.000000 to 100000000.000000 [2-copy_demo]
    614 - 2020-05-17 14:56:18.761 Full Build 5456a 1000002938 532b-a2(1) Info: CONNECTION_PROPERTY ApproximateCPUTime "-1019.45088" out of range 0.000000 to 100000000.000000 [6-secondary_demo]
    613 - 2020-05-17 14:56:18.576 Full Build 5456a 1000002936 532b-a2(1) Info: CONNECTION_PROPERTY ApproximateCPUTime "-1013.4503424" out of range 0.000000 to 100000000.000000 [4-partner2_demo]
    


[ Top ]
Message: 9 Mini-Restore ... foxhound5.db not found
Message: foxhound5.db not found ... 9 Mini-Restore
Message: Mini-Restore ... foxhound5.db not found

Explanation: The Foxhound 5 shortcut 9 - Mini-Restore contained a bug in the GA build 5.0.5432a: If the old foxhound5.db file doesn't exist, the script stops with this error message:

C:\ProgramData\RisingRoad\Foxhound5>ECHO OFF
Foxhound5 - 9 Mini-Restore
****************************************
CAUTION:
A Mini-Restore will restore an EMPTY
Foxhound database, with ONLY your
options and settings, but NO samples.
Are you sure you want to proceed?
Press any key to continue . . .
******************************************************************
*** ERROR ********************************************************
*** foxhound5.db not found...
*** "C:\ProgramData\RisingRoad\Foxhound5\foxhound5.db"
Press any key to continue . . .

To work around this bug in the Foxhound 5 GA build 5.0.5432a, create an empty foxhound5.db file in the Foxhound5 folder so the shortcut 9 - Mini-Restore will work OK.

C:\ProgramData\RisingRoad\Foxhound5>dir foxhound5.db
 Volume in drive C is OS
 Volume Serial Number is 5AB1-1BE1

 Directory of C:\ProgramData\RisingRoad\Foxhound5

02/17/2020  09:23 AM                 0 foxhound5.db
               1 File(s)              0 bytes
               0 Dir(s)  332,553,506,816 bytes free

...so the Foxhound 5 shortcut 9 - Mini-Restore will work OK:

C:\ProgramData\RisingRoad\Foxhound5>ECHO OFF
Foxhound5 - 9 Mini-Restore
****************************************
CAUTION:
A Mini-Restore will restore an EMPTY
Foxhound database, with ONLY your
options and settings, but NO samples.
Are you sure you want to proceed?
Press any key to continue . . .
Check that mini-backup file(s) exist...
Stop the Foxhound engine if it is running...
SQL Anywhere Stop Server Utility Version 17.0.9.4882
Unable to stop database server -- Database server not found.
Rename the Foxhound database and log...
The system cannot find the file specified.
*************************************************************
*** Your old foxhound5.db file has been renamed
***    to foxhound5.db.RENAMED-AT-2020-02-17-T09-25-31
*************************************************************
Copy (restore) the ORIGINAL_COPY file...
        1 file(s) copied.
*************************************************************
*** Your new foxhound5.db file has been copied
***    from the empty ORIGINAL_COPY file.
*************************************************************
*** When Foxhound starts, your next step is to choose
***    "Option 2: Activate Foxhound with a Mini-Restore"
*************************************************************
Press any key to continue . . .

This bug has been fixed in a subsequent build.


[ Top ]
Message: A subdirectory or file backup already exists.

Explanation: This message is safe to ignore if it is produced by the All Programs - Fnd - Tools - Backup Foxhound Database process:


[ Top ]
Message: Access is denied.
Message: ERROR The $post_setup.bat file could not MOVE the new foxhound5.db file to the FOXHOUND5 folder
Message: File access denied.
Message: The $post_setup.bat file could not MOVE the new foxhound5.db file to the FOXHOUND5 folder

Explanation: You may receive an "access is denied" error during the post-setup stage of a Foxhound installation.

Here's what it might look like at first:

C:\Windows\SysWOW64>ECHO OFF
Post-Setup Process for Foxhound Version 5.0
...
*** Checking for an old Foxhound5 database...
*** Moving the new Foxhound database file...
******************************************************************
*** ERROR ********************************************************
*** The $post_setup.bat file could not MOVE the new
*** foxhound5.db file to the FOXHOUND5 folder.
*** See...
***  C:\ProgramData\RisingRoad\Foxhound5\\setup\post_setup_trace.txt
*** Contact Breck.Carter@gmail.com
******************************************************************
Press any key to continue . . .

If you look inside C:\ProgramData\RisingRoad\Foxhound5\setup\post_setup_trace.txt you might see this:

Mon 08/22/2016  6:28:11.27 Foxhound 5.0.xxxx *** Moving the new Foxhound5 database file... 
Access is denied.
        0 file(s) moved.


Solution 1: Try using "Run as administrator" to reinstall Foxhound.

  1. Run the Foxhound "unsetup" process...
    start - All Programs - Foxhound5 - Tools - Unsetup Foxhound 
    

  2. Delete the Foxhound folder...
    C:\ProgramData\RisingRoad\Foxhound5
    

  3. Use right mouse - Run as administrator to run the Foxhound setup...
    Foxhound-Version-4-0-xxxx-setup.exe
    


Solution 2: Try switching to the hidden "Administrator" account to reinstall Foxhound.

  1. Run the Foxhound "unsetup" process...
    start - All Programs - Foxhound5 - Tools - Unsetup Foxhound 
    

  2. Delete the Foxhound folder...
    C:\ProgramData\RisingRoad\Foxhound5
    

  3. Open a "command prompt" window in "Administrator" mode...
    start - All Programs - Accessories - right mouse Command prompt - Run as Administrator 
    

  4. Make the magic hidden Administrator account visible in Windows 10 by typing this command and pressing Enter...
    net user administrator /active:yes
    

  5. Log off your normal account, and login as Administrator.

  6. Run the Foxhound installation again.
  7. You probably should set a password for the Administrator account, or hide it again...
    net user administrator /active:no
    

  8. If you started the Foxhound database while logged in as Administrator, shut it down.
  9. While still logged on Administrator, grant "Full Control" on the C:\ProgramData\RisingRoad folder to all "Users"...
    Windows Explorer 
      - click right mouse Properties on C:\ProgramData\RisingRoad
      - click Security
      - click Edit...
      - select "Users (..."
      - check Full Control - Allow
      - click Apply
      - click OK
    


Solution 3: The "Access is denied" message may appear during a Foxhound installation or upgrade on Windows 10:

C:\Windows\SysWOW64>ECHO OFF
Post-Setup Process for Foxhound Version 5.0
*** Checking for a post-setup path parameter...
Access is denied.
Access is denied.
*** A post-setup path parameter was provided...
C:\ProgramData\RisingRoad\Foxhound5\
Access is denied.
Access is denied.
Access is denied.
Access is denied.
Access is denied.
Access is denied.
Access is denied.
Access is denied.
Access is denied.
*******************************************************************
***                   Foxhound 5.0.xxxx
***
*** Here's where Foxhound is being installed:
*** C:\ProgramData\RisingRoad\Foxhound5\
***
Access is denied.
*** Starting the Foxhound 5.0.xxxx post-setup process...
Access is denied.
Access is denied.
Access is denied.
*** Creating foxhound5.db.5.0.xxxx.ORIGINAL_COPY...
Access is denied.

C:\Windows\SysWOW64

Try installing Foxhound 5 again:

  1. Run the Foxhound "unsetup" process...
    All Apps - Foxhound5 - Unsetup Foxhound
    

  2. Use right mouse - Run as Administrator to run the Foxhound 5 setup exe.


Solution 4: The "Access is denied" message may also mean the Foxhound engine is already running as a service and it cannot be stopped by the post setup process. As a result, the Foxhound upgrade will not work properly:


Solution 5: If the shortcut Foxhound5 - Tools - Stop Foxhound Engine doesn't finish

   C:\ProgramData\RisingRoad\Foxhound5>ECHO OFF
   Stop Foxhound Engine
   SQL Anywhere Stop Server Utility Version 16.0.0.1324

and both Task Manager and the taskkill command display "Access is denied." when you try to stop the Foxhound dbsrv17.exe process

   C:\Users\Breck>taskkill /pid 8140
   ERROR: The process with PID 8140 could not be terminated.
   Reason: Access is denied.

then check to see if there is a dbclient.exe process still running that was previously being used by Foxhound to connect to a SQL Anywhere 5.5 database. If so, shut down that dbclient.exe process and the Foxhound engine should stop.

See also...
How do I install a new version of Foxhound?


[ Top ]
Message: Activation exception: SQLCODE = ... SQLSTATE = ... ERRORMSG() = ...
Message:

Explanation:

This message was produced by the Foxhound Activation page when an exception occurred.


[ Top ]
Message: ALERT ...

Explanation: An ALERT email is sent when one or more target database conditions match user-defined criteria.

The Monitor Options page lets you turn alerts on and off and specify alert criteria for a particular target database. Individual criteria may include a threshold amount and/or a duration or waiting period.

The "Recent alert history" section of an ALERT email is a list of recent ALERT, ALL CLEAR and CANCELLED conditions for this target database.

The "Recent sample history" section of an ALERT email shows what the Foxhound History page looks like when the alert was issued, including blocked and current connections.

The sort order for the current connections section of an ALERT email depends on the alert condition, as follows:

Alert Email Connection Sort Order Connections Sorted On
1 - Database unresponsive descending CPU
2 - Long heartbeat descending CPU
3 - Long sample time descending CPU
4 - CPU usage descending CPU
5 - Database disk space descending Disk Writes
6 - Temp disk space descending Disk Writes
7 - Log disk space descending Disk Writes
8 - Other disk space descending Disk Writes
9 - Arbiter unreachable descending CPU
10 - Partner unreachable descending CPU
11 - HA failover descending CPU
12 - HA mode change descending CPU
13 - File fragmentation descending Disk Writes
14 - Unscheduled Requests descending CPU
15 - Incomplete I/Os descending Disk Writes
16 - I/O operations descending Disk Writes
17 - Checkpoint urgency descending Disk Writes
18 - Recovery urgency descending Disk Writes
19 - Cache size descending CPU
20 - Cache satisfaction ascending Cache Satisfaction
21 - Temp file usage descending Temp Space
22 - Conn temp file usage descending Temp Space
23 - Blocked connections descending Conns Blocked
24 - Conn blocking others descending Conns Blocked
25 - Locks descending Locks Held
26 - Connections descending CPU
27 - Connection CPU descending CPU
28 - Long transaction descending Transaction Running Time
29 - Cache panics descending Cache Satisfaction

See also...
Help - Foxhound Options - Global Email Settings
Help - Monitor Options - Alert Email Setup
ALL CLEAR ...
CANCELLED ...


[ Top ]
Message: ALL CLEAR ...

Explanation: An ALL CLEAR email is sent when an alert criteria is no longer met. If a waiting period is specified on the Monitor Options page, Foxhound waits for approximately half that time before issuing the all clear.

The "Recent alert history" section of an ALL CLEAR email is a list of recent ALERT, ALL CLEAR and CANCELLED conditions for this target database.

See also...
Help - Monitor Options
ALERT ...
CANCELLED ...


[ Top ]
Message: An attempt to start sample loop event ... for sampling id ... failed because event ... was already running for that sampling id.

Explanation:

This is an unexpected error, possibly caused by an internal error in Foxhound.

Please report this error; see How do I report unexpected errors and exceptions?

If possible, include the diagnostic message and associated dump; here is an example:

1. Use the Foxhound Options - 8. Diagnostics - Display Diagnostics button to find the exception id, 477 in this case:

477 - 2012-07-26 06:56:37.407 Full Build 4173a 1000001557 203a3d3(203eh1) An attempt to start sample loop event 1000001557 
   for sampling id 4 failed because event 1000000020 was already running for that sampling id. [4-Foxhound_on_old_Dell_XP]

2. Run adhoc queries to see the diagnostic message and the associated dump (see How do I run adhoc queries on the Foxhound database?):

SELECT * FROM exception_diagnostic WHERE exception_id = 477;
SELECT * FROM exception_dump       WHERE exception_id = 477;

exception_id,exception_diagnostic
477,2012-07-26 06:56:37.407 Full Build 4173a 1000001557 203a3d3(203eh1) An attempt to start sample loop event 1000001557 
   for sampling id 4 failed because event 1000000020 was already running for that sampling id. [4-Foxhound_on_old_Dell_XP]
SELECT * FROM exception_dump WHERE exception_id = 477;

exception_id,dump_id,dump_inserted_at,dump
477,1,'2012-07-26 06:56:37.409','rroad_sampling_options','203a3d3','(203eh1)',4,'1','Foxhound_on_old_Dell_XP',
   'Foxhound_on_old_Dell_XP','',,,,'Y','N',2012-07-23 12:09:23.973,'OK',1000000020,'','Y','',0,4,2012-07-26 06:56:36.070,
   2012-07-26 06:56:36.070,2012-07-26 06:56:26.026,2012-07-26 06:56:26.030,'16.0.0.1324','16.0.0.1324','p001',8192,'N',
   'N','N','DBA','',2147483647,'Conn #','ASC',0,'',''\x0d\x0a

3. Run adhoc queries to copy the diagnostic message and associate dump to a single text file:

UNLOAD SELECT * FROM exception_diagnostic WHERE exception_id = 477 TO 'c:/temp/foxhound_exception.txt';
UNLOAD SELECT * FROM exception_dump       WHERE exception_id = 477 TO 'c:/temp/foxhound_exception.txt' APPEND ON;

477,'2012-07-26 06:56:37.407 Full Build 4173a 1000001557 203a3d3(203eh1) An attempt to start sample loop event 1000001557 
   for sampling id 4 failed because event 1000000020 was already running for that sampling id. [4-Foxhound_on_old_Dell_XP]'
477,1,2012-07-26 06:56:37.409,'''rroad_sampling_options'',''203a3d3'',''(203eh1)'',4,''1'',''Foxhound_on_old_Dell_XP'',
   ''Foxhound_on_old_Dell_XP'','''',,,,''Y'',''N'',2012-07-23 12:09:23.973,''OK'',1000000020,'''',''Y'','''',0,4,
   2012-07-26 06:56:36.070,2012-07-26 06:56:36.070,2012-07-26 06:56:26.026,2012-07-26 06:56:26.030,''16.0.0.1324'',
   ''16.0.0.1324'',''p001'',8192,''N'',''N'',''N'',''DBA'','''',2147483647,''Conn #'',''ASC'',0,'''',''''\x0d\x0a'

See also...
How do I report unexpected errors and exceptions?
How do I run adhoc queries on the Foxhound database?
How do I see the schema for adhoc reporting?


[ Top ]
Message: Another version of this product is already installed.
Message: Modify, repair, or remove the program.
Message: Program Maintenance - Modify, repair, or remove the program.

Explanation: You have to run the Foxhound "unsetup" process before reinstalling Foxhound 5, or before installing a new build.

If you forget, you may see one of these dialog boxes when you run the Foxhound setup; this is a limitation of the way the InstallShield setup for Foxhound 5 is constructed:

Another version of this product is already installed.

Modify, repair, or remove the program.

Do not click on Modify or Repair; they won't damage anything, but nothing will happen when you click on the Post-Setup button at the end of Modify or Repair process.

There are three ways to run the Foxhound 5 unsetup process:

  • Click on start - All Programs - Foxhound5 - 10 Unsetup Foxhound, or
  • use the Control Panel - Add or Remove Programs dialog to remove Foxhound Version 5, or

  • run this command: MsiExec.exe /X{B0FE1886-2DBE-4269-8EBD-2A3EF45C4EF5}

The unsetup process doesn't actually delete the existing database file foxhound5.db; that file is overwritten after the data is upgraded (copied) during the post-setup process when you reinstall Foxhound.

Here's what you see when you click on start - All Programs - Foxhound5 - Tools - Unsetup Foxhound:

Unsetup Foxhound Version 5

See also...
How do I install Foxhound?
How do I install a new version of Foxhound?
How do I reinstall Foxhound?
Why is it called "unsetup" instead of "uninstall"?
How do I remove Foxhound from my system?


[ Top ]
Message: CANCELLED ...

Explanation:

A CANCELLED message is produced as soon as some alert criteria is changed or disabled using the Monitor Options page. At that point the alert testing process "starts over"; it doesn't matter what the change is. For example, even if the new alert condition is already met when the change is made, if there is a waiting period it is honored before a new alert is issued.

Also, if sampling is stopped while an Alert is active, the Alert is cancelled.

The "Recent alert history" section of a CANCELLED email is a list of recent ALERT, ALL CLEAR and CANCELLED conditions for this target database.

See also...
Help - Monitor Options
ALERT ...
ALL CLEAR ...


[ Top ]
Message: Cannot access file ... Permission denied SQLCODE=-602
Message: -602 Cannot access file ... Permission denied SQLCODE=-602
Message: OFSS Cannot access file ... Permission denied SQLCODE=-602
Message: Permission denied Cannot access file ... SQLCODE=-602
Message: SQLCODE=-602 Cannot access file ... Permission denied
Message: UNC Cannot access file ... Permission denied SQLCODE=-602

Explanation:

If a CALL start_OFSS_monitor() statement fails with "Cannot access file ... Permission denied SQLCODE=-602", and

  • you are using UNC file specification like SET unload_path = '\\\\Xps\\c\\DATA\\OFSSremote\\'

  • with an OFSS subject database being run as a Windows service,

  • try using the dbsvc -a and -p options to create the service to run under the account name and password for a Microsoft Windows account you have created

  • instead of using dbsvc -as to run under the Windows LocalSystem account.

For example, if you created the OFSS subject database service with dbsvc -as, you might see the following exception that is raised by an UNLOAD TABLE statement inside the OFSS script:

-- Subject database ISQL session

PARAMETERS OWNER;
UPDATE "{OWNER}".OFSS_settings SET unload_path = '\\\\Xps\\c\\DATA\\OFSSremote\\';
UPDATE "{OWNER}".OFSS_settings SET max_batch_duration = '7m'; 
UPDATE "{OWNER}".OFSS_settings SET encryption_key     = 'KeHX8?k1Rqz/5FvOu{nhx1#mQxy0@95e'; -- the values must agree
UPDATE "{OWNER}".OFSS_settings SET max_batch_size     = '1M'; 
UPDATE "{OWNER}".OFSS_settings SET server_messages_are_to_be_captured = 'Y';
CALL "{OWNER}".start_OFSS_monitor();

Could not execute statement.
Cannot access file
'\\Xps\c\DATA\OFSSremote\OFSS-ddd-batch------2-uuid-3728852...' --
Permission denied
SQLCODE=-602, ODBC 3 State="HY000"
C:\ProgramData\RisingRoad\Foxhound5\scripts\OFSS_1_setup.sql:7
CALL "dba".start_OFSS_monitor()

-- OFSS diagnostic table on the subject database

SELECT * FROM OFSS_exception;

exception_id,inserted_at,diagnostic_text
1,2019-07-29 16:35:00.924,OFSS-b2e(OFSSehb2) SQLCODE = -602, SQLSTATE = WL002, 
   ERRORMSG() = Cannot access file '\\\\Xps\\c\\DATA\\OFSSremote\\OFSS-arbiter-batch------2-uuid-dfa...' -- Permission denied

Here's a template for using the dbsvc -a and -p options to set up a High Availability partner database as a service:

"%SQLANY17%\Bin64\dbsvc.exe"^
  -a youraccount^
  -o "xxx\dbsvc_partner1_log.txt"^
  -p yourpassword^
  -s Automatic^
  -sd "SQL Anywhere 17 Partner1 Server"^
  -sn nnnnnnnn^
  -t Network^
  -y^
  -w nnnnnnnn^
  "%SQLANY17%\bin64\dbsrv17.exe"^
  -dt "ttt"^
  -n nnnnnnnn^
  -o "yyy\dbsrv17_partner1_log.txt"^
  -oe "yyy\dbsrv17_partner1_startup_log.txt"^
  -su sqlsql^
  -x tcpip(port=99999;dobroadcast=no)^
  -zp^
  -zl^
  -zt^
  "zzz\ddd.db"^
  -xp on


[ Top ]
Message: Cannot access ... foxhound5.db ... another process may be using the file

Explanation: If this message appears during the "post setup" step during a Foxhound upgrade, it probably means the Foxhound engine is already running as a service and it cannot be stopped by the post setup process. As a result, the Foxhound upgrade will not work properly.

Try stopping the service and rerunning the upgrade, including the initial "unsetup" step: How do I install a new version of Foxhound?

See also...
How do I install a new version of Foxhound?


[ Top ]
Message: Cannot convert '...' to a timestamp

Explanation:

This is an unexpected error, possibly caused by a problem with the performance statistics received from the target database server.

Please report this error; see How do I report unexpected errors and exceptions?

See also...
How do I see Foxhound diagnostics, errors and exceptions?


[ Top ]
Message: Cannot open transaction log file
Message: Can't use log file

Explanation: Delete the foxhound5.log file if it still exists, then start the Foxhound database one time with the dbsrv17 -f option as follows:

  • Open this command file in a text editor:
      C:\ProgramData\RisingRoad\Foxhound5\$start_foxhound5_engine.bat
    

  • Insert this line
      -f^
    

    as shown below:

    "!SQLANY17!\!BIN!\dbspawn.exe"^
      -f "!SQLANY17!\!BIN!\dbsrv17.exe"^
      -c 25p^
      -ch 50p^
      -cr-^
      -f^
      -gk all^
      -gl all^
      -gn 220^
      -gna 0^
      -m^
      -n foxhound5^
      -o foxhound5_debug.txt^
      -oe foxhound5_debug_startup.txt^
      -on 1M^
      -qn^
      -sb 0^
      -ufd restart^
      -x tcpip^
      -xd^
      -xs http(port=80;maxsize=0;to=600;kto=600)^
      foxhound5.db^
      -n f
    

  • Run Start - Foxhound5 - 14 Start Foxhound Engine

  • It should start the Foxhound database, create a new Foxhound transaction log file, and then shut down.

  • Re-edit the $start_foxhound5_engine.bat file to remove the -f^ line, then start Foxhound normally.


[ Top ]
Message: Can't open Message window log file: foxhound5_debug.txt

Explanation:

C:\ProgramData\RisingRoad\Foxhound5>ECHO OFF
Start Foxhound Engine
SQL Anywhere Start Server In Background Utility Version 16.0.0.2127
DBSPAWN ERROR:  -81
Invalid database server command line
******************************************************************
*** ERROR ********************************************************
*** dbspawn/dbsrv set ERRORLEVEL = 1
05/15 11:00:33. Can't open Message window log file: foxhound5_debug.txt
Press any key to continue . . .

If you're trying to run Foxhound 5 on Windows 10, you may have to use "Run as Administrator" to launch the Foxhound batch files.

Here's how you can set "Run as Administrator" for the Foxhound shortcuts in Windows 10:
All apps - Foxhound5 

Right mouse on Start Foxhound Engine

   Click More - Open File Location

   See this folder appear: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Foxhound5\Tools

Right mouse - Properties on Start Foxhound Engine

   Select the Shortcut tab. 

Click Advanced. 

   Check Run as Administrator.

   Click Apply.

This message may also mean the Foxhound database was already running when you tried to start it again; for example, you used the Foxhound5 - Tools - Start Foxhound Engine shortcut when the Foxhound database was already running.

If you want to restart the Foxhound database, try using the Foxhound5 - Tools - Stop Foxhound Engine shortcut first.

With some of the shortcuts, like Foxhound5 - 6 Start Foxhound via Chrome, you can just ignore this message and press a key to contine opening Foxhound in the Chrome browser.

If you are using one of the "debug" scripts to stop and restart the Foxhound engine, try running it again. The previous dbsrv17.exe process may not have had enough time to release the foxhound5_debug.txt file before a new dbsrv17.exe process tried to open that file:

Help - Introduction - Starting Foxhound - Method 2: Debug Startup

If the problem persists, Foxhound may already running as a service and the "debug" shortcut may not able to stop the Foxhound database before starting it again. Look for an earlier message "Unable to stop database server -- Request to start/stop database denied."

See also...
Invalid database server command line
Unable to stop database server -- Request to start/stop database denied.


[ Top ]
Message: Can't start HTTP listener on address 127.0.0.1:80
Message: Can't start HTTP listener on address (::):80
Message: Can't start HTTP listener on address 0.0.0.0:80
Message: Could not bind to address 0.0.0.0:80
Message: TCP/IP link, function bind, error code 10048

Explanation: Some other process (Apache, IIS, Skype, another SQL Anywhere engine, etc) is already using TCP/IP port 80.

Either tell that process to stop using port 80 or tell Foxhound to use a different port.

For example, to stop Skype from using port 80:

  • Open the Skype window,

  • click on Tools - Options... - Advanced - Connection

  • uncheck the "Use port 80 and 443 for additional incoming connections" option,

  • click on Save button and

  • restart Skype to make the change effective.

See also...
What HTTP port should I use for Foxhound?
How do I tell Foxhound to use an HTTP port other than 80?
IANA port number assignments
Database server shutdown due to startup error


[ Top ]
Message: Choose a connection string.

Explanation: This is an unexpected message.

Please contact Breck.Carter@gmail.com.


[ Top ]
Message: Choose an ODBC DSN.

Explanation: This is an unexpected message.

Please contact Breck.Carter@gmail.com.


[ Top ]
Message: Client address backtrace: ::1
Message: 1: Client address backtrace: ::1

Explanation:

The Client address backtrace is the result of a network trace from the computer running the target database back to the computer running Foxhound. The value ::1 is the IPv6 equivalent of the IPv4 address 127.0.0.1 which is "localhost", which in turn means Foxhound is running on the same computer as the target database.

The IPv6 value ::1 may show up in the Client address backtrace value if your computer has IPv6 installed even if you are using IPv4 addresses.


[ Top ]
Message: conn file was missing
Message: rroad_OFSS_load rejected a batch because the "conn" file was missing

Explanation: An OFSS batch consists of three files (head, data, conn). If any of the three files are missing, Foxhound will (try to) move the other files to the rejected subfolder.

In this case, the head file was present but the conn file was missing.

See also...
How do I find my OFSS samples?


[ Top ]
Message: Connection "..." by user id "..." rejected during post-setup data upgrade process.

Explanation:

Do not attempt to connect to the Foxhound database while the post-setup data upgrade process is running. Such connection attempts will be rejected.


[ Top ]
Message: Connection error: No IP address found for ...
Message: No IP address found for ...

Explanation:

Try changing the firewall settings on the target computer to allow network access from the computer where Foxhound is running. For example, in Norton Internet Security the Settings - Firewall - Network Trust - Configure [+] - Trust Level may be set to "Private" instead of "Full Trust".

If Foxhound is suddenly unable to monitor a target database, and this is the error message, try rebooting.

Dilbert.com 2008-12-24


[ Top ]
Message: Connection was terminated
Message: -308 Connection was terminated
Message: Connection was dropped
Message: Error! The connection to the database was closed by the server. Connection was terminated SQLCODE=-308
Message: SQLCODE = -308, SQLSTATE = 40W07, ERRORMSG() = Connection was dropped

Explanation:

If this exception occurred in a Foxhound target database, check Foxhound for an Autodropped message.

If this exception occurred during a CALL start_OFSS_monitor() on a High Availability primary database, a failover may have occurred. Try rerunning the CALL start_OFSS_monitor() to connect to the new primary.


[ Top ]
Message: CREATE PROCEDURE rroad_..._properties failed ... Modifications not permitted for read-only database
Message: Modifications not permitted for read-only database ... CREATE PROCEDURE rroad_..._properties failed

Explanation: This can occur when Foxhound connects to a High Availability secondary (mirror) database and/or a read-only scale out (copy) database, but not the updatable primary or root node database.

In this case Foxhound cannot create the three properties procedures (rroad_engine_properties, rroad_database_properties and rroad_connection_properties) in the target database because it is read-only.

25 2016-06-19 15:37:21.784 Full Build 4679a 1000010086 701.a3(701eh2) CREATE PROCEDURE rroad_engine_properties failed. 
   SQLSTATE = WO005, ERRORMSG() = Server 'p001': [SAP][ODBC Driver][SQL Anywhere] 
   Modifications not permitted for read-only database [120-HA_Demo_16_Copy4]

26 2016-06-19 15:37:21.795 Full Build 4679a 1000010086 702.a3(702eh2) CREATE PROCEDURE rroad_database_properties failed. 
   SQLSTATE = WO005, ERRORMSG() = Server 'p001': [SAP][ODBC Driver][SQL Anywhere] 
   Modifications not permitted for read-only database [120-HA_Demo_16_Copy4]

27 2016-06-19 15:37:21.815 Full Build 4679a 1000010086 700.a3(700eh2) CREATE PROCEDURE rroad_connection_properties failed. 
   SQLSTATE = WO005, ERRORMSG() = Server 'p001': [SAP][ODBC Driver][SQL Anywhere] 
   Modifications not permitted for read-only database [120-HA_Demo_16_Copy4]

28 2016-06-19 15:38:07.056 Full Build 4679a 1000010161 701.a3(701eh2) CREATE PROCEDURE rroad_engine_properties failed. 
   SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere] 
   Modifications not permitted for read-only database [122-HA_Demo_16_Secondary]

29 2016-06-19 15:38:07.066 Full Build 4679a 1000010161 702.a3(702eh2) CREATE PROCEDURE rroad_database_properties failed. 
   SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere] 
   Modifications not permitted for read-only database [122-HA_Demo_16_Secondary]

30 2016-06-19 15:38:07.079 Full Build 4679a 1000010161 700.a3(700eh2) CREATE PROCEDURE rroad_connection_properties failed. 
   SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere 
   ]Modifications not permitted for read-only database [122-HA_Demo_16_Secondary]

One solution is to

  • start another Foxhound sampling session connected to the primary or root node database, then

  • wait a moment for the three properties procedures to be created on the primary or root node database and then sent to the secondary (mirror) database and/or read-only scale out (copy) database, then

  • stop and start sampling on the secondary (mirror) database and/or read-only scale out (copy) database, to force Foxhound to begin using the three properties procedures.

See also...
How do I see Foxhound diagnostics, errors and exceptions?


[ Top ]
Message: Data cannot be copied from an old Foxhound database that has never been activated.
Message: DIAG ... Data cannot be copied from an old Foxhound database that has never been activated.
Message: ERROR ... DIAG ... Data cannot be copied from an old Foxhound database that has never been activated.

Explanation: A second attempt to install Foxhound will not copy any data from the Foxhound database installed during the first attempt, if that database has never been activated.

*** C:\ProgramData\RisingRoad\Foxhound5\
***
*** You may launch Foxhound with this shortcut:
***   Start - Foxhound5 - 1 Start Foxhound
***
*** The "Foxhound Activation" page MAY appear in your browser.
*** If it appears, it will ask you for a registration key.
*** Need a registration key? See www.risingroad.com/foxhound
*** Questions? Problems? Ask breck.carter@gmail.com
*******************************************************************
******************************************************************
*** ERROR ********************************************************
DIAG 2016-08-24 13:40:11.633 Data cannot be copied from an old Foxhound database
 that has never been activated.
******************************************************************
*** For more information, see...
***  C:\ProgramData\RisingRoad\Foxhound5\\setup\post_setup_trace.txt
***  C:\ProgramData\RisingRoad\Foxhound5\\setup\databasestart_diagnostic.txt
***  C:\ProgramData\RisingRoad\Foxhound5\\setup\old_foxhound1_debug.txt
***  C:\ProgramData\RisingRoad\Foxhound5\\setup\old_foxhound1_debug_startup.txt
*** Contact Breck.Carter@gmail.com
Press any key to continue . . .

Try completely removing Foxhound from your computer then reinstalling it.

See also...
How do I remove Foxhound from my system?
How do I reinstall Foxhound?


[ Top ]
Message: Data cannot be upgraded from ... to ...

Explanation: When installing a new version of Foxhound, the data from an existing Foxhound database earlier than build 1.3586 cannot be upgraded.

The new Foxhound database will be installed but it will not contain any of the monitor samples or option settings from the old database.


[ Top ]
Message: Database server connection limit exceeded

Explanation:

Foxhound can't connect to the target database because the target server already has the maximum number of connections.


[ Top ]
Message: Database server shutdown due to startup error

Explanation: Some other HTTP web server (Apache, IIS, another SQL Anywhere engine, etc) may already be using TCP/IP port 80.

If so, either stop that other process, or tell Foxhound to use a different port.

See also...
What HTTP port should I use for Foxhound?
How do I tell Foxhound to use an HTTP port other than 80?
IANA port number assignments
Can't start HTTP listener on address 127.0.0.1:80


[ Top ]
Message: DBSPAWN ERROR: -81
Message: -81: DBSPAWN ERROR: -81

Explanation: This is a generic error message produced by the dbspawn.exe utility when the Foxhound database fails to start properly because dbsrv17.exe has detected some problem. To determine what the real problem is, try using one of the "debug" scripts to start the Foxhound engine:

Help - Introduction - Starting Foxhound - Method 2: Debug Startup
Look for another error message, such as:


[ Top ]
Message: dbspawn/dbsrv17 set ERRORLEVEL = 0
Message: 0: dbspawn/dbsrv17 set ERRORLEVEL = 0
Message: ERRORLEVEL = 0 from dbspawn/dbsrv17

Explanation: (Note: This is different from the more common message "dbspawn/dbsrv17 set ERRORLEVEL = 1".)

If the "dbspawn/dbsrv17 set ERRORLEVEL = 0" message appears by itself, without any other error messages, it is probably safe to ignore; it is probably a false error which is sometimes displayed by the "debug" scripts used to start the Foxhound engine:

Help - Introduction - Starting Foxhound - Method 2: Debug Startup

See also...
dbspawn/dbsrv17 set ERRORLEVEL = 1


[ Top ]
Message: dbspawn/dbsrv17 set ERRORLEVEL = 1
Message: 1: dbspawn/dbsrv17 set ERRORLEVEL = 1
Message: ERRORLEVEL = 1 from dbspawn/dbsrv17

Explanation: This is a generic error message produced by the dbspawn.exe utility when the Foxhound database fails to start properly because dbsrv17.exe has detected some problem. To determine what the real problem is, try using one of the "debug" scripts to start the Foxhound engine:

Help - Introduction - Starting Foxhound - Method 2: Debug Startup

Look for another error message, such as:

See also...
Can't open Message window log file: foxhound5_debug.txt
dbspawn/dbsrv17 set ERRORLEVEL = 1
Invalid database server command line
Unable to stop database server -- Request to start/stop database denied.


[ Top ]
Message: dbspawn/dbsrv17 set ERRORLEVEL = 255
Message: 255: dbspawn/dbsrv17 set ERRORLEVEL = 255
Message: ERRORLEVEL = 255 from dbspawn/dbsrv17

Explanation: This is a generic error message produced by the dbspawn.exe utility when the Foxhound database fails to start properly because dbsrv17.exe has detected some problem. To determine what the real problem is, try using one of the "debug" scripts to start the Foxhound engine:

Help - Introduction - Starting Foxhound - Method 2: Debug Startup

See also...
Can't open Message window log file: foxhound5_debug.txt


[ Top ]
Message: dbspawn/dbsrv17 set ERRORLEVEL = 3
Message: 3: dbspawn/dbsrv17 set ERRORLEVEL = 3
Message: ERRORLEVEL = 3 from dbspawn/dbsrv17

Explanation: This is a "file not found" error that may indicate SQL Anywhere 16 should be installed or reinstalled.

See also...
What are the Foxhound system requirements?


[ Top ]
Message: Decryption error: Missing encryption key
Message: LOAD TABLE error: The data to load is not encrypted
Message: Missing encryption key
Message: SQLCODE = -1188, SQLSTATE = WL013, ERRORMSG() = LOAD TABLE error: The data to load is not encrypted
Message: SQLCODE = -851, SQLSTATE = 08W63, ERRORMSG() = Decryption error: Missing encryption key
Message: The data to load is not encrypted

Explanation: The encryption key that was specified before the CALL "{OWNER}".start_OFSS_monitor() on the OFSS subject database must also be specified for the CALL load_OFSS_samples() on Foxhound.

Here's an example of the error:

-- On subject database 1:

PARAMETERS OWNER;
UPDATE "{OWNER}".OFSS_settings SET unload_path = 'C:\\DATA\\OFSSddd12\\';               -- folder 1
UPDATE "{OWNER}".OFSS_settings SET max_batch_duration = '2m';                           -- 2 minutes between batches
UPDATE "{OWNER}".OFSS_settings SET encryption_key = 'KeHX8?k1Rqz/5FvOu{nhx1#mQxy0@95e'; -- encryption key 1
CALL "{OWNER}".start_OFSS_monitor();

-- On Foxhound Adhoc Query connection 1: 

CALL load_OFSS_samples ( @load_path = 'C:\\DATA\\OFSSddd12\\' );  

Could not execute statement.
Decryption error: Missing encryption key
SQLCODE=-851, ODBC 3 State="08001"
Line 1, column 1
CALL load_OFSS_samples ( @load_path = 'C:\\DATA\\OFSSddd12\\' )

Here's the corrected code:

-- On subject database 1:

PARAMETERS OWNER;
UPDATE "{OWNER}".OFSS_settings SET unload_path = 'C:\\DATA\\OFSSddd12\\';               -- folder 1
UPDATE "{OWNER}".OFSS_settings SET max_batch_duration = '2m';                           -- 2 minutes between batches
UPDATE "{OWNER}".OFSS_settings SET encryption_key = 'KeHX8?k1Rqz/5FvOu{nhx1#mQxy0@95e'; -- encryption key 1
CALL "{OWNER}".start_OFSS_monitor();


-- On Foxhound Adhoc Query connection 1: 

CALL load_OFSS_samples ( 
   @load_path = 'C:\\DATA\\OFSSddd12\\',                   -- folder 1 
   @encryption_key = 'KeHX8?k1Rqz/5FvOu{nhx1#mQxy0@95e' ); -- encryption key 1

[ Top ]
Message: Email not sent because Alert Emails were disabled.
Message: Email not sent because no Alert email address was provided.
Message: Email not sent because of the Alert Email Schedule.
Message: Email not sent because sampling is offline.

Explanation:

When an Alert, All Clear or Alert Cancelled message is not accompanied by an email, the reason is included:

Email not sent because Alert Emails were disabled.

One or the other or both of these checkboxes are unchecked:
Foxhound Options - 1. Global Overrides - Enable Emails.

Monitor Options - 7. Email Setup - Send Alert emails:

Email not sent because sampling is offline.

Alert emails are not supported by the Offline Foxhound Sampling Service (OFSS).

Email not sent because no Alert email address was provided.

Emails won't be sent if the following field is empty:
Monitor Options - 7. Email Setup - Email address(es) for Alerts:

Email not sent because of the Alert Email Schedule.

The Monitor Options - 8. Alert Email Schedule was enabled, and "Y" was not specified for the 15-minute period during which the Alert, All Clear or Alert Cancelled message was displayed.


[ Top ]
Message: Error - File output check failed with return code 1
Message: 1: Error - File output check failed with return code 1
Message: File output check failed with return code 1

Explanation:

The Export Diagnostics button on the Foxhound Options page will display this message when the the file specification in the "Export diagnostics to file:" field is invalid.


[ Top ]
Message: Error 1730. You must be an Administrator to remove this application.
Message: 1730: You must be an Administrator to remove this application. - Error 1730.
Message: You must be an Administrator to remove this application. - Error 1730.

Explanation:

Click on "Yes" rather than pressing Enter when the Windows User Account Control dialog box asks for permission, or use right mouse - Run as Administrator on the Unsetup Foxhound shortcut...

User Account Control

Do you want to allow the following program from an
unknown publisher to make changes to this computer?

...and don't wait too long.

If you see this ...

Error 1730. You must be an Administrator to remove this
application. To remove this application, you can logon as
an Administrator, or contact your technical support group for
assistance.

Error 1730. You must be an Administrator to remove this application.

... click on OK, then try running Unsetup Foxhound again.


[ Top ]
Message: Error in TCPIP port options

Explanation:

If the message "Error in TCPIP port options" repeatedly appears in a popup dialog box, check to see if Foxhound is unable to connect to a target database running on an earlier version of SQL Anywhere; e.g., version 6.

You may also see this message in the Foxhound Monitor page: -- [Adaptive Server Anywhere]Communication link failure: Communication error --

One possible explanation is the target database is not running.


[ Top ]
Message: Error: SQLCODE = ..., SQLSTATE = ..., ERRORMSG() = ...

Explanation:

Something went wrong when you pressed one of these buttons on the Foxhound Monitor Options page:

  • Create Connection Strings

  • Start All Monitor Sessions

  • Stop All Sessions

  • Delete All Sessions

Some more diagnostic information may be available by pressing the Display Diagnostics button on the Foxhound Options page.


[ Top ]
Message: EXCEPTION in PROCEDURE rroad_... at ...: SQLCODE = ..., SQLSTATE = ..., ERRORMSG() = ...
Message: EXCEPTION in EVENT rroad_... at ...: SQLCODE = ..., SQLSTATE = ..., ERRORMSG() = ...

Explanation:

An exception has occurred inside one of Foxhound's exception handling modules. In other words, while Foxhound was trying to record diagnostic information about one exception, another exception occurred. Information about the first exception was lost; this message describes the second exception.

Please report this error; see How do I report unexpected errors and exceptions?


[ Top ]
Message: EXCEPTION SQLCODE = ..., SQLSTATE = .., ERRORMSG() = ... in patch file "..."

Explanation: This is an unexpected error, possibly caused by an internal error in Foxhound.

Please report this error; see How do I report unexpected errors and exceptions?


[ Top ]
Message: failed to delete a file after it was processed
Message: rroad_OFSS_load failed to delete a file after it was processed

Explanation: After an OFSS batch is successfully loaded into the Foxhound database, the three files (head, data, conn) are deleted; this is normal. However, in this case, the delete operation failed for one of the files.

See also...
How do I find my OFSS samples?


[ Top ]
Message: failed to move a leftover file to the rejected subfolder
Message: rroad_OFSS_load failed to move a leftover file to the rejected subfolder

Explanation: After all the OFSS batches are processed by Foxhound (successfully or otherwise), all remaining files in the folder are moved into the rejected subfolder. In this case, the move operation failed for one of the files.

Note that you may see two messages for each file: a message describing a problem (batch rejected, etc), and this message.

Here are the reasons Foxhound moves a file to the rejected folder:

  • It is an OFSS file for a batch that was explicitly rejected.

  • It is an OFSS data file but the corresponding head file is missing.

  • It is an OFSS conn file but the corresponding head file is missing.

  • It is not an OFSS file.

  • It is an OFSS file that was successfully processed, but the normal delete operation failed.

See also...
How do I find my OFSS samples?


[ Top ]
Message: file is unavailable

Explanation: Look in the target database server console log for a message like this:

Cannot open dbspace 'xxx' from file 'incorrect-filespec'.

If that's the problem, fix the filespec in the target database

ALTER DBSPACE xxx RENAME 'correct-filespec';
and then restart the target database and reconnect from Foxhound.


[ Top ]
Message: File system error: ... SQLCODE=-1066
Message: -1066, SQLSTATE = WO027, ERRORMSG() = File system error: ..., @batch_is_ok = "Y", @batch_number = "0", @sampling_id = "0"
Message: OFSS File system error: ... SQLCODE=-1066
Message: SQLCODE = -1066, SQLSTATE = WO027, ERRORMSG() = File system error: ..., @batch_is_ok = "Y", @batch_number = "0", @sampling_id = "0"
Message: UNC File system error: ... SQLCODE=-1066

Explanation:

If a CALL load_OFSS_samples() statement fails with "File system error: ... SQLCODE=-1066", and

  • you are using a UNC file specification like CALL load_OFSS_samples ( @load_path = '\\\\Inspiron\\c\\DATA\\InspironOFSSremote\\' )

  • with a copy of Foxhound being run as a Windows service,

  • try using the dbsvc -a and -p options to create the service to run under the account name and password for a Microsoft Windows account you have created

  • instead of using dbsvc -as to run under the Windows LocalSystem account.

For example, if you created the Foxhound service with dbsvc -as, you might see the following exception that is raised by a LOAD TABLE statement inside Foxhound:

-- Foxhound5 - 2 Adhoc Query via ISQL

CALL load_OFSS_samples ( @load_path = '\\\\Inspiron\\c\\DATA\\InspironOFSSremote\\', 
                         @encryption_key = 'KeHX8?k1Rqz/5FvOu{nhx1#mQxy0@95e' ); 

Could not execute statement.
File system error: \\Inspiron\c\DATA\InspironOFSSremote
SQLCODE=-1066, ODBC 3 State="HY000"
Line 1, column 1
(Continuing after error)
Procedure completed

-- Foxhound Options - 7. Diagnostics - Display Diagnostics

2019-08-01 09:38:33.990 Full Build 5372a 2 1600Bb4(OFSS1400eh8) SQLCODE = -1066, SQLSTATE = WO027, 
   ERRORMSG() = File system error: \\Inspiron\c\DATA\InspironOFSSremote, @batch_is_ok = "Y", @batch_number = "0", @sampling_id = "0"

Here's a snippet that shows how to modify the code in C:\ProgramData\RisingRoad\Foxhound5\scripts\$create_SQL_Anywhere_17_bin64_service.bat

...
ECHO To create the Foxhound5 service...
PAUSE
"C:\Program Files\SQL Anywhere 17\Bin64\dbsvc.exe"^
  -o "C:\ProgramData\RisingRoad\Foxhound5\dbsvc_log.txt"^
  -y^
  -a youraccount^
  -p yourpassword^
  -s Automatic^
  -sn Foxhound5^
  -sd "Foxhound Version 5 Database Monitor Bin64 Service"^
  -t Network^
  -w Foxhound5 "C:\Program Files\SQL Anywhere 17\Bin64\dbsrv17.exe"^
...


[ Top ]
Message: Fill in the "Connection Strings file:" field and press Save before clicking on ...
Message: Cannot access file '...' -- The system cannot find the file specified
Message: Error: Cannot access file '...' -- The system cannot find the file specified

Explanation:

Before you click on any of these buttons on the Foxhound Monitor Options page, you must provide a valid connection strings file specification:

  • Create Connection Strings

  • Start All Monitor Sessions

  • Stop All Sessions

  • Delete All Sessions


[ Top ]
Message: Foxhound:-121;42501;Permission denied: you do not have permission to execute the procedure "sa_server_option"
Message: 121;42501;Permission denied: you do not have permission to execute the procedure "sa_server_option"
Message: Permission denied: you do not have permission to execute the procedure "sa_server_option"

Explanation: This message appears in section 14. Change Target Settings of the Monitor Options page when the user id Foxhound is using to connect to your target database is not allowed to call the sa_server_option() procedure on that database.

One solution is to use a user id with DBA privileges. Another solution is to GRANT SERVER OPERATOR TO that user id on the target database... or, just use dbsrv -zp -zl -zt to start the target database so it's unnecessary to use section 14. Change Target Settings of the Monitor Options page.

If the target database happens to be "Foxhound 5 Adhoc Schema - autostart and connect", note that GRANT SERVER OPERATOR TO ADHOC has not been (and cannot be) executed on that database... so you cannot use section 14. Change Target Settings of the Monitor Options page.

See the Connecting to Target Databases section of the Help.


[ Top ]
Message: Foxhound Extended edition is required for ...

Explanation: The Database Monitor portion of the Foxhound Basic edition will stop sampling the target database and display one of the following messages when one of its limitations of the Basic edition is exceeded:

 
3:32:14 PM    1.8s   -- Foxhound Extended edition is required for more than 1 physical processor on the target server --
3:32:12 PM    2.1s   -- Foxhound Extended edition is required for more than 1 physical processor on the target server at -- 

2:11:52 PM   10.0s   -- Foxhound Extended edition is required for more than 100 connections on one target database --
2:11:42 PM    6.5s   -- Foxhound Extended edition is required for more than 100 connections on one target database at -- 

1:58:03 AM   12.5s   -- Foxhound Extended edition is required for use with SQL Anywhere Standard or Advanced edition --
1:57:50 AM    2.4s   -- Foxhound Extended edition is required for use with SQL Anywhere Standard or Advanced edition at --

To continue sampling you must obtain an Extended edition registration key and enter it on the Foxhound About page.

See also...
What are the differences among the different editions of Foxhound: Rental, Basic and Extended?


[ Top ]
Message: Foxhound needs JavaScript to be enabled.

Explanation: Foxhound needs "JavaScript" or "Active scripting" to be enabled in the browser; here's how:

Firefox 3: Tools - Options - Content - check "Enable JavaScript"

IE 8: Tools - Internet Options - Security - Local intranet - Custom level...
   - Scripting - Active scripting - check "Enable"


[ Top ]
Message: Foxhound requires target PROPERTY ( CollectStatistics ) = Yes; i.e., do not specify dbsrv -k - sampling stopped at
Message: CollectStatistics
Message: dbsrv -k
Message: out of range for destination
Message: Value 18446744073709551615 out of range for destination

Explanation: Foxhound cannot collect performance statistics if the target server CollectStatistics feature is turned off; i.e., if SELECT PROPERTY ( 'CollectStatistics' ) returns 'No'.

This can happen after the target server is started with the -k option, or after CALL sa_server_option ( 'CollectStatistics', 'NO' ) is executed on the target database. When this happens, Foxhound stops sampling and displays these messages:

-- Foxhound requires target PROPERTY ( CollectStatistics ) = Yes; i.e., do not specify dbsrv -k - sampling stopped -- 
-- Foxhound requires target PROPERTY ( CollectStatistics ) = Yes; i.e., do not specify dbsrv -k - sampling stopped at -- 

You may also see messages like this:

-- Value 18446744073709551615 out of range for destination --
-- Value 18446744073709551615 out of range for destination at --

If this problem was caused by a CALL sa_server_option ( 'CollectStatistics', 'NO' ) on the target database,

- you may be able to fix it with a CALL sa_server_option ( 'CollectStatistics', 'YES' )

- then clicking on Start Sampling on the Foxhound Monitor page.

If this problem was caused by starting the target server with dbsrv -k,

- the CALL might not work; you may see another message Value 18446744073709551615 out of range for destination.

- In that case, try stopping the target server, and then restarting it without the dbsrv -k option.

- After that, you may have to click Start Sampling on the Foxhound Monitor page.


[ Top ]
Message: Foxhound was not available yet, probably because the Foxhound engine had not finished starting up.
Message: Foxhound now accepting requests
Message: Preparing monitor sample sessions...

Explanation:

If you have a lot of sampling sessions defined, even if they are all stopped, it takes some time for Foxhound to process them when starting up.

When this delay occurs, you may see "Foxhound was not available yet..." instead of the Foxhound Menu page.

You may also see "Preparing monitor sample sessions..." in the Foxhound database server console window for a long time before "Foxhound now accepting requests" appears.

This delay will be longest when the computer running Foxhound has just been rebooted.

You can speed up the next startup by deleting old sample sessions you no long need.


[ Top ]
Message: Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
Message: 57014: Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'

Explanation:

You may see a few of these messages in the Foxhound engine console log if you abruptly shut Foxhound down while there are a large number of sampling sessions in progress; they are safe to ignore:

I. 10/03 14:12:33. Database server shutdown requested by DBSTOP
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_sample_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
E. 10/03 14:12:38. Handler for event 'rroad_monitor_main_loop' caused SQLSTATE '57014'
E. 10/03 14:12:38. Statement interrupted by user
I. 10/03 14:12:38. Starting checkpoint of "f" (foxhound5.db) at Sun Oct 03 2010 14:12
I. 10/03 14:12:38. Finished checkpoint of "f" (foxhound5.db) at Sun Oct 03 2010 14:12
I. 10/03 14:12:40. Database server stopped at Sun Oct 03 2010 14:12


[ Top ]
Message: Hash error in patch file "..."

Explanation: The patch file may have been corrupted.

Try replacing the patch file and starting Foxhound again, then report this error; see How do I report unexpected errors and exceptions?


[ Top ]
Message: I/O error Fatal error: A disk read from file "...\foxhound5.db" failed with error code: (23) -- transaction rolled back --
Message: 23: I/O error Fatal error: A disk read from file "...\foxhound5.db" failed with error code: (23) -- transaction rolled back --
Message: A disk read from file "...\foxhound5.db" failed with error code: (23) -- transaction rolled back --
Message: transaction rolled back: I/O error Fatal error: A disk read from file "...\foxhound5.db" failed with error code: (23)

Explanation: The disk drive holding the Foxhound database may be faulty. Another possibility is that faulty RAM is causing bogus disk-related error messages, in which case the computer should be stopped before the entire disk drive is corrupted.

Here's a sample of this error message as it appears in the Foxhound monitor display:

 7:18:50 AM  6h 38m 24s  -- I/O error Fatal error: A disk read from file "C:\ProgramData\RisingRoad\Foxhound5\foxhound5.db" failed 
   with error code: (23) -- transaction rolled back --
12:41:13 AM              Alert #1: Foxhound has been unable to gather samples for 1m or longer.
12:40:26 AM     1.1s     -- I/O error Fatal error: A disk read from file "C:\ProgramData\RisingRoad\Foxhound5\foxhound5.db" failed 
   with error code: (23) -- transaction rolled back at --
12:40:25 AM     2.2s     -- Connection was terminated --
12:40:22 AM    13.7s     -- Connection was terminated at -- 
That message may be accompanied by this message in the Foxhound engine console log:
*** ERROR *** Assertion failed: 201813 (11.0.1.2276)
Checkpoint log: page buffer read failed with status 1:23

See also...
How do I see Foxhound diagnostics, errors and exceptions?
How do I report unexpected errors and exceptions?


[ Top ]
Message: Incorrect or missing encryption key ... Exception in load_OFSS_samples
Message: -1188 LOAD TABLE error: The data to load is not encrypted
Message: -840 Incorrect or missing encryption key
Message: -851 Decryption error: Missing encryption key
Message: Decryption error: Missing encryption key SQLCODE -851
Message: LOAD TABLE error: The data to load is not encrypted SQLCODE -1188
Message: Missing encryption key SQLCODE -851
Message: The data to load is not encrypted SQLCODE -1188

Explanation: The OFSS files created by CALL load_OFSS_samples() statement must have the same (or no) encryption keys as the files read by CALL load_OFSS_samples() statement.

If there are any encryption key mismatches, the CALL load_OFSS_samples() statement will fail with an exception and an ISQL error message:

start_OFSS_monitor()   load_OFSS_samples()   Result
====================   ===================   ======
no key                 no key                OK
key                    matching key          OK
no key                 key                   SQLCODE -1188  LOAD TABLE error: The data to load is not encrypted
key                    no key                SQLCODE  -851  Decryption error: Missing encryption key
key                    different key         SQLCODE  -840  Incorrect or missing encryption key
Workaround: Delete the mismatching files from the OFSS data folder, or move each set of files with matching (or no) encryption keys to a separate folder and use separate CALL load_OFSS_samples() statements.

Here are what the exceptions and error messages look like:

start_OFSS_monitor()   load_OFSS_samples()   Result
====================   ===================   ======
no key                 key                   SQLCODE -1188  LOAD TABLE error: The data to load is not encrypted

158 - 2020-07-12 10:23:41.076 Full Build 5484a 37820 1600Bd1(OFSS1600Beh1) Exception in load_OFSS_samples: SQLCODE = -1188, SQLSTATE = WL013, 
   ERRORMSG() = LOAD TABLE error: The data to load is not encrypted, batch number = 0, subject database [sampling_id is ZERO]

Could not execute statement.
LOAD TABLE error: The data to load is not encrypted
SQLCODE=-1188, ODBC 3 State="HY000"
Line 1, column 1
CALL load_OFSS_samples ( @load_path = 'C:\\DATA\\OFSS\\', @encryption_key = 'KeHX8?k1Rqz/5FvOu{nhx1#mQxy0@95e' )

start_OFSS_monitor()   load_OFSS_samples()   Result
====================   ===================   ======
key                    no key                SQLCODE  -851  Decryption error: Missing encryption key

159 - 2020-07-12 10:30:06.431 Full Build 5484a 37820 1600Bd1(OFSS1600Beh1) Exception in load_OFSS_samples: SQLCODE = -851, SQLSTATE = 08W63, 
   ERRORMSG() = Decryption error: Missing encryption key, batch number = 0, subject database [sampling_id is ZERO]

Could not execute statement.
Decryption error: Missing encryption key
SQLCODE=-851, ODBC 3 State="08001"
Line 1, column 1
CALL load_OFSS_samples ( @load_path = 'C:\\DATA\\OFSS\\' )

start_OFSS_monitor()   load_OFSS_samples()   Result
====================   ===================   ======
key                    different key         SQLCODE  -840  Incorrect or missing encryption key

162 - 2020-07-12 10:35:07.591 Full Build 5484a 37820 1600Bd1(OFSS1600Beh1) Exception in load_OFSS_samples: SQLCODE = -840, SQLSTATE = 08W62, 
   ERRORMSG() = Incorrect or missing encryption key, batch number = 0, subject database [sampling_id is ZERO]

Could not execute statement.
Incorrect or missing encryption key
SQLCODE=-840, ODBC 3 State="08001"
Line 1, column 1
CALL load_OFSS_samples ( @load_path = 'C:\\DATA\\OFSS\\', @encryption_key = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' )


[ Top ]
Message: Info: HTTPValidityCheck failed on the Monitor Options page; input values ignored.
Message: HTTPValidityCheck failed on the Monitor Options page; input values ignored
Message: input values ignored

Explanation: This message is recorded as an exception for diagnostic purposes.

Foxhound has detected a problem with the input data on the Monitor Options page that it has received from the browser.

Rather than accept any of the input data and risk storing bad data in the database, Foxhound has rejected all the data received from the Monitor Options page.

Try closing and reopening the Monitor Options page, and reentering your changes.

If the situation persists, please contact Breck.Carter@gmail.com.


[ Top ]
Message: Info: Unique index collision avoided: ping_id = ... ping_log_inserted_at = ... sampling_id = ...
Message: 011c-irpl1(011c-irpl1) Info: Unique index collision avoided: ping_id = ... ping_log_inserted_at = ... sampling_id = ...
Message: 206b2a(206eh4) SQLCODE = -196, SQLSTATE = "23505", ERRORMSG() = "Index 'ix_ping_inserted' for table 'rroad_ping_log' would not be unique"
Message: Index 'ix_ping_inserted' for table 'rroad_ping_log' would not be unique
Message: SQLCODE = -196, SQLSTATE = "23505", ERRORMSG() = "Index 'ix_ping_inserted' for table 'rroad_ping_log' would not be unique"
Message: Unique index collision avoided: ping_id = ... ping_log_inserted_at = ... sampling_id = ...

Explanation: These are unexpected error messages.

If you see either of these messages, please contact Breck.Carter@gmail.com:

011c-irpl1(011c-irpl1) Info: Unique index collision avoided: ping_id = ... ping_log_inserted_at = ... sampling_id = ...
206b2a(206eh4) SQLCODE = -196, SQLSTATE = "23505", ERRORMSG() = "Index 'ix_ping_inserted' for table 'rroad_ping_log' would not be unique"


[ Top ]
Message: input schema version ... is not compatible with the Foxhound build number ...
Message: rroad_OFSS_load rejected a batch because the input schema version ... is not compatible with the Foxhound build number ...

Explanation: You may be using OFSS code in your source database that is newer than the build of Foxhound that you are running.

Alternatively, your copy of Foxhound may accept input from older versions of OFSS code, but your OFSS code is too old.

See also...
How do I find my OFSS samples?


[ Top ]
Message: Internal Error 2203: C:\Windows\Installer\597604a.ipi,-2147287035
Message: 2203: Internal Error 2203: C:\Windows\Installer\597604a.ipi,-2147287035

Explanation:

If this message appeared while you were running the Foxhound "Unsetup" process, click OK and try running it again.

Then, don't wait too long to click on Yes when the following question appears in the User Account Control dialog box:

"Do you want to allow the following program from an unknown publisher to make changes to this computer?


[ Top ]
Message: Internal error; bad call to rroad_update_rroad_global_options: column = "...", value = "..."
Message: bad call to rroad_update_rroad_global_options: column = "...", value = "..."

Explanation:

Please report this unexpected error; see How do I report unexpected errors and exceptions?


[ Top ]
Message: Internal error: Do not attempt to UPDATE rroad_connection_string.connection_string_name
Message: Do not attempt to UPDATE rroad_connection_string.connection_string_name

Explanation:

Please report this unexpected error; see How do I report unexpected errors and exceptions?


[ Top ]
Message: Internal error: No code exists to validate connection-level property ...
Message: No code exists to validate connection-level property "..."

Explanation:

Please report this unexpected error; see How do I report unexpected errors and exceptions?


[ Top ]
Message: Internal error: Retry loop failed to find a Top Sample or Most Recent Sample to display.
Message: Retry loop failed to find a Top Sample or Most Recent Sample to display.

Explanation:

When Foxhound encounters invalid data ("Value out of range", etc.) when trying to display a sample in the Top Sample of the History page or the Most Recent Sample of the Monitor page, it skips that sample by marking it lost and then looks for an earlier sample to display.

If it performs this process 100 times without finding a valid sample, it gives up an issues an "Internal error: Retry loop failed to find a Top Sample or Most Recent Sample to display." message instead.

Please report this error; see How do I report unexpected errors and exceptions?

If possible, include the diagnostic dumps for the previous exceptions involving invalid data; here is an example:

1. Use the Foxhound Options - 8. Diagnostics - Display Diagnostics button to find the exception id for the "Retry loop failed" exception, 9670 in this case:

9670 - 2012-02-28 13:38:52.695 Full Build 4025a 32470 182a5(182eh2) Internal error: Retry loop failed 
   to find a Top Sample or Most Recent Sample to display.

The "Retry loop failed..." exception was preceded by 100 other exception messages; here are the last two...

9668 - 2012-02-28 13:38:52.542 Full Build 4025a 32470 182a3(182eh1) SQLCODE = -158, SQLSTATE = 22003, 
   ERRORMSG() = Value 46116860613593576000 out of range for destination
9669 - 2012-02-28 13:38:52.680 Full Build 4025a 32470 182a3(182eh1) SQLCODE = -158, SQLSTATE = 22003, 
   ERRORMSG() = Value 46116860613593576000 out of range for destination

2. Run adhoc queries to see the associated diagnostic exception dumps (see How do I run adhoc queries on the Foxhound database?):

SELECT * FROM exception_dump WHERE exception_id IN ( 9668, 9669 );

9668,5720,2012-02-28 13:38:52.638,'''182a3'',''(182eh1)'',5,174924,''N'',''Y'','''',48135,141,0,2012-02-25 23:37:06.233,
   ''12.0.1.3457'',''12.0.1.3457'',8192,''Y'',''Y'',''Y'',346348371968,346348371968,346348371968,346348371968,''connected'',
   3,1703587580,2145158597,5064721575,0,4603399663,41,4832,78,17480984,0,0,409567321,62331053,''/xxx/xxx.db'',
   0,746148869,536379770,4294966040,11157,33435808,''synchronous'',''synchronized'',15,4,0,''connected'',46116860613593576,
   5,''Off'',60,2055699670,''xxx'',''2012-01-25 20:23:24.305352'',0,50532,50923,113980,2821290,0,3081820,0,261656,1,0,87,
   0,0,0,0,1230,11,76,0,0,55581,251471,43,15624,6,0\x0d\x0a'

9669,5721,2012-02-28 13:38:52.757,'''182a3'',''(182eh1)'',5,174917,''N'',''Y'','''',61238,145,0,2012-02-25 23:36:15.701,
   ''12.0.1.3457'',''12.0.1.3457'',8192,''Y'',''Y'',''Y'',346348371968,346348371968,346348371968,346348371968,''connected'',
   3,1703536657,2145044617,5061900285,0,4600317839,39,4832,78,17480984,0,0,409305665,62331052,''/xxx/xxx.db'',
   0,746148782,536379770,4294966040,11157,33435808,''synchronous'',''synchronized'',16,4,0,''connected'',46116860613593576,
   5,''Off'',60,2055698440,''xxx'',''2012-01-25 20:23:24.305352'',0,63667,47745,145261,6110614,0,6198114,0,88976,2,0,1455,
   0,0,0,0,1144,12,75,0,0,118312,251428,14,15618,5,0\x0d\x0a'

See also...
How do I report unexpected errors and exceptions?
How do I run adhoc queries on the Foxhound database?
How do I see the schema for adhoc reporting?


[ Top ]
Message: Invalid database engine command line

Explanation: If Foxhound is trying to make connection to a local SQL Anywhere 5.5 target database, make sure that "Agent - Not Specified" is selected on the Startup Options dialog box of the ODBC DSN. In particular, the registry entry for the ODBC DSN should not include an "Agent"="..." line.


[ Top ]
Message: Invalid database server command line

Explanation: This is a generic error message produced by the dbspawn.exe utility when the Foxhound database fails to start properly because dbsrv17.exe has detected some problem. To determine what the real problem is, try using one of the "debug" scripts to start the Foxhound engine:

Help - Introduction - Starting Foxhound - Method 2: Debug Startup

See also...
Can't open Message window log file: foxhound5_debug.txt


[ Top ]
Message: Invalid server and/or database name: The database engine is stopping.

Explanation:

The Foxhound database was started with an unexpected server and/or database name, possibly because one of the Foxhound command files was incorrectly edited.


[ Top ]
Message: Invalid user ID or password

Explanation: Passwords may be cAsE sEnSiTiVe in target databases created with SQL Anywhere Version 10 and later.

Perhaps the password has changed and Foxhound needs to use the new value:

  • If this message appears on the Foxhound Monitor page for a session that uses an ODBC DSN to connect, and the user id and password specified inside that DSN are used to make the connection, try updating the DSN to specify the new password.
  • If this message appears on the Foxhound Monitor page for a session that uses an ODBC DSN to connect, but the user id and password were explicitly specified on the Foxhound menu when the Monitor session was originally started, try specifying the user id and new password on the menu page and clicking on the Monitor Database button again.


[ Top ]
Message: Management of procedure rroad_ ... _properties failed on ...: SQLCODE = ..., SQLSTATE = ..., ERRORMSG() = ...
Message: Permission denied: you do not have permission to use the "CREATE PROCEDURE" statement

Explanation: If you see SPs: NNN on the Monitor or History pages, check Foxhound Options - 7. Diagnostics - Display Diagnostics.

If you see the "Management of procedure ... failed on" messages, something went wrong with the Foxhound process that tries to push the three special procedures to your target database:

rroad_connection__properties
rroad_database_properties
rroad_engine_properties

If you see "Permission denied: you do not have permission to use the "CREATE PROCEDURE" statement" try using a different user id for Foxhound to connect to the target database, or manually create the rroad_xxx_procedures ahead of time:

2020-07-08 13:57:13.310 Full Build 5482a 1000059723 701.e3(701eh3) Management of procedure rroad_engine_properties failed on ddd17 string: 
   SQLCODE = -660, SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere]
   Permission denied: you do not have permission to use the "CREATE PROCEDURE" statement [8-ddd17 string]
2020-07-08 13:57:13.321 Full Build 5482a 1000059723 702.e3(702eh3) Management of procedure rroad_database_properties failed on ddd17 string:  
   SQLCODE = -660, SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere] 
   Permission denied: you do not have permission to use the "CREATE PROCEDURE" statement [8-ddd17 string]
2020-07-08 13:57:13.333 Full Build 5482a 1000059723 700.e3(700eh3) Management of procedure rroad_connection_properties failed on ddd17 string:  
   SQLCODE = -660, SQLSTATE = WO005, ERRORMSG() = Server 'p002': [SAP][ODBC Driver][SQL Anywhere] 
   Permission denied: you do not have permission to use the "CREATE PROCEDURE" statement [8-ddd17 string]

If you see the message "Duplicate Foxhound sampling sessions" because you have two sampling sessions connected to the same physical target database,

  • perhaps via one connection to a High Availability primary database

  • and another connection to the High Availability partner database that is acting as the primary,

an attempt to upgrade a procedure may fail on one of the connections because the upgrade has already worked on the other connection; for example:

8 2019-03-31 13:13:52.666 Full Build 5277a 1000000027 700.e3(700eh3) 
   Management of procedure rroad_connection_properties failed on primary_demo: 
   SQLCODE = -660, SQLSTATE = WO005, ERRORMSG() = Server 'p005': [SAP][ODBC Driver][SQL Anywhere]
   Item 'rroad_connection_properties' already exists [5-primary_demo]
9 2019-03-31 13:13:52.713 Full Build 5277a 1000000025 700.e4(701eh2) 
   Info: Procedure rroad_connection_properties has been upgraded to build number 5277 on partner1_demo [3-partner1_demo]

For more help, contact Breck.Carter@gmail.com


[ Top ]
Message: Mini-restore exception: SQLCODE = ... SQLSTATE = ... ERRORMSG() = ...

Explanation:

This message was produced by the Foxhound Activation page when an exception occurred while preparing to perform a Mini-Restore.


[ Top ]
Message: Mini-restore failed: the DB_PROPERTY ( FILE ) was unavailable
Message: Mini-restore failed: the build number was different
Message: Mini-restore failed: the sampling tables were not empty

Explanation:

This message was produced by the Foxhound Activation page when the Mini-Restore failed for one of several reasons:

the call to DB_PROPERTY ( FILE ) returned an empty, NULL or blank value
the sampling tables were not empty
the build number was different


[ Top ]
Message: Mini-restore succeeded using file ...
Message: Info: Mini-restore succeeded using file ...

Explanation:

This message was produced by the Foxhound Activation page when it successfully activated Foxhound via Option 2: Activate Foxhound with a Mini-Restore.


[ Top ]
Message: Modifications not permitted for read-only database SQLCODE=-757
Message: -757 Modifications not permitted for read-only database
Message: Could not execute statement. Modifications not permitted for read-only database SQLCODE=-757
Message: OFSS Modifications not permitted for read-only database SQLCODE=-757
Message: SQLCODE = -757 Modifications not permitted for read-only database

Explanation: The Offline Foxhound Sampling Service (OFSS) doesn't work on read-only subject databases because the OFSS scripts can't modify the database.

This limitation affects High Availability secondary (mirror) and read-only scale-out databases in particular.

C:\HASETUP2-V17>"C:\Program Files\SQL Anywhere 17\bin64\dbisql.com"
  -c "SERVER=secondary_server; UID=dba; PWD=sql; HOST=localhost:55502,localhost:55503; CON=Secondary;"
  READ ENCODING Cp1252 "C:\ProgramData\RisingRoad\Foxhound5\scripts\OFSS_1_setup.sql" [OFSS]
You have connected to a read-only database.
Some Interactive SQL functionality will be disabled.
10 row(s) affected

Could not execute statement.
  Modifications not permitted for read-only database
  SQLCODE=-757, ODBC 3 State="42000"

C:\ProgramData\RisingRoad\Foxhound5\scripts\OFSS_1_setup.sql:83
  CREATE TABLE "OFSS".OFSS_settings (

You can continue executing or stop.
1. Stop
2. Continue
Select an option:

Administrative Tip: When using OFSS on a High Availability setup, run the OFSS setup and start_OFSS_monitor() on the primary, not the underlying partner. After a failover, you can then rerun the CALL start_OFSS_monitor() on the primary because it will be updatable.

You can also run OFSS on the arbiter server if it has a database.


[ Top ]
Message: moved a leftover file to the rejected subfolder
Message: rroad_OFSS_load moved a leftover file to the rejected subfolder

Explanation: After all the OFSS batches are processed by Foxhound (successfully or otherwise), all remaining files in the folder are moved into the rejected subfolder. This message is produced for each file that is moved.

Note that you may see two messages for each file: a message describing a problem (batch rejected, etc), and this message.

Here are the reasons Foxhound moves a file to the rejected folder:

  • It is an OFSS file for a batch that was explicitly rejected.

  • It is an OFSS data file but the corresponding head file is missing.

  • It is an OFSS conn file but the corresponding head file is missing.

  • It is not an OFSS file.

  • It is an OFSS file that was successfully processed, but the normal delete operation failed.

See also...
How do I find my OFSS samples?


[ Top ]
Message: No complete sample data is available for display in the "Top Sample" section for this database.

Explanation:

The Monitor or History page is unable to display anything in the "Top Sample" section because no successful samples have been gathered for this target database, or because ping-only sampling has always been in effect.


[ Top ]
Message: No detailed information about the ... connection(s) is recorded for the sample taken at ...
Message: No detailed information about blocked connections is recorded for the sample taken at ...

Explanation:

When Foxhound is successfully gathering samples there is always at least one connection to the target database: the connection from Foxhound itself.

However, information about individual connections may not be recorded because it has been deleted or it was never recorded in the first place.

If that is the case, the blocked connections and current connections sections will display these messages:

   No detailed information about blocked connections is recorded for the sample taken at ...
   No detailed information about the ... connection(s) is recorded for the sample taken at ... 

Here are the reasons information about individual connections may not be recorded.

   The number of connections exceeded the Foxhound Options - Connection Sampling Threshold when the sample was recorded.
   The Monitor Options - Connection Sample Schedule was set to skip connections when the sample was recorded.
   The Foxhound Options - Purge process has deleted all the connection information for the sample.


[ Top ]
Message: No information about ... connections has been gathered yet.

Explanation: No samples have been recorded yet so there is no information about blocked connections yet either.

Two versions of this message are produced; here's the full text:

No information about blocked connections has been gathered yet.

No information about connections has been gathered yet.


[ Top ]
Message: No information about ... connections is available for the sample lost at ...

Explanation: This sample was lost so there is no information about connections.

Two versions of this message are produced; here's the full text:

No information about blocked connections is available for the sample lost at xxx.

No information about connections is available for the sample lost at xxx.


[ Top ]
Message: No information about this database is available for display in the "Monitor Status Area".

Explanation:

The Monitor page is unable to display anything in the "Monitor Status Area" because no successful samples have been gathered for this target database, or because ping-only sampling has always been in effect.


[ Top ]
Message: No information about this database is available for display in the "Sample History Status Area".

Explanation:

The History page is unable to display anything in the "Monitor Status Area" because no successful samples have been gathered for this target database, or because ping-only sampling has always been in effect.


[ Top ]
Message: No OFSS batches were found

Explanation: It's OK to repeatedly call rroad_OFSS_load when there's nothing (yet) to process.

In particular, the Foxhound rroad_OFSS_load procedure looks for "head" files with correctly formatted file names. This rroad_OFSS_load.status value is returned when no such files are found in the input folder.

See also...
How do I find my OFSS samples?


[ Top ]
Message: No patches were processed.

Explanation: This is a normal message.

No new patch files were found in the Foxhound folder, and no previous patches needed to be re-applied after a Mini-Restore or data upgrade process.


[ Top ]
Message: OFSS batch (file "...") was rejected because the OFSS build number ... is not compatible with the Foxhound build number ...

Explanation: The OFSS Load Component inside Foxhound will not accept batch files from an OFSS Monitor component that is more recent (higher build number).


[ Top ]
Message: OFSS batch number ... (file "...") was rejected because it had been previously processed.

Explanation: The OFSS Load Component inside Foxhound read two consecutive batch files with the same batch number. The first file was accepted and the second was rejected.


[ Top ]
Message: OFSS batch number ... (file "...") was rejected because it was received out of order (after batch number ...).

Explanation: The OFSS Load Component inside Foxhound read two consecutive batch files where the first file had a larger batch number than the second. The first file was accepted and the second was rejected.


[ Top ]
Message: OFSS is supported for SQL Anywhere versions 12, 16 and 17, not version ...

Explanation: The Offline Foxhound Sampling Service (OFSS) is only supported for subject databases running on SQL Anywhere versions 12, 16 and 17, for the following reasons:

  • The DATEDIFF MILLISECOND function returns INTEGER as opposed to BIGINT in SQL Anywhere 11 and earlier.

  • The SQL SECURITY INVOKER clause is not supported in SQL Anywhere 10 and earlier.

See also...
Foxhound 5 » Introduction and Setup - Requirements


[ Top ]
Message: OFSS sampling id is zero for batch file "..."

Explanation: The OFSS Load Component inside Foxhound failed to process a batch file for some unknown reason.

Please report this error; see How do I report unexpected errors and exceptions?


[ Top ]
Message: Older samples purged at ...

Explanation: The Foxhound purge process last ran at the "Older sample purged at ..." date/time, and the sample date/time shown to the left identifies the most recent sample that was deleted.

See Foxhound Options - Purge sample data.


[ Top ]
Message: Only the Extended edition of Foxhound can be started with a SQL Anywhere server name other than "foxhound5".
Message: Foxhound can only be started with the SQL Anywhere database name set to "f".

Explanation:

Short answer: Use "foxhound5" and "f" as the SQL Anywhere server and database names for Foxhound.

Long answer...

The SQL Anywhere server name must be set to "foxhound5" for the Rental Edition and Basic Edition of Foxhound, and the SQL Anywhere database name must be set to "f" for all editions of Foxhound.

For example, the server name option "-n foxhound5" and database name option "-n f" are the standard settings that appear in all the installed shortcuts that start Foxhound.

The SQL Anywhere server name may be set to something other than "foxhound5" for the Extended Edition to allow multiple instances of Foxhound to be started on the same computer.

Note: This freedom to use any server name extends to the "GA" edition of Foxhound, where "GA" is the edition name given to a copy of Foxhound that has not been activated yet. In this case it is expected that Foxhound will be activated as a new Extended Edition copy.

If a "GA" copy of Foxhound is running with a SQL Anywhere server name other than "foxhound5", and an attempt is made to activate it with anything other than a "New Extended Edition" key, that attempt will fail.

See also...
What are the differences among the different editions of Foxhound: Rental, Basic and Extended?


[ Top ]
Message: Option 1 displayed: Activate Foxhound with a Registration Key
Message: Info: Option 1 displayed: Activate Foxhound with a Registration Key

Explanation:

This message was produced by the Foxhound Activation page when it offered Option 1: Activate Foxhound with a Registration Key.


[ Top ]
Message: Option 2: Activate Foxhound with a Mini-Restore is not offered because ...
Message: Info: Option 2: Activate Foxhound with a Mini-Restore is not offered because Foxhound is already activated.
Message: Info: Option 2: Activate Foxhound with a Mini-Restore is not offered because no mini-backup files matching build number ... were found.
Message: Info: Option 2: Activate Foxhound with a Mini-Restore is not offered because the Foxhound folder was not found.
Message: Info: Option 2: Activate Foxhound with a Mini-Restore is not offered because the sampling tables are not empty.

Explanation:

This message was produced by the Foxhound Activation page when it did not offer Option 2: Activate Foxhound with a Mini-Restore for one of several reasons:

... because Foxhound is already activated.
... because the sampling tables are not empty.
... because the Foxhound folder was not found.
... because no mini-backup files matching build number ... were found.


[ Top ]
Message: Option 2 displayed: Activate Foxhound with a Mini-Restore
Message: Info: Option 2 displayed: Activate Foxhound with a Mini-Restore

Explanation:

This message was produced by the Foxhound Activation page when it offered Option 2: Activate Foxhound with a Mini-Restore.


[ Top ]
Message: overlapping sample timestamp
Message: rroad_OFSS_load rejected a batch because of an overlapping sample timestamp

Explanation: Foxhound received a second OFSS batch with the same or overlapping sample timestamp value(s) as a batch that was previously successfully processed.

Foxhound rejects the batch and moves the file to the rejected subfolder.

See also...
How do I find my OFSS samples?


[ Top ]
Message: Parse error: Invalid or missing keyword near 'CPOOL‘
Message: Error in syntactical analysis: Invalid or missing keyword near 'CPOOL‘.
Message: Invalid or missing keyword near 'CPOOL‘

Explanation: Try using a different ODBC driver for the Foxhound connection to the target database.

For example, try using the ODBC driver from a more recent version of SQL Anywhere, which will probably be backward compatible with your target database; e.g., DRIVER=SQL Anywhere 16 will work with a SQL Anywhere 10 database.

There may be compatibility issues between the particular ODBC driver you are using and the ODBC connection options used by Foxhound.


[ Top ]
Message: Patch file OK "..."

Explanation: The named patch file was processed successfully.


[ Top ]
Message: Permission denied: Cannot CREATE PROCEDURE rroad_...
Message: Cannot CREATE PROCEDURE rroad_...

Explanation: Foxhound has been unable to create one or more of the following procedures on the target database:

rroad_connection_properties

rroad_database_properties

rroad_engine_properties

Foxhound will still work but performance of Foxhound itself may be affected, especially if there are a lot of connections to the target database.

One solution is to GRANT RESOURCE to the user id Foxhound uses to connect to the target database.

Another solution is to create the procedures yourself on the target database, with the Foxhound user id as the owner; see Help - Introduction - Connecting to Target Databases.


[ Top ]
Message: Permission denied: you do not have permission to execute a statement of this type
Message: you do not have permission to execute a statement of this type

Explanation: If the target is a SQL Anywhere High Availability arbiter server without a database, Foxhound cannot open a direct ODBC connection because there's no database.

In this case, one alternative is to switch to ping-only sampling; see section 16. Ping Settings - Perform Ping-Only Sampling on the Monitor Options page.

Another alternative is to restart the arbiter server with its own (empty?) database so Foxhound can start sampling via a direct ODBC connection to the target database.


[ Top ]
Message: Pick a valid ODBC DSN, and specify the user id and password on the Foxhound DSN tab or inside the DSN itself
Message: Please fill in both User Id and Password, or leave both empty.

Explanation: When using the DSN tab on the Foxhound menu to choose Display Schema or Monitor Database, both the user id and password values must be specified together, in the same place: either explicitly in the User Id: and Password: fields on the menu, or inside the target database ODBC DSN itself.

Currently, Foxhound cannot deal with the following scenarios:

  • A DSN with an encrypted password.
    Workaround: Store the unencrypted password in the DSN, or specify the unencrypted password value in the Password: field on the menu together with the User Id: value.
  • A user id with an empty password.

    Workaround: Create a user id with a non-empty password and use that user id instead.

This message may also appear in a Database Monitor session that was once able to connect to the target database via an ODBC User DSN, but is no longer able to connect because the Foxhound database was started as a service and thus requires System DSNs in order to connect to target databases. Try deleting the User DSN and recreating it as a System DSN; that will allow Foxhound to reconnect and resume sampling in the old sampling session rather that starting a new session.


[ Top ]
Message: Procedure rroad_ ... _properties build number ... is more recent than Foxhound build number ... on ...
Message: Error: Procedure rroad_connection__properties build number ... is more recent than Foxhound build number ... on ...
Message: Error: Procedure rroad_database_properties build number ... is more recent than Foxhound build number ... on ...
Message: Error: Procedure rroad_engine_properties build number ... is more recent than Foxhound build number ... on ...

Explanation: If you see SPs: NNN on the Monitor or History pages, check Foxhound Options - 7. Diagnostics - Display Diagnostics.

If you see the "Error: Procedure ... is more recent" messages, a newer version of the Foxhound Monitor was previously used on this target database.

If so, use the new version of Foxhound instead of this one, or drop the following procedures from the target database as follows...
DROP PROCEDURE rroad_engine_properties;
DROP PROCEDURE rroad_database_properties;
DROP PROCEDURE rroad_connection_properties;

... and then use the Stop Sampling and Start Sampling buttons on the Foxhound Monitor page to get the old version of Foxhound to install its own version of these procedures.


[ Top ]
Message: Procedure 'rroad_connection_properties' not found

Explanation:

The following exception may appear when sampling is being started for a duplicate sampling session (one of two or more separate sampling sessions for the same target database):

17 2020-07-02 12:53:33.618 Full Build 5480a 1000000031 204.q5(204eh-c4) 
   SQLCODE = -660, SQLSTATE = WO005, ERRORMSG() = Procedure 'rroad_connection_properties' not found [7-ddd17]

The problem may resolve itself when Foxhound tries to reconnect to the target database.

If the problem persists, or if SPs: YYY is not displayed on the Monitor and History pages, please contact breck.carter@gmail.com.


[ Top ]
Message: Procedure rroad_engine_properties build number ... is different from the Foxhound build number ... on ...
Message: Error: Procedure rroad_connection_properties build number ... is different from the Foxhound build number ... on ...
Message: Error: Procedure rroad_database_properties build number ... is different from the Foxhound build number ... on ...
Message: Error: Procedure rroad_engine_properties build number ... is different from the Foxhound build number ... on ...
Message: Procedure rroad_connection_properties build number ... is different from the Foxhound build number ... on ...
Message: Procedure rroad_database_properties build number ... is different from the Foxhound build number ... on ...

Explanation:

The Foxhound Monitor has determined that the build number for this procedure on the target database is not correct.

The data for one sample is lost, but Foxhound may be able repair or recover from the error in order to start sampling again.


[ Top ]
Message: Procedure rroad_engine_properties has been upgraded [from build number ...] to build number ... on ...
Message: Info: Procedure rroad_connection_properties has been upgraded [from build number ...] to build number ... on ...
Message: Info: Procedure rroad_database_properties has been upgraded [from build number ...] to build number ... on ...
Message: Info: Procedure rroad_engine_properties has been upgraded [from build number ...] to build number ... on ...
Message: Procedure rroad_connection_properties has been upgraded [from build number ...] to build number ... on ...
Message: Procedure rroad_database_properties has been upgraded [from build number ...] to build number ... on ...

Explanation:

If "from build number ..." does NOT appear in the message...

...you started using Foxhound on a target database for the first time, and Foxhound pushed this stored procedure to that target database.

This message usually appears in sets of three:

... Info: Procedure rroad_engine_properties has been upgraded to build number .... on ....
... Info: Procedure rroad_database_properties has been upgraded to build number .... on ....
... Info: Procedure rroad_connection_properties has been upgraded to build number .... on ....

If "from build number ..." DOES appear in the message...

...you installed a new build of Foxhound, and when it connected to a target database it successfully pushed the new version of this stored procedure to that target database.

This message usually appears in sets of three:

... Info: Procedure rroad_engine_properties has been upgraded from build number .... to build number .... on ....
... Info: Procedure rroad_database_properties has been upgraded from build number .... to build number .... on ....
... Info: Procedure rroad_connection_properties has been upgraded from build number .... to build number .... on ....


[ Top ]
Message: proxy_rroad_..._properties returned a result set with a different schema than expected
Message: Status: proxy_rroad_connection_properties returned a result set with a different schema than expected

Explanation: If Foxhound was recently upgraded (for example, from version 3 to 4), the new version of Foxhound may not have been able to upgrade the three "rroad_..._properties" procedures (rroad_connection_properties, rroad_database_properties and rroad_engine_properties) because the target database is read-only. If the target database is a read-only scale-out copy database, try connecting the new version of Foxhound to the primary database so the rroad_..._properties" procedures can be updated, after which they will be automatically synchronized to the read-only copy database. See Help - Introduction - Connecting to Target Databases for more information about these procedures.

Another possibility is that two different versions of Foxhound are being used to monitor the same target database using the same user id:

  • Stop one of the sampling sessions, and stop and start the other one, or

  • stop both sampling sessions, change one of them to connect to the target database with a different user id, then start both sampling sessions.

[ Top ]
Message: Purge run ... which started at ... has been cancelled because it was running too long.
Message: Handler for event 'rroad_scheduled_purge' caused SQLSTATE '57014'
Message: Statement interrupted by user - Handler for event 'rroad_scheduled_purge' caused SQLSTATE '57014'
Message: User "DBA" dropped event connection ... ("rroad_scheduled_purge")

Explanation:

Messages like these may appear in the Foxhound diagnostic text file foxhound5_debug.txt:

I. 05/16 08:19:35. User "DBA" dropped event connection 1000011953 ("rroad_scheduled_purge")
E. 05/16 08:19:35. Handler for event 'rroad_scheduled_purge' caused SQLSTATE '57014'
E. 05/16 08:19:35. Statement interrupted by user

These messages appear when the Foxhound purge process has run for more than 19 minutes and is cancelled before the next purge begins at the 20-minute mark.

Your Foxhound database may be getting very large; see Help - Introduction - Controlling Growth and How do I shrink the size of the Foxhound database?.

These messages are safe to ignore if your Foxhound database isn't getting too large, and Foxhound performance isn't suffering.

Note that the message "User "DBA" dropped ... rroad_scheduled_purge" has nothing to do with Alert #1 messages.


[ Top ]
Message: Request Time-Out (408)
Message: 408: Request Time-Out

Explanation: Try using a number larger than 600 seconds for the one or both of the HTTP protocol options TimeOut (to) and KeepaliveTimeOut (kto)... or change them to zero to disable HTTP timeouts.

You can do this by editing one or more of the following Windows command files:

C:\ProgramData\RisingRoad\Foxhound5\

    $backup_foxhound5.bat
    $start_foxhound5_default_browser_debug.bat
    $start_foxhound5_default_browser.bat
    $start_foxhound5_engine.bat

C:\ProgramData\RisingRoad\Foxhound5\scripts

    $create_SQL_Anywhere_17_bin64_service.bat
    $MULTI_Step_2_dbsrv_all.bat
    $MULTI_Step_2b_dbsrv_one.bat
    $run_most_recent_mini_restore.bat
    $TEN_INSTANCES_2_dbsrv.bat 

Look for a line inside each command file that says this:

-xs http(port=80;maxsize=0;to=600;kto=600)^
and change one or both of the 600 values to zero (to disable timeouts) or something larger than 600 seconds (10 minutes).


[ Top ]
Message: rroad_OFSS_load rejected batch ... because it was not timestamped later than existing samples

Explanation: If an OFSS batch does not arrive until after a later batch is processed by Foxhound, the delayed batch will be rejected because Foxhound does not process batches out of timestamp order.

You can accept the fact the delayed batch will not appear in the Foxhound Sample History page, or you can try starting over: Delete the OFSS sampling session from Foxhound, move the deleted OFSS batch(es) back into the main OFSS folder, and call rroad_OFSS_load again. Note that when you start over, batches that were accepted earlier will no longer appear in the Foxhound Sample History page, so either way samples will be lost.

See also...
How do I find my OFSS samples?


[ Top ]
Message: Sample Schedule in effect

Explanation:

Each sample session is either under manual control, in which case various Stop and Start buttons are available, or under control of a sample schedule, in which case the schedule has control and the buttons are replaced with the message "Sample Schedule in effect".

In the latter case, the message is a link to the Monitor Options page where it is possible to modify or disable the schedule.


[ Top ]
Message: Setup error: DIAG yyyy-mm-dd hh:nn:ss.sss ...

Explanation:

Something has gone wrong during the post-setup process of a Foxhound installation.

If the full text of the "Setup error:" message doesn't help, have a look at the post_setup_trace.txt file; see How do I figure out what went wrong during an installation?

Even if the installation has replaced the old copy of your Foxhound database with a new one, you can start over again as follows:

  • Run the Foxhound "Unsetup" process (see How do I run the Foxhound "unsetup" process?),

  • restore the old copies of the foxhound5.db and foxhound5.log files from the C:\ProgramData\RisingRoad\Foxhound5\backup\previous_build folder to the C:\ProgramData\RisingRoad\Foxhound5 folder, and

  • run the Foxhound Installshield setup again.


[ Top ]
Message: Specified database file already in use

Explanation: Use the ODBC Administrator link to check the ODBC DSN for a problem like this:

The "Database file:" field is filled in and "Start database automatically" is checked, but the database is already running. If your ODBC DSN specifies different "Server name" and/or "Database name" values than the ones already in use, it will try to start the same database file a second time, and that is not allowed.
If that is the case, change the "Server name" and/or "Database name" values to match the ones already in use. You can leave the "Database file:" field is filled in and "Start database automatically" checked if you want, so your ODBC DSN will auto-start the database when it isn't already running.


This message is safe to ignore if it is produced by the All Programs - Foxhound5 - Tools - Backup Foxhound Database process.


[ Top ]
Message: Specified database not found

Explanation: Check ODBC DSN or connection string for a problem like one of these:

  • The server is running, but the database name is wrong.

  • The server is not running, and no database file is specified.

  • The server starts OK, but the specified database file is not found.

[ Top ]
Message: SQL Anywhere database server ... not supported

Explanation: Foxhound only contains code for target databases running on SQL Anywhere 5.5, 6, 7, 8, 9, 10, 11, 12, 16 and 17 engines.

Note that Foxhound 5 has not been tested with target databases running on SQL Anywhere 5.5 engines, but it has been tested with target databases created with SQL Anywhere 5.5 and running on SQL Anywhere 6 software.


[ Top ]
Message: SQL Anywhere database version ... not supported

Explanation: Foxhound only contains code for target databases created with SQL Anywhere versions 5.5, 6, 7, 8, 9, 10, 11, 12, 16 and 17.

Note that Foxhound 5 has not been tested with target databases running on SQL Anywhere 5.5 engines, but it has been tested with target databases created with SQL Anywhere 5.5 and running on SQL Anywhere 6 software.


[ Top ]
Message: SQL Anywhere version ... not supported.

Explanation: Foxhound only contains code for target databases created with SQL Anywhere versions 5.5, 6, 7, 8, 9, 10, 11, 12, 16 and 17.

Note that Foxhound 5 has not been tested with target databases running on SQL Anywhere 5.5 engines, but it has been tested with target databases created with SQL Anywhere 5.5 and running on SQL Anywhere 6 software.


[ Top ]
Message: SQL Anywhere version ... or later is required to run this application.
Message: However, version ... is actually being used.
Message: Please install version ... or later. See www.sap.com.

Explanation: Other versions of SQL Anywhere can be used to run the target databases, but Foxhound itself requires a particular version to run.


[ Top ]
Message: SQLANY17 environment variable not set properly.
Message: ERROR SQLANY17 environment variable not set properly.

Explanation: Foxhound requires SQL Anywhere 17 to run its own database.

C:\ProgramData\RisingRoad\Foxhound5>ECHO OFF
Foxhound5 - 1 Start Foxhound
******************************************************************
*** ERROR ********************************************************
*** SQLANY17 environment variable not set properly.
*** Install SQL Anywhere 17.
Press any key to continue . . .

The SQLANY17 environment variable is optional, but by default it is used by the delivered *.bat files. Either perform a standard installation of SQL Anywhere 17 to get SQLANY17 set up, or edit the *.bat files to replace references to SQLANY17.

If you have recently installed SQL Anywhere 17, the SQLANY17 environment variable may not yet be visible to your Windows session for some unknown reason. Try using Control Panel to view the environment variables to make them visible: Control Panel - System - Advanced System Settings - Environment Variables - System Variables

If the system PATH variable is too long, one of the symptoms may be that the SQLANY17 environment variable is not visible to your Windows session. To fix this condition, launch the C:\Windows\System32\SystemPropertiesAdvanced.exe program and use

Environment Variables... 
   - System Variables 
   - select Path 
   - Edit...
to remove duplicate or unnecessary entries from the system PATH.

See also...
What are the Foxhound system requirements?


[ Top ]
Message: SQLCODE = -307, SQLSTATE = 40W06, ERRORMSG() = All threads are blocked
Message: -307: All threads are blocked
Message: 40W06: All threads are blocked
Message: All threads are blocked

Explanation:

If this error occurred in Foxhound itself, rather than on a target database, please report it: How do I report unexpected errors and exceptions?

See also...
How do I see Foxhound diagnostics, errors and exceptions?


[ Top ]
Message: SQLCODE = -660, SQLSTATE = WO005, ERRORMSG() = Server 'p001': [Microsoft][ODBC SQL Server Driver][SQL Server] Incorrect syntax near the keyword 'TRANSACTION'
Message: 660 Incorrect syntax near the keyword 'TRANSACTION'
Message: Incorrect syntax near the keyword 'TRANSACTION'

Explanation:

Foxhound cannot use a Microsoft SQL Server ODBC DSN to connect to a target database. Try using a SQL Anywhere ODBC DSN, and only use Foxhound with SQL Anywhere databases.

7338	2017-02-08 08:52:30.818 Full Build 4729a 1000000037 240a1a(240eh1) SQLCODE = -660, SQLSTATE = WO005, 
   ERRORMSG() = Server 'p001': [Microsoft][ODBC SQL Server Driver][SQL Server]
   Incorrect syntax near the keyword 'TRANSACTION'. [1-WSX_NZ]
7339	2017-02-08 08:52:30.818 Full Build 4729a 1000000037 204.b5(204eh-d7) SQLCODE = -660, SQLSTATE = WO005, 
   ERRORMSG() = Server 'p001': [Microsoft][ODBC SQL Server Driver][SQL Server]
   Incorrect syntax near the keyword 'TRANSACTION'. [1-WSX_NZ]


[ Top ]
Message: Statement interrupted by user

Explanation: It is probably safe to ignore all "Statement interrupted by user" exceptions, especially if you aren't seeing any other symptoms:

   11 2010-12-26 13:49:13.066 Full Build ----- 5809 050a5(050eh1) SQLCODE = -299, SQLSTATE = 57014, 
      ERRORMSG() = Statement interrupted by user
When you hit the browser Back or Refresh buttons while Foxhound's web interface is executing a query or some other operation on the Foxhound database, Foxhound may record a "Statement interrupted by user" exception. Nothing bad has happened; Foxhound is simply being overzealous when it records this event as an exception.

See also...
How do I see Foxhound diagnostics, errors and exceptions?


[ Top ]
Message: Syntax error: syntax error near ...

Explanation: If the target database is using SQL Anywhere 5.5 and you get one of these messages, try upgrading the target database engine to 5.5.5.2787:

Syntax error: near 'rroad_..._properties' in "[rroad_..._properties]"

Syntax error: syntax error near 'creator'

Syntax error: syntax error near 'sa_conn_properties'

Syntax error: syntax error near 'table_name'


[ Top ]
Message: Target SQL Anywhere server version ... not supported

Explanation: Check the Foxhound website to see if there is a more recent build of Foxhound that does support target databases using the version of SQL Anywhere shown in the message.


[ Top ]
Message: The $backup_foxhound5_log.bat file did not find an existing full backup of the database and log files in the folder ...

Explanation:

Before running the All Programs - Foxhound5 - Tools - Backup Foxhound Transaction Log shortcut, you have run the Backup Foxhound Database shortcut at least once:

C:\Windows\system32>ECHO OFF
Backup Foxhound Transaction Log
******************************************************************
*** ERROR ********************************************************
*** The $backup_foxhound5_log.bat file did not find an existing
*** full backup of the database and log files in the folder
*** C:\ProgramData\RisingRoad\Foxhound5\backup\generation3
*** Try running $backup_foxhound5.bat first,
*** then try running $backup_foxhound5_log.bat again,
*** then contact Breck.Carter@gmail.com
******************************************************************
Press any key to continue . . .


[ Top ]
Message: The activation upgrade was not successful: The registration key has been used before.

Explanation:

You get this message when you try to use an activation key more than once. If you are trying to upgrade or renew Foxhound, you must obtain a registration key for that purpose; see How do I get a registration key for Foxhound?


[ Top ]
Message: The connection was refused when attempting to contact localhost

Explanation: Start the Foxhound engine and try again.


[ Top ]
Message: The data upgrade process has begun: to build ... from ...

Explanation: The Foxhound post-setup process has begun to copy and upgrade the data stored in a previous version of the Foxhound database.

More information may be found in this file on Windows 10:

C:\ProgramData\RisingRoad\Foxhound5\setup\post_setup_trace.txt

See also...
How do I install a new version of Foxhound?


[ Top ]
Message: The data upgrade process has failed: to build ... from ...; diagnostics = "..."

Explanation: The Foxhound post-setup process was unable to copy and upgrade the data stored in a previous version of the Foxhound database. This doesn't stop the new installation, but it does mean the history of Monitor samples and alerts did not get copied over to the new installation, nor did your Foxhound option and alert settings.

More information may be found in this file on Windows 10:

C:\ProgramData\RisingRoad\Foxhound5\setup\post_setup_trace.txt

See also...
How do I install a new version of Foxhound?


[ Top ]
Message: The data upgrade process has succeeded: to build ... from ...

Explanation: The Foxhound post-setup process has successfully copied and upgraded the data stored in a previous version of the Foxhound database.

More information may be found in this file on Windows 10:

C:\ProgramData\RisingRoad\Foxhound5\setup\post_setup_trace.txt

See also...
How do I install a new version of Foxhound?


[ Top ]
Message: The Foxhound database must run on its own SQL Anywhere engine.

Explanation: Here is the full message text:

The Foxhound database must run on its own SQL Anywhere engine.
   Do not start another database on the same engine, and
   do not start the Foxhound database on an engine that is already running another database.
It is possible that some other database was accidentally started (or auto-started) on the SQL Anywhere engine that is running Foxhound. By default the server command lines that start Foxhound specify the dbsrv17 -sb 0 and -xd options to prevent that from happening.

To get around this problem, take whatever steps are necessary to prevent any other database from being started on the Foxhound engine, and then stop and restart the Foxhound engine.


[ Top ]
Message: The initial activation was not successful: The registration key did not work.

Explanation: The registration key you entered is either invalid, or it will not work on the copy of Foxhound you have installed.

Enter the correct registration key, or get a copy of Foxhound that will work with the key you have, or get another key.


[ Top ]
Message: The process cannot access the file because it is being used by another process.

Explanation: If this message appears during the "post setup" step during a Foxhound upgrade, it probably means the Foxhound engine is already running as a service and it cannot be stopped by the post setup process. As a result, the Foxhound upgrade will not work properly.

Try stopping the service and rerunning the upgrade, including the initial "unsetup" step: How do I install a new version of Foxhound?

See also...
How do I install a new version of Foxhound?


[ Top ]
Message: The remote table 'pxxx..SYS.DUMMY' could not be found
Message: DUMMY' could not be found
Message: SYS.DUMMY' could not be found

Explanation:

If Foxhound displays a message like this when it's trying to use DRIVER=SQL Anywhere 17 to connect to an Adaptive Server Anywhere 9.0 or earlier target database:

1:50:37 PM   17.3m   -- The remote table 'p005..SYS.DUMMY' could not be found -- 
1:33:16 PM   -       -- The remote table 'p005..SYS.DUMMY' could not be found at -- 

try changing the ODBC driver in the DSN or connection string to use DRIVER=SQL Anywhere 10, 11, 12 or 16 (DRIVER=SQL Anywhere 17 seems to have trouble):

String: ENG=ddd9; DBN=ddd9; UID=dba; PWD=sql; DRIVER=SQL Anywhere 16;

Alternatively, try starting Foxhound with the 32-bit version of SQL Anywhere and specifying a 32-bit ODBC driver; e.g., DRIVER=Adaptive Server Anywhere 9.0.

See also...
The specified DSN contains an architecture mismatch between the Driver and Application


[ Top ]
Message: The specified DSN contains an architecture mismatch between the Driver and Application
Message: architecture mismatch between the Driver and Application

Explanation:

Try starting Foxhound with the 32-bit version of SQL Anywhere.

See also...
The remote table 'pxxx..SYS.DUMMY' could not be found


[ Top ]
Message: The start_OFSS_monitor() procedure has already been called on a different connection. Use that connection, or drop it and use this connection.
Message: start_OFSS_monitor() procedure has already been called on a different connection.
Message: Use that connection, or drop it and use this connection.

Explanation:

If you execute a second CALL start_OFSS_monitor() on an OFSS subject database while the first CALL is still executing, the second CALL will be rejected and this message will appear in the SQL Anywhere diagnostic console log:

-- I. The start_OFSS_monitor() procedure has already been called on a different connection. Use that connection, or drop it and use this connection.

Note that this limitation only applies on the subject database side of the OFSS process. On the Foxhound side, multiple instances of CALL load_OFSS_samples() with different values of @load_path can be executing at the same time.


[ Top ]
Message: The system cannot find the file specified.

Explanation: This message is safe to ignore if it is produced by the All Programs - Foxhound5 - Tools - Backup Foxhound Database process.


[ Top ]
Message: The system cannot find the path specified.

Explanation: This message may indicate that SQL Anywhere 16 should be installed or reinstalled.

See also...
What are the Foxhound system requirements?


[ Top ]
Message: The system could not find the environment option that was entered.

Explanation: The FOXHOUND5 environment variable may not be set yet; see How do I get the new value of the FOXHOUND5 environment variable to show up after Foxhound is installed?


[ Top ]
Message: The table ... has more than one index on columns ( ... )

Explanation: Multiple indexes on the same columns often indicate an inefficiency or error in database design. Sometimes multiple indexes are redundant, and redundant indexes may waste space in the database; they may also waste time every time a row is inserted or deleted, and every time the indexed columns are updated. Other times, multiple indexes aren't redundant, but they still might indicate a flaw in the database design.

Note: Versions 10 and later of SQL Anywhere do not create duplicate physical indexes when duplicate logical indexes are defined. However, Foxhound still warns about these duplicates because it may be a design issue. The duplication may affect performance; e.g., if one of the indexes is incorrect it may not be used to improve performance in the way it was intended. It may also affect integrity; e.g., if one of the indexes is a foreign key referring to the wrong column it may not be used to check referential integrity in the way it was intended.

Note: Versions 7 and later of SQL Anywhere automatically create a separate unique index for every PRIMARY KEY and UNIQUE column or table constraint that you define, as well as a separate non-unique index for every FOREIGN KEY constraint. There is no reason to explicitly create indexes on the same columns, and such indexes are redundant.

However, versions 5 and 6 of SQL Anywhere create a combined index for each PRIMARY KEY or UNIQUE constraint; this index "also contains the entries for all foreign keys that reference this table, whether those foreign keys appear in the same table or in a different one" (from the ASA 6 User's Guide, Chapter 25, The effect of column order in a composite index). These combined indexes can be much larger than an ordinary index on the primary key or unique constraint columns, and in those cases an explicitly created unique index on the same columns may improve performance. Such indexes are no longer needed in versions 7 and later.

The following discussion is written in terms of SQL Anywhere Version 9; i.e., separate indexes are automatically created for all primary keys, unique constraints and foreign keys.

Each list of two or more indexes is sorted by "relative importance" to help you choose which ones to keep: primary key first, then foreign key, UNIQUE constraint, UNIQUE index and finally non-unique index.

Each pair of multiple indexes should be considered separately, as follows:

  • Primary key and unique constraint on the same columns: The unique constraint is redundant and should be dropped; a primary key acts as a unique constraint and is supported by a unique index. If the unique constraint is clustered, make the primary key clustered.

  • Primary key and unique index on the same columns: The unique index is redundant and should be dropped. If the unique index is clustered, make the primary key clustered.

  • Primary key and non-unique index on the same columns: The non-unique index is redundant and should be dropped. If the non-unique index is clustered, make the primary key clustered.

  • Primary key and foreign key on the same columns: Determine why this table has the same columns in the primary key as in the parent table's primary key or unique constraint that is the target of the foreign key; there may be a design error. Otherwise, if the primary key and foreign key are both required, there's nothing that can be done about the fact the foreign key index is redundant from a performance point of view.

  • Two unique constraints on the same columns: One unique constraint is redundant and should be dropped. If one of the unique constraints is clustered, drop the other one.

  • Unique constraint and unique index on the same columns: The unique index is redundant and should be dropped; each unique constraint is supported by a unique index. If the unique index is clustered, make the unique constraint clustered.

  • Unique constraint and non-unique index on the same columns: The non-unique index is redundant and should be dropped. If the non-unique index is clustered, make the unique constraint clustered.

  • Unique constraint and foreign key on the same columns: Determine why this table has the same columns in the candidate key (unique constraint) as in the parent table's primary key or unique constraint that is the target of the foreign key; there may be a design error. Otherwise, if the unique constraint and foreign key are both required, there's nothing that can be done about the fact the foreign key index is redundant from a performance point of view.

  • Two unique indexes on the same columns: One unique index is redundant and should be dropped. If one of the unique indexes is clustered, drop the other one.

  • Unique index and non-unique index on the same columns: The non-unique index is redundant and should be dropped. If the non-unique index is clustered, make the unique index clustered.

  • Unique index and foreign key on the same columns: Determine why this table has the same columns in the unique index as in the parent table's primary key or unique constraint that is the target of the foreign key; there may be a design error. Otherwise, if the unique index and foreign key are both required, there's nothing that can be done about the fact the foreign key index is redundant from a performance point of view.

  • Two non-unique indexes on the same columns: One non-unique index is redundant and should be dropped. If one of the non-unique indexes is clustered, drop the other one.

  • Non-unique index and foreign key on the same columns: The non-unique index is redundant and should be dropped. If the non-unique index is clustered, make the foreign key clustered.

  • Two foreign keys on the same columns: If the same primary key or unique constraint in the same parent table is the target for both foreign keys, one of the foreign keys is redundant and should be dropped. Otherwise, determine why two different foreign key constraints on the same column are required; there may be a design error. If both foreign keys are required, there's nothing that can be done about the fact one of them is redundant from a performance point of view.

[ Top ]
Message: The table ... has no primary key or unique constraint, but does have a unique index.

Explanation: Without a primary key or unique constraint, some operations may be slow.

Four different flavors of this message may be produced, flagged as Note, Warning, Caution and Danger:

Note: The table ... has no primary key or unique constraint, but does have a unique index.
This table currently has fewer than 1,000 rows so there may be no performance problems, but if the table grows larger those operations may become extremely slow.
Warning: The table ... has no primary key or unique constraint, but does have a unique index.
This table currently has more than 1,000 rows; performance may not be a problem now but if the table grows larger those operations may become extremely slow.
Caution: The table ... has no primary key or unique constraint, but does have a unique index.
This table has more than 100,000 rows so there is a very real chance those operations will be extremely slow.
Danger: The table ... has no primary key or unique constraint, but does have a unique index.
This table has more than one million rows so there is a very real danger those operations will be extremely slow; think geological time scale :)

See also...
The table ... has no primary key, unique constraint or unique index.


[ Top ]
Message: The table ... has no primary key, unique constraint or unique index.

Explanation: Because there is no way to uniquely identify each row in this table, queries and database recovery operations may be slow.

Four different flavors of this message may be produced, flagged as Note, Warning, Caution and Danger:

Note: The table ... has no primary key, unique constraint or unique index.
This table currently has fewer than 1,000 rows so there may be no performance problems, but if the table grows larger those operations may become extremely slow.
Warning: The table ... has no primary key, unique constraint or unique index.
This table currently has more than 1,000 rows; performance may not be a problem now but if the table grows larger those operations may become extremely slow.
Caution: The table ... has no primary key, unique constraint or unique index.
This table has more than 100,000 rows so there is a very real chance those operations will be extremely slow.
Danger: The table ... has no primary key, unique constraint or unique index.
This table has more than one million rows so there is a very real danger those operations will be extremely slow; think geological time scale :)

See also...
The table ... has no primary key or unique constraint, but does have a unique index.


[ Top ]
Message: The table or view ... was not found, probably because it has been recently dropped.

Explanation: The schema in the right frame is displayed using up-to-date information from the target database. This message is produced when you click on a table name in the left frame, and that table has been dropped since the left frame was displayed.


[ Top ]
Message: There are no user tables to display.

Explanation: This database only contains system tables. You can see the system tables by checking Include system tables on the main menu.


[ Top ]
Message: This monitor session has been stopped and the samples have been deleted.

Explanation: This database monitor session can no longer be displayed because it has been stopped and all the corresponding data has been deleted.

If you want to start monitoring this database again, open a new Foxhound menu and then use the Monitor Database button on the DSN or String tab of the Foxhound menu.


[ Top ]
Message: This view has no column definitions in SYSCOLUMN; it may contain a syntax error.

Explanation: This is an informational message only. This view may raise a syntax error if you use it in a SQL statement.


[ Top ]
Message: To help protect your security, Internet Explorer has restricted this file from showing active content that could access your computer.

Explanation: In Internet Explorer, go to Tools - Internet Options... - Advanced tab.

Then scroll down to Security options and check "Allow active content to run in files on My Computer".


[ Top ]
Message: Too many sampling sessions in progress. Stop one and try again.
Message: Foxhound supports 100 sessions
Message: The Foxhound Standard Edition supports 10 sessions

Explanation:

Try stopping one of the other sampling sessions; this one should then be able to start automatically.

The Foxhound Standard Edition supports 10 sampling sessions, and the Extended Edition supports up to 100 sessions.

If this message is displayed incorrectly, try stopping and restarting Foxhound. If this situation persists, please report the problem.

See also...
How do I upgrade Foxhound from one edition to another?
How do I report unexpected errors and exceptions?


[ Top ]
Message: Unable to read ... rroad5 ...
Message: Info: Unable to execute ... rroad5 ...
Message: Info: Unable to read ... rroad5 ...
Message: Unable to execute ... rroad5 ...

Explanation:

The rroad5_sa17_bin64.dll and/or rroad5_sa17_bin32.dll files may be missing from the Foxhound installation folder, or their Windows permissions may be set to prevent them from being loaded.

The message "Unable to read ... rroad5_sa17_bin64.dll" and/or "Unable to read ... rroad5_sa17_bin32.dll" will appear if Foxhound is unable to read the file.

The messages "Unabl to execute ... rroad5_sa17_bin64.dll" and/or "Unable to execute ... rroad5_sa17_bin32.dll" will appear if Foxhound is unable to call a procedure inside the file.

Try reinstalling Foxhound.

Here is where the files are installed by default on Windows 10:

C:\ProgramData\RisingRoad\Foxhound5

If you have created a custom installation for Foxhound here's what you can try:

  • First, make sure that rroad5_sa17_bin64.dll and rroad5_sa17_bin32.dll are located in the same folder as the Foxhound database foxhound5.db.
  • Second, stop and restart the Foxhound database to ensure the file can be loaded.
  • Finally, use the DSN tab on the Foxhound main menu to connect to a database without getting the "Unable to..." message.

These files contain the very small but critical portion of Foxhound logic that had to be written in C.

See also...
How do I reinstall Foxhound?
How do I report unexpected errors and exceptions?


[ Top ]
Message: Unable to stop database server -- Database server not found.
Message: 9: ERRORLEVEL from dbstop: Unable to stop database server -- Database server not found.
Message: ERRORLEVEL = 9 from dbstop: Unable to stop database server -- Database server not found.

Explanation: The dbstop.exe utility was unable to stop the Foxhound database because it couldn't connect to the database. This usually means Foxhound wasn't running in the first place, and in that case this message can be safely ignored.

See also...
How do I figure out what went wrong during an installation?


[ Top ]
Message: Unable to stop database server -- Request to start/stop database denied.
Message: 1: ERRORLEVEL from dbstop: Unable to stop database server -- Request to start/stop database denied.
Message: ERRORLEVEL = 1 from dbstop: Unable to stop database server -- Request to start/stop database denied.

Explanation: The dbstop.exe utility was unable to stop the Foxhound database, possibly because it was originally started via the network server dbsrv17.exe without -gk all being specified on the command line.

See also...
How do I figure out what went wrong during an installation?
Can't open Message window log file: foxhound5_debug.txt
Invalid database server command line


[ Top ]
Message: Unacceptable SQL Anywhere server edition: The database engine is stopping.
Message: 015a-a1d: Unacceptable SQL Anywhere server edition: The database engine is stopping.

Explanation: This message may be produced when upgrading a Foxhound Version 3 database during the installation of Foxhound 4 or later:

*** ERROR ********************************************************
DIAG yyyy-mm-dd hh:nn:ss.sss The data upgrade process failed with this exception
 at location 015a-a1d: Unacceptable SQL Anywhere server edition: The database en
gine is stopping.
******************************************************************
*** For more information, see...

Do not use an OEM or authenticated edition of SQL Anywhere to install the new version of Foxhound when a Foxhound 3 database is going to be upgraded.

Follow these steps to try again:

  • Run Windows start - Foxhound5 - 10 Unsetup Foxhound to remove the Foxhound 4 shortcuts and other components.

  • Delete the folder C:\ProgramData\RisingRoad\Foxhound5 to remove the remaining Foxhound 5 files.

  • Install a non-OEM non-authenticated edition of SQL Anywhere.

  • Reinstall Foxhound 5


[ Top ]
Message: Unexpected exception from SET TEMPORARY OPTION DEDICATED_TASK = ... ignored: ...

Explanation:

Foxhound has attempted to set the DEDICATED_TASK option for the Monitor connection to the target database, and it returned this exception.

This symptom is not regarded serious enough to stop the Monitor from gathering samples; see How do I report unexpected errors and exceptions?

See also...
How do I see Foxhound diagnostics, errors and exceptions?


[ Top ]
Message: Unexpected operation: "..."

Explanation:

Please report this error; see How do I report unexpected errors and exceptions?

See also...
How do I see Foxhound diagnostics, errors and exceptions?


[ Top ]
Message: Unexpected situation. Extended Edition already activated.
Message: Extended Edition already activated ... Unexpected situation

Explanation:

This message was produced by the Foxhound Activation page.

Please contact Breck.Carter@gmail.com


[ Top ]
Message: Unexpected situation. Please report this error.
Message: Please report this error ... Unexpected situation

Explanation:

This message was produced by the Foxhound Activation page.

Please contact Breck.Carter@gmail.com


[ Top ]
Message: User-defined exception signaled
Message: 990xx: Internal error
Message: Internal error 999xx
Message: SQL error: User-defined exception signaled

Explanation:

If you see "SQL error: User-defined exception signaled" displayed instead of the Foxhound page you expect, try using the Foxhound Options - Diagnostics - Display Diagnostics button to see if there are any diagnostic messages associated with this problem.

You may see one or more messages like this:

342 2012-11-14 17:21:26.237 Full Build 4215a 1559 210a-a7(210eh1) SQLCODE = -297, SQLSTATE = 99010, ERRORMSG() = Internal error 99010
343 2012-11-14 17:21:26.238 Full Build 4215a 1559 210a-d1b(210eh1) SQLCODE = -297, SQLSTATE = 99010, ERRORMSG() = Internal error 99010

The following "Internal error" values may indicate that the Monitor Options settings have been deleted or become corrupted for a sampling session. In this case the workaround is to stop sampling, delete the affected sampling session, and then restart sampling for that target database.

99001 99002 99003 99004 99005 99006 99007 99008 99009 99010 
99011 99012 99013 99014 99015 99016 99017 99018 99019 99020 
99021 99022 99023 99024 99025 99026 99027 99028 99029 99030 
99031 99032 99033 99034 99035 99036 99037 99038 99039 99040 
99041 99042 99043 99044 99045 99046 99047 99048 99049 99050 
99051 99052 99053 99054 99055 99056 99057 99058 99059 99060 
99061 99062 99063 99064 99065 99066 99067 99068 99069 99070 
99071

In particular, the message "Internal error 99064" may indicate that the sampling session currently displayed on the Monitor Options page has been deleted, perhaps when the Delete Multiple Monitor Sessions. In that case, Foxhound mistakenly tries (and fails) to display the deleted set of Monitor Options instead of switching to the "Default Settings". The default workaround is to close the failing Monitor Options page, and open it again for a different sampling session, or for the "Default Settings" which is never deleted.

Please report this error; see How do I report unexpected errors and exceptions?

See also...
How do I see Foxhound diagnostics, errors and exceptions?
How do I run adhoc queries on the Foxhound database?
How do I see the schema for adhoc reporting?


[ Top ]
Message: Value '...' out of range for destination

Explanation:

This is an unexpected error, possibly caused by a problem with the performance statistics received from the target database server.

Please report this error; see How do I report unexpected errors and exceptions?

See also...
How do I see Foxhound diagnostics, errors and exceptions?


[ Top ]
Message: Wrong length data in patch file "..."

Explanation: The patch file may have been corrupted.

Try replacing the patch file and starting Foxhound again, then report this error; see How do I report unexpected errors and exceptions?


This page was last generated on July 17, 2020. Foxhound 5.0 FAQ Home      Foxhound Home      RisingRoad      Breck.Carter@gmail.com