1. 7854-1 ERROR

Reason:

The Program executable is unable to locate the wchk32x.dll file in the program directory. This can happen when the network drive is not accessible. For example, if Prophesy is installed on the P: drive, but the P: drive is not connected or has been inactive for an extended period of time.

Solution:

Try reconnecting to the network drive that Prophesy resides on. Open up my computer, then locate the network drive Prophesy is installed on, and double click it. If the drive opens and you can see the contents, try re-opening the Prophesy program. If you are unable to connect to the network drive, try rebooting the workstation. If you are still unable to connect to the network drive, you should contact your in-house or local technician to resolve the issue.

2. ODBC Microsoft Access 97 driver login failed?

Symptom:

Upon launching the program, immediately a dialog titled 'ODBC Microsoft Access 97 driver login failed' comes up with the message "Unrecognized database format 'C:\\Program Files\\Prophesy\\Disp\\Data\\Prologp.mdb'."

Cause:

The Prologp.mdb file may have been converted to an Access 2000 database and is now being accessed from a machine that does not have the Jet 4.0 ODBC drivers installed.

Solution:

Install MDAC 2.1sp1 or later. For your convenience we currently ship MDAC 2.5 in the \\Redist\\Mdac folder on the product CD. The self contained nstallation file is mdac_typ.exe. Depending on what software has previously been installed on your machine, you may need to install Dcom95 first. Dcom95.exe is located in the same folder on the CD.

3. "Not Authorized Serial Number Mismatch" Error?

Problem:

When you double-click the Prophesy icon, you get an error message that reads... "Not Authorized: Serial Number Mismatch." "Prophesy Mileage is not authorized to run on this computer."

Detail:

The program, or some component thereof was running during the update process, causing the security files to be locked.

Solution:

Delete the program executable file and the security file from the program folder (ex. pfw32.exe and wchk32.dll) and reinstall. Deleting the executable file will ensure that no part of the program is running, and deleting the security file force the new installation to create a new one.

4. When I log into the program, I get a message that says: Not Authorized Error: 7854-1

It is possible that your network connection has timed out. Double click on My Computer and then double click on the network drive where Prophesy is installed. This should refresh the network and allow you to log in. If you do not see your network drive, do not have access to your network or it is unavailable then contact your local technician.

5. I get a message that says Please Register: Your Prophesy Series software is running in pre-registration mode

The system is running in pre-registration mode and needs a reset code from Prophesy. This does not indicate your account status. To obtain a reset code via email, click on Request Code Via Email and enter in the information requested before sending. If you prefer, you can call 1-800-776-6707 for the support department to obtain the reset code.

6. I cannot install an update to Prophesy from my original installation machine. What should I do?

If the installation machine is not available to use for an update installation, the next most appropriate machine to install from would be a workstation that is currently fully configured to run Prophesy from the correct network locations.

7. I'm updating Prophesy. What's the first step that I should perform?

You should always make sure that you have the installation CDs for the previous version of the system and a good backup of all data and configuration files for the system. This ensures that you have the ability to restore your system if there should be any problem during the update.

8. I'm updating Prophesy. Which machine should I install the software from using the CD?

We recommend that you install Prophesy software from the same workstation every time you update the application. This ensures that all of the components will be automatically installed to the correct location on your network. When setting up additional workstations, the CD is generally needed, though of course you should store your CD in a convenient location in case you should ever need to reinstall the software or need a utility that is included on the CD but not installed on your system.

9. Prophesy used to be installed locally on one machine. Now I'd like to set it up to be shared on my network. How should I go about installing it?

In this scenario, we recommend starting from a machine that never had the prophesy software or any components installed on it and installing in accordance with the network installation instructions from this machine to the mapped network drive. This will allow the installation to configure the support properly for a network installation. Once the software is installed, contact Prophesy for assistance in replacing the blank databases that are installed in a fresh installation with the backup copies from your prior local installation.

10. Prophesy Dispatch Series Single User to Multi-User Migration

Moving your data from a single user, one PC setup to a multi-user, network setup is a fairly simple process. There are two methods to migrate your company data. These methods are dependant upon whether you have a single company or multiple companies in Prophesy Dispatch. Single Company Migration You will be performing a single company migration if you only have one company set up in Prophesy Dispatch. The easiest way to determine how many companies you have entered in Prophesy is to check your login window. Click the Company drop down box at the top of the login screen; Aside from Sample Trucking Company how many company names do you see in the dropdown screen? If there are several, you will do a multi company migration. Please see the instructions under the multi company migration heading.

If you only need to migrate one company, please follow the instructions listed below.

1) Determine how you want to transfer your data to the new host. Be prepared to transfer anywhere from 100 Mb to 3 Gb of data.

2) Determine which Prophesy products you have installed on your single user PC. You should find the product directories in: C:\Program Files\Prophesy. Each product will have

a named folder.

a. Dispatch = Disp

b. TaxTally = TaxTally

c. DriverTrax = DriverTr

d. FleetTrax = Fleet32

e. LogPlus = LogPlus

f. FuelLogic = FuelLogic

3) In each of the named product folders you will find a subdirectory named Data, this is the folder you need to backup. (Please note: Because the Data folders for each product are named Data , you will need to create a named product folder to hold each Data folder. For example: The Data folder for TaxTally should be placed into a TaxTally folder on the backup media. Failure to do so will result in data loss due to multiple overwrites of the Data folder.)

4) Once you have made a backup copy of all your Prophesy data, you will need to do a network install of Prophesy to your new host/server. Please refer to the installation instructions for your Prophesy product.

5) Once your network installation is complete, you will want to login to the Your Name Here company and change the name in Preferences to exactly match the company name that was displayed in your previous single user login window. After you do this, log out of Prophesy.

6) From your backup media, place the Data folders into their corresponding product directories on your new host/server.

7) Congratulations! You have successfully migrated your data. Login to Prophesy and enjoy.

Multi Company Migration

You will be performing a multi company migration if you have more than one company set up in Prophesy Dispatch with the Multi Company option. The easiest way to determine how many companies you have entered in Prophesy is to check your login window. Click the Company drop down box at the top of the login screen; Aside from Sample Trucking Company how many company names do you see in the dropdown screen? If there are several, you will do a multi company migration. If you are doing a multi company migration, please see the instructions listed below. Please note: You will need a copy of Microsoft Access to complete the migration. If you do not have a copy of Microsoft Access, please contact Prophesy Support.

1) Determine how you want to transfer your data to the new host/server. Be prepared to transfer anywhere from 100 Mb to several gigabytes of data.

2) Determine which Prophesy products you have installed on your single user PC. You should find the product directories in: C:\Program Files\Prophesy. Each product will have

a named folder.

a. Dispatch = Disp

b. TaxTally = TaxTally

c. DriverTrax = DriverTr

d. FleetTrax = Fleet32

e. LogPlus = LogPlus

f. FuelLogic = FuelLogic

3) In each of the named product folders you will find a subdirectory named Data, this folder contains the data for the first company you created in Prophesy. These are the first set of folders that you need to backup. (Please note: Because the Data folders for each product are named Data , you will need to create a named product folder to hold each Data folder. For example: The Data folder for TaxTally should be placed into a TaxTally folder on the backup media. Failure to do so will result in data loss due to multiple overwrites of the Data folder.)

4) The data for each additional company you created in Prophesy can be found in the Disp folder. These subdirectories will have a shortened name that reflects the company data that they contain. Since these folders contain all of that specific company"s data for each of the installed Prophesy products, this is the only folder you will need to backup for each additional company.

5) In the Disp folder, you will find a file called Prodsys.mdb or just Prodsys. You will need to backup this data as well.

6) Once you have made a backup copy of all your Prophesy data, you will need to do a network install of Prophesy to your new host/server. Please refer to the installation instructions for your Prophesy product.

7) From your backup media, place the Data folders into their corresponding product directories on your new host/server. Place the named company folders in the Disp folder.

8) Place prodsys.mdb into the Disp folder.

9) Open prodsys.mdb in MS Access. It may show a security warning, just click the Open button. It may tell you that you can"t make changes to the database, just click Ok .

10) Once you open the database, you will see a list of tables. Locate the MasterCompanies table.

11) Open the MasterCompanies table. As you can see, this is where Prophesy looks for each database associated with each company. You will need to determine the Absolute path to each database and edit the entry in each column accordingly. For example, the old location for prodsp.mdb was: C:\Progra~1\Prophesy\Disp\Data\prodsp.mdb. The new

location might be: P:\Progra~1\Prophesy\Disp\Data\prodsp.mdb.

12) Once you have finished editing prodsys.mdb, close MS Access and try logging in. You should be able to see all of your companies in the dropdown window of the login screen.

13) Congratulations! You have successfully migrated your data. Login to Prophesy and enjoy

11. After updating the program, it tells me that Prophesy is currently being updated by another user?

When an update or install is first ran, it creates the file Lockuser.txt in the .Prophesy\Disp folder. This file disallows users from logging into the program while the update is being performed and was possibly not removed due to the install or database update ending prematurely. If the Lockuser.txt is present, it can be renamed to Lockuser(date).txt to allow access to the program. Prophesy Support MUST still be contacted to ensure there are no other problems.

12. Where is the Windows System directory?

The Windows System directory is called System in Win9x and System32 in Windows NT, 2000 or XP. It is located in the windows directory, which is likely to be Windows for Win9x or XP, or Winnt for Windows NT or 2000, but it could have another name if something else was chosen when the operating system was installed. So, it may be any of the following, among others

C:Winnt\System32

C:Windows\System32

C:Win95\System

C:Win98\System

13. During the install, I get the error: 16-bit MS-DOS Subsystem - (path) The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application?

This issue can occur if one or more of these files are missing or damaged.

Config.nt

Autoexec.nt

Command.com

To repair these missing or damaged files, have your technician refer to Article ID 324767 at Microsoft's support page. Following is a link to this page:

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

A common cause for this sort of problem is a virus, malware (adware) or other attack on your computer. These files are frequent targets and many recovery utilities will simply remove the infected files rather than restoring the original files.

14. How do I Install / Update the Prophesy software?

The packet that came with your update or installation CDs will include a set of Prophesy Dispatch installation instructions. Please refer to this for any installation questions. If you have not received or misplaced these instructions, call Prophesy Technical Support to obtain another copy.

15. Setting up Prophesy through a Terminal Services session?

Make sure that install CD is placed in the server's optical drive. If the CD cannot be loaded locally, the install files can be copied from the CD to the server. Follow the instructions in the "Running Prophesy install from non-CD storage" FAQ. Ensure that Terminal Services is running in Install mode. Run Setup as a normal install. If the server will have local workstations logging into it, make sure that the Multi-user network install option is selected. If the server will only be hosting remote users, perform a local install. When Setup prompts for the Mileage CD, the CD must be changed locally. If the CD cannot be loaded locally, again the install files can be copied from the CD to the server. Follow the instructions in the "Running Prophesy install from non-CD storage" FAQ. Once Setup is complete, select "Cancel" to the restart request. Ensure that Terminal Services is out of Install mode. Run the Prophesy application prior to rebooting to ensure the installation was successful.