888.509.5307
Get an Info Kit
Get an Info Kit
Welcome to the Prophesy Customer Care Center!
Our team is here to help you get the most from your Prophesy Software!
Simply select your area of interest.
To adjust rates across the board or for select rates within a rate schedule, right-click and select Adjust Rates.
Example: changing a fuel surcharge
Always double-check for correction.
There are two ways to check your program version from within the program.
On the drive on which Prophesy is installed, browse to the folder \Program Files (x86)\Prophesy\Disp. and delete the file Lockuser.txt. Then try opening the program again.
If you are sure you have not reached your maximum user login limit, it could be that the program is registering logged in users that are not actually logged in. A user with administrative access can follow these steps to clear the license locks:
Note: Following these steps will reset the Dispatch Board back to its default view, which means that any view customizations will need to be reapplied if necessary.
There are two different layouts for the Booking screen in Dispatch. To change your layout, open any load or book a new one, then click Edit > Toggle Screen Layout. Repeat this process until you have the layout that you need. You may also set a default booking screen layout on the System Defaults tab of the Preferences window.
There are a few possible reasons for this. Here are some things you can try:
Unloaded origin tracking is a simple concept once you are familiar with how it works, however it commonly causes some initial confusion. The most important thing to understand is that when Dispatch assigns an unloaded origin, it is pulling the unloaded origin information from the tractor’s record, and not the driver’s record. So if for some reason the unloaded origin isn’t assigning properly, it can most likely be resolved by verifying the information is correct within the tractor’s master record:
A typical issue with unloaded origin tracking is that the check-in date is incorrect. It is possible for dispatchers to enter an invalid date, and not realize this when building the load, therefore updating the tractor’s record with an invalid date. After correcting the date as well as the location in the tractor’s record, the next load you create that has this tractor assigned to it will pull the correct unloaded origin. (A tractor’s current status does not get updated with dates prior to what the current status shows within the tractor’s master record.)
For example, if the current status shows a date of 02/02/2041, and you complete a load on the date of 03/05/2014, the tractor’s record does not get updated with the destination of that load. This is because the date in the record is later than that of the completion date of the load.
This could be a problem with not having the necessary permissions to the C:\Program Files\Common Files\ODBCData Sources folder. Give the user full permissions to this folder and re-run Workset.exe or Userset.exe as needed.
If you have the appropriate administrative permissions, you will be able to click Yes to log in. Then click Maintain > Users and click the Reset Logins button. If you do not have permissions, another user with the proper clearance must log in and complete this process.
If you are sure that no one else is running this report, it could be that the program erroneously locked it. Do the following to clear the reporting locks:
If you are sure that no other user is posting currently, it could be that the program erroneously locked the posting screens. Do the following to clear the posting locks:
Prophesy Dispatch has a built-in utility that allows you to compact and repair the Dispatch database in the event that it becomes corrupted or grows too large in size. This utility should be used with caution! It is highly recommended that you or your IT personnel back up the databases before any of the following procedures are done. For more information on this procedure, please contact Prophesy Support at ptssupport@accellos.com or 1-800-776-6707.
To compact and repair your database:
If the above does not work, or if you need to compact and repair a database other than your primary Dispatch database (such as TaxTally), you can try compacting and repairing your database manually:
Example:
“C:\Program Files (x86)\Access 97 Runtime\Msaccess.exe” /runtime “C:\Program Files (x86)\Prophesy\Disp\Data\Prodsp.mdb” /compact
“C:\Program Files (x86)\Access 97 Runtime\Msaccess.exe” /runtime “C:\Program Files (x86)\Prophesy\Disp\Data\Prodsp.mdb” /repair
Often, users find it necessary to customize their dispatch board in ways that best accommodate their needs. The dispatch board allows for this on a number of levels. Here are some helpful features you can use to customize your experience:
Note that all view options are specific to your user account, allowing each person to have his or her own customized view.
For example, if you want to find 25% of 93% of a given amount, make a calculation of 93 * 25%. In this case your result is 23.25.
A complete Prophesy backup requires all .mdb files residing in active Prophesy folder and its subfolders be copied to secure backup media. A technician familiar with your network would best handle this. You may also find out where your data is by clicking Help > About > Info. This will give you the exact location of your data. If you have Multi- Company Dispatch you should do this for each company.
Dispatch: [Mapped drive]:\Program Files (x86)\Prophesy\Disp\Data\*.mdb
TaxTally: [Mapped drive]:\Program Files (x86)\Prophesy\TaxTally\Data\*.mdb
LogPlus: [Mapped drive]:\Program Files (x86)\Prophesy\LogPlus\Data\*.mdb
DriverTrax: [Mapped drive]:\Program Files (x86)\Prophesy\DriverTrax\Data\*.mdb
FleetTrax: [Mapped drive]:\Program Files (x86)\Prophesy\Fleet32\Data\*.mdb
* If you are using Prophesy Accounting or QuickBooks, you must back up the .mdb files in the Disp\Acc folder, or the file ProQB.mdb in the Disp\Data folder, respectively.
* If you are using a multi-company version of Prophesy Dispatch, each company will use its own set of databases (located by default at [Mapped drive]:\Program Files (x86)\Prophesy\Disp\[Company Name]).
All of these databases must be backed up prior to updating the program. Also, if you have numerous companies, it may be convenient (though not necessary) to back up the file “prodsys.mdb” (located in the Disp folder), which contains a list of your companies and their database locations. If the Prophesy software is to be moved to a new location upon restoring the data, the MasterCompanies table of “prodsys.mdb” must be updated with the new locations. Please contact Prophesy Support at ptssupport@accellos.com or 800-776-6707 with any questions regarding this matter.
Prophesy Dispatch allows you to use your own custom logo on reports and freight bills. To use this feature, size and format your logo to the following specifications:
Once your logo file is in the Disp folder, the reports and freight bills should utilize this file and show on the printout.
NOTE: For Multi-Company Dispatch, follow the steps above. However, if different logos are used for different companies, you must copy the corresponding logo into the company folder located in the Disp directory. These folders are the ID’s that you created when you first added the company via Prophesy Dispatch.
Beginning with the Dispatch Version 6.1 update, Prophesy Dispatch no longer includes the legacy Version 4.1 booking screen. We continue to make changes in workflow and overall functionality to the booking interface introduced in Version 5, and these changes have rendered the older interface obsolete.
To assist former users of the Version 4.1 booking screen, and for general reference, a set of videos on how to build a load using the Version 5 booking screen can be viewed by clicking the links below.
Pending Loads – Creating Loads and taking customers’ orders (12 minutes)
Assigning Loads – Assigning Drivers, Owner Operators or Carriers to a load (8 minutes)
Close all windows within Prophesy so you see only the gray background. The utility menu will then be available (if you have appropriate administrative permissions).
When you create transactions in Prophesy Dispatch, revenue types are associated with these transactions. This translates into A/R transactions for your invoices and expense accounts for your Payroll, Owner Operator or Carrier payments in QuickBooks. You can view a list of the standard revenue types that come with our software by clicking Maintain > Rating > Revenue Item Types.
What happens when I select defaults?
Whether you’ve just set up QuickBooks or have used it for years, you already have a Chart of Accounts. Using the defaults option does not remove these accounts; Prophesy will only add revenue types to them.
Example:
Invoices will be sent to your A/R under the ”Trucking Revenue: Sub” account specific to the revenue item type. The same will apply to your expenses. Owner Operators’ payments will be sent to the ”Purchased Transportation: Sub” account specific to the revenue item type. Again, Prophesy will add accounts to your existing accounts but does not alter or remove any accounts that you have already set up.
In QuickBooks, click Customers > Create Invoices, check To be Printed at the lower left hand of the screen and click the Customize button at the top. In the template, click Print Status Stamp.
After sending new or modified data to QuickBooks, the interface generates a status report with these details:
Especially during the conversion from IIF to SDK interface or when modifying the account assignments, specific errors can occur. The following will explain how to trouble shoot and correct these problems.
1. The name of the list element “Customer ID” is already in use. Please note: This warning is most likely displayed after the initial data processing session, immediately after the conversion from IIF to SDK or after accounts have been re-initialized or modified.
2. The Customer ID in the Dispatch program must correspond to the Customer Name in QuickBooks. This is different from the IIF interface, where the Dispatch specific Customer Name was displayed as the Customer Name In QuickBooks.
3. Company Name with the QuickBooks Customer Name. After the initial data processing session the Status Report window should display the status “Modified” for successfully processed customers that exist both in Dispatch and QuickBooks. New customers, customers that only have been entered in Dispatch should be processed with the status “New.” If the processing of specific customer records failed with the displayed error status, one of the causes listed below, will apply.
1. The customer exists in the Dispatch file, but is set to “Inactive” in the QuickBooks company file.
2. The Company Name for this customer is duplicated by a QuickBooks Vendor Name or QuickBooks Employee Account No. This could be caused by the above mentioned “swapping” of QuickBooks Customer fields.
3. The Customer ID exists in QuickBooks Correction of problem
1. Change customer status to “Active”
2. Locate and modify the duplicate ID in the QuickBooks file, by appending a letter or number to the name
3. Modify the duplicate ID in the QuickBooks Other Names list, by appending a letter or number to the name
The same warning message can be displayed for account names as well. The name of the list element “Service Item” & “Account Name” is already in use
1. “Company Driver Payroll” exists both in Dispatch and QuickBooks, and is not assigned to the respective income account in QuickBooks.
2. “Company Driver Payroll” exists both in Dispatch and QuickBooks, but has the wrong type in QuickBooks.
Correction of problem
1. Edit the revenue item in QuickBooks and assign the required account.
2. Edit the revenue item in QuickBooks and modify the item type.
Often users may discover issues with processing information from Prophesy to QuickBooks. These issues could be the cause of needing to update the QuickBooks application via patches that QuickBooks distributes to its users. For example:
QuickBooks 2006 should be updated as often as possible.
To update the QuickBooks application, do the following.
a) Open the QuickBooks application in Single-User mode
b) Click on Help>Update QuickBooks.
c) Click the Update Now button
d) Click on Get Updates
If any updates need to be downloaded and installed, the update procedure will do this automatically. The procedure can take a while depending on internet speed, so please plan accordingly. Other users will need to remain out of QuickBooks completely while the update is being performed. At the end of the update, the update will prompt you to reboot the machine.
***Also note that this update procedure should be done from all the machines that run the QuickBooks application.
For more information on updating the QuickBooks application, you can visit http://quickbooks.intuit.com/
1. Open QuickBooks. Be sure to open the QuickBooks Company you want to link with Prophesy.
2. In QuickBooks, click File > Open Previous Company.
3. Write down exactly what is displayed on the top line.
4. Close QuickBooks completely.
5. Log into Prophesy and click Accounting > Run QuickBooks Export.
6. Here, at the top, double-click on the Green writing that reads ‘Dispatch/QuickBooks Interface’.
7. This will open a text box on the bottom right of the screen.
8. In the text box, type in ‘restore’ (without the quotes). Then hit enter on your keyboard.
9. This will open a browse window. Browse and select the file you wrote down in step 3 above.
10. A message should display indicating the program has been reconnected. Then close the QuickBooks Export screen.
11. Open QuickBooks and make sure it’s in Single-User Mode.
12. In Dispatch, open the QuickBooks Export screen and process information to QuickBooks from Prophesy as needed.
Technology professionals recommend waiting to migrate to new technology for business critical software and systems until a stable version is available. Most new software applications have multiple updates within the first few months of release. Peachtree has also dramatically increased its system requirements for its products. You should also evaluate your hardware so you can properly run any new software.
Open your Peachtree application. Click on Help > About Peachtree Accounting. At the top of the screen, it provides the version of Peachtree that you are using.
Yes.
While we work with many versions of Peachtree. Sage has made significant changes to the way all software interfaces with its software. This product is new to everyone, including all your software manufacturers. We would caution customers against upgrading to this new system without evaluating its impact on all business critical software and processes.
Prophesy is currently working on new releases that will take advantage of the new Peachtree 2009 accounting system. Customers on Prophesy CompleteCare (Technical Support, Software Updates, and much more!) will receive these updates when available at no additional cost.
Peachtree is a registered trademark of Sage Software, Inc. and its affiliates.
Make sure that all windows within Dispatch are closed. Click Utility > Clear User Views. Check the Freight Billing check box and then click Reset. Click OK and try reopening the Print/Post Freight Bills screen.
If another user is not in the Print/Post Freight Bills screen, make sure that all windows within Dispatch are closed and click Utility > Clear Posting Flags. Click Yes on the message that appears and try opening the Print/Post Freight Bills screen again.
From the main screen in Prophesy Accounting, click File > Clear All Locks. Enter your password (if one has been set up) and click Verify. This should allow you to open the module as needed.
Go to the Accounting login screen and click Update Settings. Modify the address and save the changes.
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.
The parts data can be imported into FleetTrax using the Import/Export functionality. The Import/Export functionality can be accessed by clicking Utility->Data Maintenance->Data Import/Export->Import. Then select the parts from the drop-down box.
Import/Export – Parts
The import functionality requires the data to be in a pre-defined format. Please refer to the Import/Export File Format section in FleetTrax Help manual.
The cost of the parts can be edited using the Parts – Inventory option. To change the cost of the parts, please do the following: Select Inventory-> Stock->Parts->Inventory menu in FleetTrax. The list of the parts will be displayed. Select the parts records, whose cost is to be modified and then click on ‘Modify’. The selected parts record will be displayed. The cost of the parts is displayed as ‘Level 1′, ‘Level 2′ and ‘Level 3′. Click on the ‘Edit Cost Structure’ button.
Parts Inventory
You will be asked to enter the ‘Audit Password’.
Audit Password
After entering the correct ‘Audit’ password, the ‘Level 1′, ‘Level 2′ and ‘Level 3′ Quantity and Cost are enabled for editing. You can edit the cost and then click on the ‘Save’ button.
The above message is displayed to indicate that the FleetTrax application upgrade or FleetTrax Database upgrade process is been started by some you. Please check with the other user of FleetTrax, if they have started the FleetTrax Upgrade or FleetTrax Database upgrade process. Try running the application after the upgrade process is over. In case if it is found that no other user has started the upgrade process, then search the folder where FleetTrax.exe is installed. Locate the file ‘LockUser.txt’. You can delete this file. After deleting this file, you should be able to access the application as usual.
Note: Please don’t’ delete the file if the upgrade process in going on.
User can configure the Barcodes using the Inventory->Bar Code->Setup Label. Please refer to the ‘Barcodes’ section in the FleetTrax Help manual.
The above error message occurs if the status of the user is marked as ‘Logged In’ in the database, in this we need to re-set this status. One of the possible reasons for such situation can be, if the user’s has shut down the PC, without closing the FleetTrax. Following the given steps will help to reset this status.
1. Click on the Admin Tools button.
2. Select the radio button that says ‘Reset Logged- In Users’ and click on continue button.
3. Type in the Administrator’s User ID and Password and click on continue button.
4. Click on Reset All logins Button and then the OK button this should reset the status.
Click on Utility > Security Options > Audit Password.
In this screen type in the Old password followed by New Password in both the fields and then click on Save.
Click on Utility > Data Maintenance > Change Unit Cost of Fuel Logs.
Change the price from this screen and then click on Save.
Click on Utility > Data Maintenance > Change > Vehicle Number.
Enter the New Vehicle Number and click on the change button
Click on Utility > Data Maintenance > Change > Change Password.
In this screen type in the Old password followed by New Password in both the fields and then click on Save.
Click on Utility > Security > User Accounts.
Click on Add and fill in the details and then click on save.
If your reports show incorrect vehicle totals, or if you see different totals on different reports
for example, the “Vehicle Lifetime Totals” and “Work Orders” reports,
you may need to rebuild your vehicle totals. This needs to be done for each vehicle that is showing incorrect or discrepant totals:
1. Open a vehicle profile and click the Edit Totals button on the General tab.
2. Click the Rebuild button.
3. Select the months you would like to rebuild by checking the box to the left of each, or click the Select All button to select all months.
4. Click the Rebuild button.
5. Click OK in the Vehicle Totals window.
6. Click Save in the Vehicle Profile window.
The official FMCSA website has a complete list of federal regulations governing transport companies. Inspection regulations are found in Part 396 and can be accessed by clicking the following link:
http://www.fmcsa.dot.gov/rules-regulations/administration/fmcsr/fmcsrguidedetails.asp?regulation=396
The main FMCSA Rules & Regulations page can be found at:
http://www.fmcsa.dot.gov/rules-regulations/rules-regulations.htm
When you create a new vehicle profile in Dispatch, it is automatically exported to FleetTrax along with the initial odometer reading you entered in the Dispatch profile. For example, if you create a vehicle in Dispatch named T101 with an odometer reading of 10,000 miles, an identical vehicle named T101 is automatically added to FleetTrax with a reading of 10,000 miles.
From this point forward, the odometer reading in FleetTrax is generally considered to be more current, given that readings in FleetTrax are always physical, and those in Dispatch are typically estimated.
When you are completing a load in Dispatch, the current odometer from FleetTrax is retrieved and displayed in the “Cur Odom” field of the load completion screen. When you click OK to complete the load, the total miles on the load are added to both the Dispatch and FleetTrax odometers.
Odometer updates from any source other than completed loads will not be exported from the program in which they are done. This includes FleetTrax work orders, daily logs, and fuel logs; as well as direct updates to vehicle profiles in either Dispatch or FleetTrax. Using our example, say you complete a FleetTrax work order with an odometer reading of 11,000 miles. After completing the work order, T101 will show 10,000 miles in Dispatch and 11,000 miles in FleetTrax.
Now if you complete a 500-mile load in Dispatch, the load completion screen will show that the vehicle currently has 11,000 miles, because that is the reading in FleetTrax and is presumed correct. When you click OK, 500 miles are added to both the Dispatch profile and the FleetTrax profile, giving T101 a total of 10,500 miles in Dispatch and 11,500 miles in FleetTrax. (Note that you can edit the “New Odom” field in the load completion screen to control the new reading that is sent to FleetTrax, or even choose not to send equipment updates to FleetTrax at all.)
To utilize this process Prophesy will need to get a couple of files from your company. There are two files that we will need, Comdata transaction fuel file & also the Prophesy Dispatch database, which is named prodsp.mdb. Call your Comdata Customer Relations Representative. Tell them you need flagged FM 00001 Fuel Bill (Data) because you need 384 byte fuel data or ‘Standard Fuel Layout Via Motors’ data that is processed by Comdata Reports. Once this request is made the files will be available the next day. At this point ask Comdata to help you download Comdata Reports and install this on your PC. With this configuration you will also create a folder on the C drive called Comdata. Steps you would take to download the Comdata information. To get files from Comdata follow this process
Select TRANSFER and FILES
Select “All Account and Customer Codes” and “All Data and Print Files” and click <OKAY>
Should give you a RESULT SUMMARY window
Click <OKAY>
Then to prove you got files from Comdata
Select REPORTS and DATA
Select “Fuel Card Billing US ” – (if flagged at Comdata for mixed billing, also need Fuel Card Billing )
Select “Customer Ids”
Select “From Date” and “To Date”
Select “Print” or “Print Preview” and click <OKAY>
If you get a blank report and you think you had activity on a day, call Comdata to confirm you did or did not have activity
If doing Print Preview, close all Preview Windows before proceeding To make the fuel data available for Prophesy
Select DATABASE and EXTRACT
Select “Fuel Card Billing US ” (if flagged at Comdata for mixed billing, also need Fuel Card Billing Canada )
Select “Customer Ids” (this is data you want to make available for Prophesy)
Select “From Date” and “To Date” (this is data you want to make available for Prophesy)
Record Length is always 384
Click <OKAY>
This then takes you to a “SAVE AS” window
Select the C-drive
Select Comdata folder
For file name, We recommend that you use transaction date. An example of this would be “032504.txt”and then click <SAVE>
Should say “Database Extract Completed Successfully ”
At this point you have successfully downloaded the information from Comdata. The next step of this interface will be to import this data into Prophesy Dispatch. To do this, Prophesy Technical Support will set up a time with you. We currently dial into your machine with a set meeting using a product called WEBEX. This will allow us to set up the rest of the interface by transmitting/updating a definition file, and we will also give you a walkthrough of the import process of your Comdata files. If you have additional questions about this process, please email support@mile.com.
Note that a printed installation guide was included in the folder with your most recent disc. If you do not have this guide, you can download it here.
The Prophesy system requirements are found near the beginning of the installation guide, which you can download here.
Instructions on this process can be found here.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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
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
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.
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
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.
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.
This can occur when you attempt to start an application after it has closed unexpectedly. Press CTRL+ALT+DEL on your keyboard or right-click on an empty area of your Windows task bar, and then click “Task Manager”. On the Applications tab of the Task Manager window, click on the application to highlight it and then click the End Task button. Once the application is closed, try opening it again. If the problem persists, try rebooting your PC.
Yes. First, copy all of the files from the disc to a new folder; we will name it ”Prophesy Disc” in this example. Open the folder “Prophesy Disc\Redist\Prophesy\Util”, and copy the files CDROM.TXT and CDROM.BAT into the “Prophesy Disc” folder. Now you can perform the installation on any PC that has access to this folder by running the CDROM.BAT file.
When contacting our support team it may be useful to send us a picture of your screen, or screenshot. Simply press the PrtScn key on your keyboard (typically directly above the Insert key). Next, open Microsoft Word if it is installed, otherwise you can open Microsoft Paint; and press CTRL+V on your keyboard to paste it into a new document. Save the document and attach it to your helpdesk ticket or other message to us.
Prophesy applications are fully compatible with the following Windows versions:
*Windows 7 and Windows Vista are no longer supported.*
Note: User Account Control (UAC) must be turned off to install Prophesy or run a workstation setup in a network environment. For instructions on how to turn UAC on or off, please refer to the Training Videos section on this page or our installation guide.
In the menu, click Maintain > Driver Letters. Here you may either modify an existing letter, or create your own. To modify an existing letter, scroll through the available letters, make any necessary changes, and click the Save button. To create a letter, click the Add Record button, fill in all appropriate information, and click the Save button. Next, click Reports > Violation Letters. Select a date range between which you would like to track violations or compliance, then choose the letter you wish to print, and finally, select one or more drivers to which to send the letter. Click the Run button, and the letters will appear on the screen.
This can occur if the database was not properly converted to Microsoft Access 97 format when you updated LogPlus to version 6.4. To convert the database manually using the Access 97 runtime environment (included with the Prophesy software), click Start > Run, and type:
“C:\Program Files\Access 97 Runtime\msaccess.exe” /convert “[database]”
where [database] is the full location and name of the database you want to convert. Be sure to enclose all filenames in quotes (“”), but do not enclose the /convert option in quotes. When you click OK, the conversion is performed, and LogPlus should now open.
In rare cases, it may be necessary to repeat the audit process. Run the audit utility again, and if that does not work, check to make sure all logs have been entered exactly as they appear on the written logs, and manually check the number of duty hours within the applicable 7- or 8-day period.
Open one of the logs, and the driver name may correct itself immediately. If so, make sure that this is indeed the correct log for this driver, and click the Save button. Repeat the process for each affected log.
The FMCSA website features articles, guides, and frequently asked questions regarding the new Hours of Service rules. Go to the main FMCSA page, http://www.fmcsa.dot.gov, click the “Rules & Regulations” tab, and click the link entitled “Hours of Service (HOS)”. The direct address of the HOS page is:
http://www.fmcsa.dot.gov/rules-regulations/topics/hos/hos-2005.htm
The Parameters button contains options that apply only to trip sheets and the map, so it is only enabled when one of these windows is active (in front of all other windows). To enable this button, open a new or existing trip, or open the map.
Press F2 to open the Parameters window, and click the Data Paths tab. Verify that these paths are correct and change them if necessary. Then reboot your PC. If the error does not go away, and you find that your changes to the Data Paths tab of the Parameters window did not hold, you may be experiencing a Windows Registry issue that can occur when Windows has been configured to start without displaying the login window. Try adding a password to your Windows account to see if this helps.
This is a Windows 2000/XP related issue that can occur when a valid TEMP environment variable has not been set or is set incorrectly. To set your TEMP environment variable, make sure a valid Temp folder exists on your computer and is accessible to all users, or create one if necessary. Then:
Prophesy Mobile Comm is a next-generation Mobile Resource Management (MRM) solution that allows you to easily manage all of your mobile assets. Using GPS-enabled devices (cell phones or in-cab devices), you can track your drivers, vehicles and other mobile assets. Prophesy Mobile Comm also supports two-way data communication so you can send Load and other information to your drivers – and they can reply to that information. Full integration with Prophesy’s Dispatch software is also available.
When a version update or install is loaded, it creates the file Lockuser.txt in the .Prophesy\TaxTally\Data 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.
The validation utility in TaxTally is a useful tool to correct reports in the event that your data becomes disordered. Especially if you have opened previously saved trips and modified data in any way, validation may be necessary. To run the utility:
1. Make a backup of your TaxTally database.
2. Open TaxTally and click Utility > Validate Transactions in the menu.
3. Click the Validate button, and you will see activity in the status bar in the lower left of the screen. A message will appear when the process is complete.
4. Click OK and run your report to see the changes.
The program has likely updated the rates using the wrong “taxrates.txt” file. To fix this: click Utility > Update Tax Rates in the TaxTally menu. Note the bold black type above the file list at the left. If the ending folder name says “Disp”, then click once on the two periods in brackets ([..]) in the list. Then click the TaxTally folder once ([TaxTally]). Finally, click the Install button in the lower right of the window, and proceed with the update normally.
Detail: The Prophesy Logo appears on all TaxTally reports by default, but it can be bypassed by creating a picture to replace it.
Solution: Create a 288 x 58 pixel bitmap in MS Paint and save it as “taxlogo.bmp” in the TaxTally folder. You can put your own logo into the bitmap, or, if you do not want a logo, simply leave it blank.
This means that communication between TaxTally and Acrobat has not been established. Try reinstalling Acrobat and running the report again. Acrobat version 5 is included on the Prophesy installation CD in the “Redist” folder. For the latest Acrobat version, go to http://www.adobe.com.
IMPORTANT:
Do not use the following procedure if you have ever modified truck weights or fuel types in entered transactions. This process will reset all transactions to the default weight and fuel type for the assigned vehicle.
1. Make a backup of your TaxTally database.
2. Open TaxTally and click Utility > Validate Transactions in the menu.
3. Check the box labeled Reset weight/axle data, then click the Validate button, and you will see activity in the status bar in the lower left of the screen. A message will appear when the process is complete.
4. Click OK and run your report. The error message will no longer appear.
1. Install TaxTally agency from one of the new workstations to the new network location.
2. Export the HKEY_LOCAL_USERS\Software\ODBC\ODBC.INI and HKEY_LOCAL_MACHINE\Software\Prophesy Transportation Software, Inc.\Prophesy TaxTally\Clients registry keys as “ODBCReg.txt” and “ClientRg.txt”. Have the user send them to us.
3. Clear out any ODBC Data Sources that are not TaxTally Clients from the ODBCReg.txt.
4. Search and replace the old drive and directory with the new desired location in the two text files. Merge them together by pasting the contents of one file with the exception of the first line (REGEDIT4) to the second. Send the resulting file ‘NewReg.txt’ back to the user.
5. Copy the client data folders (all folders under TaxTally except \Data, \Supp, and \Backup) to the new location on the network. At this point make sure that no further data entry is being performed locally on the original workstation.
6. Have the user import the registry entries from the merged NewReg.txt by renaming the file clients.reg and double clicking the file. Regedit should confirm that the file was imported successfully.
7. Run the application from the new workstation and confirm that you have access to all the clients.
8. Run the workstation setups and registry import for all remaining workstation, saving the original machine that had the program running locally for last.
1. Open Task Manager (press CTRL+ALT+DEL on your keyboard, and then click Task Manager).
2. Click the Processes tab.
3. Locate “protax.exe” in the list, then right-click on it and select End Process.
4. Click Yes to confirm.
Have you ever struggled through a TMS implementation? If your answer is yes, you are not alone.
Implementations are certainly not the same for all businesses and can sometimes be tricky. We understand that small to medium size trucking companies and brokerages, like yours, function differently than the industry big dogs and need implementation plans that fit your business. We strongly believe that no matter what your size, your company should receive all of the personalized care and specialized instruction that it deserves.
This whitepaper outlines the top five action items that small to mid-size businesses can take on to help simplify the implementation process and assure that it is completed successfully. These steps include:
Prophesy Transportation Solutions offers both web-based and stand-alone systems to fit any customer’s need. More than 12,500 trucking companies, brokers, and 3PLs have chosen industry-preferred Prophesy Transportation Solutions software to handle growth, increase revenue, and maximize profits.
NEED HELP WITH THE UPDATE? View our tutorial video here.
The following fuel tax update is available to Prophesy TaxTally customers with an active Prophesy CompleteCare subscription. To complete this update you will need the password that was emailed or faxed to you by Prophesy.
For help with installing this update, a tutorial video is available here. If you need further assistance or did not receive the password, please open a support ticket.
CURRENT RATES VERSION: 3-2024-01
Additional downloads might be required depending on your version of TaxTally.
Watch Tutorial Video Read InstructionsIf you do not have a PDF reader, click here to download a free copy of Adobe Reader®.
If you use the latest version of Adobe Reader, you might be unable to open IFTA forms due to Adobe’s new security features. To fix this issue:
Prophesy now offers FREE access to the 25 DOT mandated forms required during the driver interviewing and hiring process. These forms are also included in Prophesy DriverTrax.
Simply fill out the contact form to continue the download process. We will send you a secure link via email to the FREE downloadable forms.
(Please add moreinfo@mile.com to your permitted email list if you use any SPAM blocking software to insure that this email is not accidentally blocked.)
