User manual

131
Error messages on the History tab
• “Modem reported modem error”: Note whether the RD and SD lights on the modem are
locked on. This may be a bug that showed up in PhoneSweep 1.1. Contact Sandstorm Enterprises
to report the bug. Sandstorm has a patch, which may fix this bug.
• “Problem with localwrite”: This means that PhoneSweep failed in its attempts to communicate
with a modem after a call had already begun. Check the connectors on the cables to your modems
to see that they are firmly seated.
User interface error messages
• “Can’t run help system. Is hh.exe in the path? You can install it from hhupd.exe on the
PhoneSweep CD”: There is an error in the Windows HTML help system. Reinstall it by running
hhupd.exe in the top-level PhoneSweep directory.
• “SHLWAPI.dll could not be found”: Install Internet Explorer 4.01 or higher.
The debug.bat File and Advanced Debugging
This interface is intended for advanced users familiar with TCP/IP and SQL. If you do not have this
expertise, don’t worry about running the tests in this section. If you have read carefully through the
previous sections of the troubleshooting guide and have not solved your problem, please feel free to
contact Sandstorm Technical Support by emailing [e-mail].
Running the file debug.bat presents you with a list of tests that you can perform to help diagnose
problems with PhoneSweep. You can run this file by selecting Troubleshooting Utility from the Start /
Programs / PhoneSweep menu. Debug.bat is in the top-level PhoneSweep directory and can execute the
following tests:
• Initiate a TCP/IP ping of localhost, to see if the local protocol stack is available. PhoneSweep
uses TCP/IP to communicate among the engine, database and UI.
• Start up the embedded SQL database separately from the PhoneSweep engine and UI, to test its
behavior or to determine the precise error message from a failure.
• Start the PhoneSweep engine separately from the graphical user interface.
• Start the PhoneSweep UI separately from the engine and database.
• Check the status of an already-running copy of the SQL database.
• Log into the SQL database as administrator. This permits SQL queries directly to the database.
This is intended for advanced users familiar with SQL.
• List all preference variables that have been set in the “default” profile directly from the SQL
database.
• Run the dongle diagnostics program.
• Run the database fix program (DBFIX). This can repair a corrupt profile.