BusinessTECH Consulting Inc.
Great Neck, New York 11022
Phone: (516) 717-4606
sales@businesstechinc.com
TransTECH Logistics
Troubleshooting—LogiPoint-M Server Version

When I try to start LogiPoint-M I see a splash screen, then I either get an error
message or nothing. LogiPoint-M won't start.

  • If you are using the Server Version of LogiPoint-M you must make sure that the server itself has been started and is running prior to trying to start LogiPoint-M. When you installed the server a shortcut should have been placed on your Desktop. The procedure necessary to start the server differs depending on whether the OS is Windows XP or Windows Vista/7. If the former then make sure you are logged in as an Administrator and just double-click the shortcut; otherwise, you must right-click on the shortcut, select Run As Administrator and supply your credentials. If you are sure the server is running and you are trying to start LogiPoint-M on a computer other than the one on which the server is installed then another possibility is that the IP address of the computer running the server has changed. This address is stored in the TT.INI file on each computer running LogiPoint-M; this INI file is located in the COMMON_APPLICATION_DATA\BusinessTECH directory. To correct the situation either contact BusinessTECH support or determine the IP of the computer running the server and edit the INI file on each computer, removing the old IP and entering the new one..

I need to add a factor for a new Carrier. I entered the factor as a Vendor in LogiPoint-M
but when I go to add the Carrier I don't see that Vendor in the "Link to Vendor"
pick list.

  • When you add a factor as a Vendor you need to select "Carrier" under Vendor Type on the second page of the Vendor entry form.

I am trying to access SYSTEM SETUP but I get the message "Configuration File is Locked".

  • First, be sure that only one workstation at a time is trying to access SYSTEM SETUP. If that is not the cause of the problem then have everyone exit LogiPoint-M (you do not have to close down Quickbooks) and shutdown the DB Server (right-click and select Exit). Then restart the server and log back in. That should correct the problem.