Messages

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?

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

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

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 4.0
...
*** Checking for an old Foxhound4 database...
*** Moving the new Foxhound database file...
******************************************************************
*** ERROR ********************************************************
*** The $post_setup.bat file could not MOVE the new
*** foxhound4.db file to the FOXHOUND4 folder.
*** See...
***  C:\ProgramData\RisingRoad\Foxhound4\\setup\post_setup_trace.txt
*** Contact Breck.Carter@gmail.com
******************************************************************
Press any key to continue . . .

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

Mon 08/22/2016  6:28:11.27 Foxhound 4.0.4682 *** Moving the new Foxhound4 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 - Foxhound4 - Tools - Unsetup Foxhound 
   

2. Delete the Foxhound folder...

   C:\ProgramData\RisingRoad\Foxhound4
   

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 - Foxhound4 - Tools - Unsetup Foxhound 
   

2. Delete the Foxhound folder...

   C:\ProgramData\RisingRoad\Foxhound4
   

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 7 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 4.0
*** Checking for a post-setup path parameter...
Access is denied.
Access is denied.
*** A post-setup path parameter was provided...
C:\ProgramData\RisingRoad\Foxhound4\
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 4.0.4673
***
*** Here's where Foxhound is being installed:
*** C:\ProgramData\RisingRoad\Foxhound4\
***
Access is denied.
*** Starting the Foxhound 4.0.4673 post-setup process...
Access is denied.
Access is denied.
Access is denied.
*** Creating foxhound4.db.4.0.4673.ORIGINAL_COPY...
Access is denied.

C:\Windows\SysWOW64

Try installing Foxhound 4 again:

1. Run the Foxhound "unsetup" process...

   All Apps - Foxhound4 - Unsetup Foxhound
   

2. Use right mouse - Run as Administrator to run the Foxhound 4 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:

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

• Here is an example of this and other related error messages produced by the post setup process when the Foxhound engine is running as a service:

  ... *** Starting the existing Foxhound database... 19/07/2010 15:20:03.26 Foxhound 1.3736 *** ERRORLEVEL = 1 *** ...no, the existing Foxhound database did NOT start. *** ERRORLEVEL = 1 07/19 15:20:02. Cannot access "C:\Documents and Settings\All Users\Application D ata\RisingRoad\Foxhound4\foxhound4.db": another process may be using the file ... *** Moving the old Foxhound database files... A subdirectory or file backup already exists. A subdirectory or file previous_build already exists. The process cannot access the file because it is being used by another process. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the old *** foxhound4.db file to the "previous_build" subfolder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . The process cannot access the file because it is being used by another process. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the old *** foxhound4.log file to the "previous_build" subfolder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . *** Moving the new Foxhound database files... Access is denied. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the new *** foxhound4.db file to the FOXHOUND4 folder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . Access is denied. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the new *** foxhound4.log file to the FOXHOUND4 folder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . *** Deleting the temporary setup files... *** Wrapping up... ****************************************************************** *** ERROR ******************************************************** dbspawn old_foxhound4 ERRORLEVEL = 1 ...

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

   C:\ProgramData\RisingRoad\Foxhound4>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 dbsrv16.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?

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 ...

Explanation: This alert may not have anything to do with High Availability. Foxhound uses any runtime change in the server name to trigger this alert, and that can happen if you manually stop and restart the target database with a different server name.

If you are not using HA, you can disable Alert #11 to avoid this message.

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 ...

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?

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

If you forget, you will see this error when you run the Foxhound setup; this is a limitation of the way the InstallShield setup for Foxhound is constructed:

There are three ways to run the Foxhound unsetup process:

• Click on start - All Programs - Foxhound4 - Tools - Unsetup Foxhound, or

• use the Control Panel - Add or Remove Programs dialog to remove Foxhound Version 4, or

• run this command: MsiExec.exe /X{08A52B52-C7AF-424B-9A9E-4A010F0D304A}

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

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?

Explanation: When a new build of Foxhound is installed, the data upgrade portion of the post-setup process fails with the message "Authentication failed".

Foxhound is not licensed to run using an "OEM" or "Authenticated" edition of SQL Anywhere.

Try installing a regular non-OEM edition of SQL Anywhere. Then rerun the upgrade, including the initial "unsetup" step: How do I install a new version of Foxhound?

Note: A fix for this problem will be delivered in the next Generally Available build of Foxhound.

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

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 ...

Explanation: Try removing any new line (CR/LF) or other special characters from the file specification.

Also, the FOXHOUND4 environment variable may not be set yet properly; see How do I get the new value of the FOXHOUND4 environment variable to show up after Foxhound is installed?

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?

Here is an example of this and other related error messages produced by the post setup process when the Foxhound engine is running as a service:

... *** Starting the existing Foxhound database... 19/07/2010 15:20:03.26 Foxhound 1.3736 *** ERRORLEVEL = 1 *** ...no, the existing Foxhound database did NOT start. *** ERRORLEVEL = 1 07/19 15:20:02. Cannot access "C:\Documents and Settings\All Users\Application D ata\RisingRoad\Foxhound4\foxhound4.db": another process may be using the file ... *** Moving the old Foxhound database files... A subdirectory or file backup already exists. A subdirectory or file previous_build already exists. The process cannot access the file because it is being used by another process. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the old *** foxhound4.db file to the "previous_build" subfolder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . The process cannot access the file because it is being used by another process. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the old *** foxhound4.log file to the "previous_build" subfolder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . *** Moving the new Foxhound database files... Access is denied. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the new *** foxhound4.db file to the FOXHOUND4 folder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . Access is denied. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the new *** foxhound4.log file to the FOXHOUND4 folder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . *** Deleting the temporary setup files... *** Wrapping up... ****************************************************************** *** ERROR ******************************************************** dbspawn old_foxhound4 ERRORLEVEL = 1

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

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?

Explanation: If the full message looks like one of these:

Cannot open transaction log file -- Can't use log file "foxhound.log" since the database file has been used more recently

Cannot open transaction log file -- Can't use log file "foxhound.log" since the offsets don't match the offsets in the database file

All Programs - Foxhound4 - Tools - Start Foxhound via default browser - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Chrome - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Firefox - debug

All Programs - Foxhound4 - Tools - Start Foxhound via IE - debug

Explanation:

C:\ProgramData\RisingRoad\Foxhound4>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: foxhound4_debug.txt Press any key to continue . . .

If you're trying to run Foxhound 4 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 - Foxhound4 Right mouse on Start Foxhound Engine Click More - Open File Location See this folder appear: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Foxhound4\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 Foxhound4 - Tools - Start Foxhound Engine shortcut when the Foxhound database was already running.

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

With some of the shortcuts, like Foxhound4 - 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 following "debug" shortcuts to stop and restart the Foxhound engine, try running it again. The previous dbsrv16.exe process may not have had enough time to release the foxhound4_debug.txt file before a new dbsrv16.exe process tried to open that file:

All Programs - Foxhound4 - Tools - Start Foxhound via default browser - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Chrome - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Firefox - debug

All Programs - Foxhound4 - Tools - Start Foxhound via IE - debug

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.

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

Explanation: This is an unexpected message.

Please contact Breck.Carter@gmail.com.

Explanation: This is an unexpected message.

Please contact Breck.Carter@gmail.com.

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.

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.

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.

Explanation: Try applying Patch 3 to Foxhound 4 build 4729, or upgrading to Foxhound 4 build 4739 or later, to get this bug fix:

Fix "unable to load dll" messages: Could not load dynamic library Unable to load either rroad4.dll or rroad464.dll Unable to read rroad4.dll Unable to read rroad464.dll (1) This fix delivers 4 new *.dll files and replaces 10 *.bat files in the Foxhound 4 folder. These files fix a problem where Foxhound does not start when it is installed on a computer with SQL Anywhere 17 installed but not SQL Anywhere 16. Symptoms include the following error messages: The program can't start because dblib16.dll is missing Unable to load either rroad4.dll or rroad464.dll The fix requires that all *.bat files which start the Foxhound 4 database using dbsrv16.exe or dbsrv17.exe must include code that replaces the rroad4.dll and rroad464.dll with files that support whichever version of SQL Anywhere is going to be used: 16 or 17. The fix consists of these lines added to the *.bat files: REM Code from patch-4729-003-DLLs-Properties... IF /I "%SPGM%z%BIN%z"=="dbsrv16.exezBin32z" (COPY rroad4_sa16_bin32.dll rroad4.dll) IF /I "%SPGM%z%BIN%z"=="dbsrv16.exezBin64z" (COPY rroad4_sa16_bin64.dll rroad464.dll) IF /I "%SPGM%z%BIN%z"=="dbsrv17.exezBin32z" (COPY rroad4_sa17_bin32.dll rroad4.dll) IF /I "%SPGM%z%BIN%z"=="dbsrv17.exezBin64z" (COPY rroad4_sa17_bin64.dll rroad464.dll) Those lines are added to the following *.bat files: $backup_foxhound4.bat $start_foxhound4_chrome.bat $start_foxhound4_chrome_debug.bat $start_foxhound4_default_browser.bat $start_foxhound4_default_browser_debug.bat $start_foxhound4_engine.bat $start_foxhound4_firefox.bat $start_foxhound4_firefox_debug.bat $start_foxhound4_ie.bat $start_foxhound4_ie_debug.bat

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

The messages "Unable to read rroad4.dll" and/or "Unable to read rroad464.dll" will appear if Foxhound is unable to read the files via xp_read_file.

The message "Unable to load either rroad4.dll or rroad464.dll" will appear when Foxhound is unable to CALL a function in either file. This message is accompanied by diagnostic data which is also written to the rroad_exception table; see How do I report unexpected errors and exceptions?

Try reinstalling Foxhound.

Here is where rroad4.dll and rroad464.dll are installed by default on Windows 7:

C:\ProgramData\RisingRoad\Foxhound4

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

• First, make sure that rroad4.dll and rroad464.dll are located in the same folder as the Foxhound database foxhound4.db.
• Second, stop and restart the Foxhound database to ensure that rroad4.dll or rroad464.dll can be loaded.
• Finally, use the DSN tab on the Foxhound main menu to connect to a database without getting the "Could not load dynamic library..." message.

The rroad4.dll and rroad464.dll files contain the very small but critical portion of Foxhound logic that had to be written in C.

Outside the context of Foxhound, the message "Could not load dynamic library" can appear when SQL code running on a 32-bit SQL Anywhere server tries to load a CREATE EXTERNAL procedure located in a 64-bit DLL, or vice versa. Foxhound should not have this particular problem because both 32-bit and 64-bit versions of the DLL rroad4.dll and rroad464.dll are provided, and Foxhound loads whichever one corresponds to the SQL Anywhere server being used to run Foxhound.

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

Explanation: There are two or more sampling sessions with the same target database, possibly because there are two or more different ODBC DSNs or connection strings that point to the same target database.

When you upgrade Foxhound to a new build, each sampling session tries to update the three Foxhound properties procedures on its target database, and only one attempt will work for each target.

You will see three or more error messages along with the three successful "Info:" exceptions:

2010-06-25 04:32:58.531 Full Build 3706a 1000000006 701.a3(701eh2) CREATE PROCEDURE rroad_engine_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p002': [Sybase][ODBC Driver][SQL Anywhere]Item 'rroad_engine_properties' already exists 2010-06-25 04:32:58.531 Full Build 3706a 1000000005 204.d1b(204eh-b6) Info: Procedure rroad_engine_properties has been upgraded from build number 3705 to 3706 on aaa3 ddd11 dba sql 2010-06-25 04:37:21.437 Full Build 3706a 1000000026 702.a3(702eh2) CREATE PROCEDURE rroad_database_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p001': [Sybase][ODBC Driver][SQL Anywhere]Item 'rroad_database_properties' already exists 2010-06-25 04:37:21.437 Full Build 3706a 1000000027 204.d6b(204eh-b9) Info: Procedure rroad_database_properties has been upgraded from build number 3705 to 3706 on sales 2010-06-25 04:37:21.687 Full Build 3706a 1000000027 204.e2b(204eh-c3) Info: Procedure rroad_connection_properties has been upgraded from build number 3705 to 3706 on sales 2010-06-25 04:37:21.703 Full Build 3706a 1000000026 700.a3(700eh2) CREATE PROCEDURE rroad_connection_properties failed. SQLSTATE = WO005, ERRORMSG() = Server 'p001': [Sybase][ODBC Driver][SQL Anywhere]Item 'rroad_connection_properties' already exists

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

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?

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\Foxhound4\
***
*** You may launch Foxhound with this shortcut:
***   Start
***     - All Programs
***       - Foxhound4
***         - Start Foxhound via default browser
***
*** 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\Foxhound4\\setup\post_setup_trace.txt
***  C:\ProgramData\RisingRoad\Foxhound4\\setup\databasestart_diagnostic.txt
***  C:\ProgramData\RisingRoad\Foxhound4\\setup\old_foxhound1_debug.txt
***  C:\ProgramData\RisingRoad\Foxhound4\\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?

Explanation: When installing a new version of Foxhound, the data from an existing beta copy of the Foxhound database 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.

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.

Explanation:

• If you are connecting via the String tab and you have not specified a DSN, make sure to specify a DRIVER.

• If you are connecting via the String tab and there is a space ahead of the DRIVER parameter, try removing it. Certain versions of SQL Anywhere have a problem with that.

• If you are connecting via the String tab and you have specified a DSN, make sure it exists.

• If you are using the 64-bit version of SQL Anywhere to run Foxhound, check to see if the ODBC DSN for the target database only works with the 32-bit version of SQL Anywhere, or vice versa.

  Also check for the message "The specified DSN contains an architecture mismatch between the Driver and Application".

Explanation:

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

Explanation: Here are some possibilities:

• A local target server was specified, and that server is not running.
  
  
• If Foxhound has been started as a service, you may have to specify a LINKS parameter to connect to a target database even if it has been started on the same computer: ENG=ddd16; DBN=ddd16; UID=dba; PWD=sql; DRIVER=SQL Anywhere 16; LINKS=TCPIP(HOST=localhost; PORT=2638; DoBroadcast=NONE);
  
  
• A HOST= network server address was specified, and that server is not running.
  
  
• The correct HOST= network server address was specified on the Network tab, but the ENG= server name is wrong.
  
  
• The wrong HOST= network server address was specified on the Network tab.
  
  
• Caution: If you change the HOST= value, you may connect to the wrong server if a different, but working, IP address was cached in the workstation file C:\Program Files\Sybase\SQL Anywhere 9\win32\asasrv.ini. To avoid using this cache file specify "DOBROADCAST=NONE" on the Network tab; e.g.: use HOST=ip-address;DOBROADCAST=NONE to force only that address to be used.

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

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

All Programs - Foxhound4 - Tools - Start Foxhound via default browser - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Chrome - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Firefox - debug

All Programs - Foxhound4 - Tools - Start Foxhound via IE - debug

• Unable to stop database server -- Request to start/stop database denied.

• Invalid database server command line

• Can't open Message window log file: foxhound4_debug.txt

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

If the "dbspawn/dbsrv16 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" shortcuts used to start the Foxhound engine:

All Programs - Foxhound4 - Tools - Start Foxhound via default browser - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Chrome - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Firefox - debug

All Programs - Foxhound4 - Tools - Start Foxhound via IE - debug

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

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

All Programs - Foxhound4 - Tools - Start Foxhound via default browser - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Chrome - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Firefox - debug

All Programs - Foxhound4 - Tools - Start Foxhound via IE - debug

Look for another error message, such as:

• Unable to stop database server -- Request to start/stop database denied.

• Invalid database server command line

• Can't open Message window log file: foxhound4_debug.txt

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

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

All Programs - Foxhound4 - Tools - Start Foxhound via default browser - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Chrome - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Firefox - debug

All Programs - Foxhound4 - Tools - Start Foxhound via IE - debug

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

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?

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.

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?

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.

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

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.

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?

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?

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?

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';

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

Explanation: Foxhound is not allowed to call the sa_server_option() procedure on the target database.

See the Connecting to Target Databases section of the Help.

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?

Explanation: Foxhound is not licensed to run using an "OEM" or "Authenticated" edition of SQL Anywhere.

Foxhound can connect to and monitor a target database running on an OEM or Authenticated edition of SQL Anywhere, but Foxhound itself requires a non-authenticated edition to run.

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"

Explanation: Sampling stopped because the Foxhound engine was not running.

When Foxhound is restarted it will automatically try to reconnect to the target database and start sampling again.

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.

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" (foxhound4.db) at Sun Oct 03 2010 14:12 I. 10/03 14:12:38. Finished checkpoint of "f" (foxhound4.db) at Sun Oct 03 2010 14:12 I. 10/03 14:12:40. Database server stopped at Sun Oct 03 2010 14:12

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\Foxhound4\foxhound4.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\Foxhound4\foxhound4.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 --

*** 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?

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.

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"

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?

Explanation:

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

Explanation:

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

Explanation:

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

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.
running for that sampling id. [4-Foxhound_on_old_Dell_XP]

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?

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.

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

All Programs - Foxhound4 - Tools - Start Foxhound via default browser - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Chrome - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Firefox - debug

All Programs - Foxhound4 - Tools - Start Foxhound via IE - debug

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

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.

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.

Explanation: If you see this message when you are reloading your target database after unloading it, just press Continue to ignore it and proceed:

You may see three consecutive messages; press Continue to ignore each one:

Could not execute statement. Item 'rroad_engine_properties' already exists SQLCODE=-110, ODBC 3 State="42S01" Line 4643, column 1 You can continue executing or stop. Could not execute statement. Item 'rroad_database_properties' already exists SQLCODE=-110, ODBC 3 State="42S01" Line 4774, column 1 You can continue executing or stop. Could not execute statement. Item 'rroad_connection_properties' already exists SQLCODE=-110, ODBC 3 State="42S01" Line 4880, column 1 You can continue executing or stop.

Here's what might have happened:

• The Foxhound Monitor was set up to gather samples from your target database.

• You decided to unload, recreate and reload that database.

• When you unloaded the database, the reload.sql file included CREATE PROCEDURE statements for the three procedures named in the error messages above.

• When you started the new database, but before you had a chance to run the reload.sql file, the Foxhound Monitor connected to the new (empty) database.

• The Foxhound Monitor then immediately ran its own CREATE PROCEDURE statements for those three procedures. See Help - Introduction - Connecting to Target Databases for more information about this process.

• When you ran the the reload, it could not execute the CREATE PROCEDURE statements in the reload.sql file because those procedures already existed.

• Since they are already there, just press Continue to ignore the messages...

• ...or, edit the reload.sql file to remove the three CREATE PROCEDURE statements.

See also...
Help - Introduction - Connecting to Target Databases

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.

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.

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.

Explanation: This is a normal message.

Either no patch*.* files exist the Foxhound folder, or the ones that do exist have been detected by previous Foxhound runs.

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.

Explanation:

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

Long answer...

The SQL Anywhere server name must be set to "foxhound4" 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 foxhound4" 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 "foxhound4" 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 "foxhound4", 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?

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.

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?

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

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.

Explanation: If the target database is a SQL Anywhere High Availability arbiter server, Foxhound can only perform ping-only sampling because there is no actual database on the target server.

In this case, try checking the "Run the Foxhound Ping process without gathering any other sample data" option on the Monitor Options - 16. Ping Settings - Perform Ping-Only Sampling section for the arbiter target.

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.

Explanation: 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 because there are three procedures pushed to each target database "xxx":

   2012-10-21 10:34:52.193 Full Build 4209a 1000000205 204.d1b(204eh-b6) Info: Procedure rroad_engine_properties has been upgraded from build number 4206 to 4209 on ddd12 [1-ddd12]
   2012-10-21 10:34:52.250 Full Build 4209a 1000000205 204.d6b(204eh-b9) Info: Procedure rroad_database_properties has been upgraded from build number 4206 to 4209 on ddd12 [1-ddd12]
   2012-10-21 10:34:52.457 Full Build 4209a 1000000205 204.e2b(204eh-c3) Info: Procedure rroad_connection_properties has been upgraded from build number 4206 to 4209 on ddd12 [1-ddd12]
   

Explanation: A newer version of the Foxhound Monitor was previously used on this target database.

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;

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.

Explanation:

Messages like these may appear in the Foxhound diagnostic text file foxhound4_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.

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:

$backup_foxhound4.bat $start_foxhound4_chrome.bat $start_foxhound4_chrome_debug.bat $start_foxhound4_default_browser.bat $start_foxhound4_default_browser_debug.bat $start_foxhound4_engine.bat $start_foxhound4_firefox.bat $start_foxhound4_firefox_debug.bat $start_foxhound4_ie.bat $start_foxhound4_ie_debug.bat By default, those command files are installed here on Windows 7: C:\ProgramData\RisingRoad\Foxhound4

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

-xs http(port=80;maxsize=0;to=600;kto=600)^

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.

Explanation: Samples were not recorded because you clicked Stop Sampling.

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 foxhound4.db and foxhound4.log files from the C:\ProgramData\RisingRoad\Foxhound4\backup\previous_build folder to the C:\ProgramData\RisingRoad\Foxhound4 folder, and

• run the Foxhound Installshield setup again.

Explanation: This error message may appear in two locations. It may be displayed on the Monitor page:

EMAIL FAILURE - SMTP send Alert email failed with return code 5 when sending "03:34 - ALERT #1 - Database unresponsive - benchmark_test_on_BRECK-PC"

2 2010-03-10 03:34:38.484 Full Build 3642a 1000000083 223b9(223eh3) Info: SMTP send Alert email failed with return code 5 when sending "03:34 - ALERT #1 - Database unresponsive - benchmark_test_on_BRECK-PC"

0 Success 2 xp_startsmtp failed. 3 xp_stopsmtp failed. 5 xp_sendmail failed. 12 Attachment not found. 15 Insufficient memory. 20 Unknown recipient. 25 Mail session failed to start. 100 Socket error. Antivirus software may have blocked the outbound connection to the SMTP server. Check the "SMTP Server:" field. 101 Socket timeout. 102 Unable to resolve the SMTP server hostname. 103 Unable to connect to the SMTP server. 104 Server error; response not understood. Check the "SMTP Server:" field. 105 A TLS error occurred. Check the "SMTP Authorization User Name:", "SMTP Authorization Password:" and "SMTP Certificate Filespec:" fields. 421 Domain service not available, closing transmission channel. 450 Requested mail action not taken: mailbox unavailable. 451 Requested action not taken: local error in processing. Message may have been rejected as spam. 452 Requested action not taken: insufficient system storage. 500 Syntax error, command unrecognized. (This may include errors such as a command that is too long). 501 Syntax error in parameters or arguments. 502 Command not implemented. 503 Bad sequence of commands. 504 Command parameter not implemented. 511 Bad email address. 550 Requested action not taken: mailbox unavailable. For example, the mailbox is not found, there is no access, or no relay is allowed. 551 User not local; please try forward-path. 552 Request mail action aborted: exceeded storage allocation. 553 Requested action not taken: mailbox name not allowed. For example, the mailbox syntax is incorrect. 554 Transaction failed. The message may have been rejected as spam.

See also...
SMTP Error Codes & SMTP Status Codes & SMTP Reply Codes Reference 2010

Explanation: This is a contradictory and confusing error message that appears on the Monitor Options page:

• "235/2.7.0 Accepted" means that SMTP is working

• but "return code -1" means that an attempt to actually send a test email message failed.

The most likely reason is that the email address field is empty:

Fill in the Email address(es) for Alerts: field and click on Save before clicking on Send Test Alert Email on the Monitor Options page.

The same is true for the Send Test AutoDrop Email button:

Fill in the Email address(es) for AutoDrop Notices: field and click on Save before clicking on Send Test AutoDrop Email.

See also...
SMTP send ... email failed with return code ... when sending "..."

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.

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.

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 4 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.

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 4 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.

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 4 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.

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

For example:

SQL Anywhere version 16.0.0.2127 or later is required to run this application.
However, version 16.0.0.2052 is actually being used.
Please install version 16.0.0.2127 or later. See www.sap.com.  ...more help

Explanation: Foxhound requires SQL Anywhere 16 or 17 to run it's own database.

C:\ProgramData\RisingRoad\Foxhound4>ECHO OFF
Start Foxhound via Default Browser
******************************************************************
*** ERROR ********************************************************
*** SQLANY16 or SQLANY17 environment variable not set properly.
*** Install SQL Anywhere 16 or 17.
Press any key to continue . . .

The SQLANY16 and SQLANY17 environment variables are optional, but by default they are used by the delivered *.bat files. Either perform a standard installation of SQL Anywhere 16 and/or 17 to get SQLANY16 and/or SQLANY17 set up, or edit the *.bat files to replace references to %SQLANY16% and/or %SQLANY17%.

If you have recently installed SQL Anywhere 16 or 17, the SQLANY16 or 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 SQLANY16 or 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...

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

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?

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]

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

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

Explanation: The Foxhound engine stopped because you clicked on the Stop Foxhound Engine button.

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'

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.

Explanation: You may see the following error message if you are using the Task Scheduler on Windows Vista or Windows 7 to backup the Foxhound database using the technique described here: (see How do I backup my Foxhound database on a regular basis?

******************************************************************
*** ERROR ********************************************************
*** The $backup_foxhound4.bat file looked for a path specification
*** in the FOXHOUND4 environment variable and it was empty.
*** Try rebooting and running $backup_foxhound4.bat again,
*** then contact Breck.Carter@gmail.com
******************************************************************

Here's a workaround: Reboot the computer after installing a new version of Foxhound.

See also...
How do I backup my Foxhound database on a regular basis?
How do I install a new version of Foxhound?
How do I reinstall Foxhound?

Explanation:

Before running the All Programs - Foxhound4 - 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_foxhound4_log.bat file did not find an existing
*** full backup of the database and log files in the folder
*** C:\ProgramData\RisingRoad\Foxhound4\backup\generation3
*** Try running $backup_foxhound4.bat first,
*** then try running $backup_foxhound4_log.bat again,
*** then contact Breck.Carter@gmail.com
******************************************************************
Press any key to continue . . .

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?

Explanation:

Uninstall and remove this expired beta copy of Foxhound, and either install a new beta copy with a future expiry date, or a generally-available Rental, Basic or Extended copy.

Explanation: Start the Foxhound engine and try again.

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 7:

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

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

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 7:

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

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

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 7:

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

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

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.

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.

See also...
How do I stop and restart Foxhound?

Explanation: The Foxhound engine stopped because you clicked on the Stop Foxhound Engine button.

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.

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?

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?

Explanation: This is a normal message.

The patch file is about to be executed; no errors have been detected up to this point.

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?

Explanation: This is a normal message.

The patch file has been executed; no errors have been detected up to this point.

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?

Here is an example of this and other related error messages produced by the post setup process when the Foxhound engine is running as a service:

... *** Starting the existing Foxhound database... 19/07/2010 15:20:03.26 Foxhound 1.3736 *** ERRORLEVEL = 1 *** ...no, the existing Foxhound database did NOT start. *** ERRORLEVEL = 1 07/19 15:20:02. Cannot access "C:\Documents and Settings\All Users\Application D ata\RisingRoad\Foxhound4\foxhound4.db": another process may be using the file ... *** Moving the old Foxhound database files... A subdirectory or file backup already exists. A subdirectory or file previous_build already exists. The process cannot access the file because it is being used by another process. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the old *** foxhound4.db file to the "previous_build" subfolder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . The process cannot access the file because it is being used by another process. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the old *** foxhound4.log file to the "previous_build" subfolder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . *** Moving the new Foxhound database files... Access is denied. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the new *** foxhound4.db file to the FOXHOUND4 folder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . Access is denied. ****************************************************************** *** ERROR ******************************************************** *** The $post_setup.bat file could not MOVE the new *** foxhound4.log file to the FOXHOUND4 folder. *** Contact Breck.Carter@gmail.com ****************************************************************** Press any key to continue processing... Press any key to continue . . . *** Deleting the temporary setup files... *** Wrapping up... ****************************************************************** *** ERROR ******************************************************** dbspawn old_foxhound4 ERRORLEVEL = 1 ...

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

Explanation:

Try starting Foxhound with the 32-bit version of SQL Anywhere; see How do I start Foxhound with the 32-bit version of SQL Anywhere when both the 32-bit and 64-bit versions of SQL Anywhere are installed?

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

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

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

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

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.

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.

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.

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.

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

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.

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

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".

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?

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.

Here's a sample of this error message from the post_setup_trace.txt file:

Fri 12/31/2010  7:59:42.59 Foxhound 1.3806 *** dbstop 1 old_foxhound4 ERRORLEVEL = 9 
SQL Anywhere Stop Server Utility Version 11.0.1.2467
Unable to stop database server -- Database server not found.

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

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

This problem can affect the post-setup stage of a Foxhound installation, as well as the following Foxhound shortcuts:

All Programs - Foxhound4 - Tools - Start Foxhound via default browser - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Chrome - debug

All Programs - Foxhound4 - Tools - Start Foxhound via Firefox - debug

All Programs - Foxhound4 - Tools - Start Foxhound via IE - debug

All Programs - Foxhound4 - Tools - Stop Foxhound Engine

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

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?

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?

Explanation:

These messages appear in the Foxhound database engine console log when the Foxhound Monitor has given up waiting for a "connection failed" response to its attempt to connect to the target database:

Connection 1000002140 dropped by Foxhound because it failed to connect to target DSN RuralFinds_Bonnie after 16.1s (timeout threshold is 15.0s; see Foxhound Options) 
User "DBA" dropped event connection 1000002140 ("rroad_monitor_sample_loop")

Note that Foxhound does not give up trying to connect just because a connection failed, that's not what this kind of "timeout" is; for more information see Help - Foxhound Options - Connection Timeout.

To stop further attempts to restart start sampling for this target database after a timeout, click on Start Sampling, then Cancel Request.

To stop all further attempts to restart sampling after a time out, or to change how often the attempts are made, see Help - Foxhound Options - Timeout Retry.

It is also normal to see several messages like this when the Foxhound engine is forcibly stopped while it is sampling several target databases.

See also...
Help - Foxhound Options - Diagnostics
Help - Foxhound Options - Connection Timeout
Help - Foxhound Options - Timeout Retry

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?

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?