Troubleshooting

Use the information in this section to troubleshoot responses, system errors or informational messages, that you may see in the TotalMail® 2000 Viewer.

If your issue is not described in this chapter, or if the solution says to do so, you can contact Trimble Transportation Support and locate Mobile Comm support. If you do not already have an account, select Sign Up to create one.

Responses after you send a message

This section is for responses that you might see after you send a form or text message to a driver’s device.

Responses not related to the driver’s device

This table explains responses you may see after you send a message to any type of device your driver may use. See also Responses related to specific driver device brands.

Response When This Appears How to Troubleshoot

FillLoadAssignment: There is nothing planned for this Driver/Truck

This appears if you send a trip to a driver and the driver has no other trips planned within the system’s set time frame.

This is just for your information.

Invalid parameter number

This may appear any time.

  1. Make sure that the form is correct and complete. Resend the form.

  2. Contact your TotalMail System Administrator.

MComm wouldn’t take message: Failed. Unknown reasons.

This may appear any time. For example, the transmission signal may be weak or lost.

Send the message again, after time passes.

If the message is urgent:

  • Telephone the driver.

  • Send an SMS (phone text) message to the driver.

    If those methods fail, then the driver might be out of signal transmission range, or their device is offline or damaged.

Unknown Driver ID: 1234

This message appears when you send a message to a driver ID that is not in the system.

  1. Make sure that the ID is typed correctly.

  2. Look up the driver ID in the TMWSuite File Maintenance and TotalMail 2000 Configuration applications.

    If the driver ID does not exist, but you know that it should, then create or add the driver and the ID in both the TMWSuite and TotalMail systems.

CheckBranch: Invalid procedure call or argument Evaluating BRANCH

You did not complete the form correctly.

Contact Trimble Transportation Support and locate Mobile Comm support. If you do not already have an account, you can create one by selecting Sign Up.

Creating message Unknown Addressee: ExampleID

Note: ExampleID represents a real ID in your system.

You sent a form or text message to one or more address IDs, but the system did not find the ExampleID.

You must resolve the unknown address ExampleID in the system.

  1. Open the TotalMail 2000 Configuration utility.

  2. Select Settings.

  3. Select Use In Address Resolution for the company or addressee.

Data source name not found and no default driver specified

This appears if the connection to the SQL Server is lost or is not configured properly.

Make sure that:

  1. The user name and password are spelled correctly.

  2. The server is on and working properly.

  3. The database is in the active state.

  4. Go to the Transaction Agent’s PSXact Property Page settings. Select TMWSuite DB. The correct SQL server and database display.

Nowhere to deliver message to: Dispatch group not set

This appears if you send a message to an ID that is not in your dispatch group.

  1. Look up the driver ID, tractor ID, or trailer ID.

    • Make sure that it is typed correctly.

    • Make sure that it is assigned to your dispatch group.

  2. If any ID is not assigned to your dispatch group, and you are sure that it should be, then assign it.

No data was provided to update the tractorprofile

This appears if you updated the tractor profile information (for example, the odometer reading), but entered no data in the message.

  1. Make sure that data was provided.

  2. Contact Trimble Transportation Support and locate Mobile Comm support. If you do not already have an account, you can create one by selecting Sign Up.

Look up the asset’s ID number and verify it is spelled correctly. Verify placement and update the order in TMWSuite accordingly.

You get this message if the form that you sent is not found or not recognized by your company’s mobile comm vendor (for example D2Link®).

Contact Trimble Transportation Support and locate Mobile Comm support. If you do not already have an account, you can create one by selecting Sign Up.

The form must be replaced with one that is recognized by this specific vendor.

Responses related to specific driver device brands

This table shows responses you might see based on the specific brand of device that the driver uses. If none of your drivers use the device mentioned, you will not see the corresponding message. See also Responses not related to the driver’s device.

Device Brand Response How to Troubleshoot

D2Link

MComm wouldn’t take message:The D2LinkHost could not deliver message to the phone within the time period.

  • The transmission signal may be weak or lost.
    Send the message again later, when signal strength improves or when the driver returns to signal transmission range.

  • If the message or form is time-critical, then:

    • Telephone the driver.

    • Send an SMS (phone text) message to the driver.

    If those methods fail, then the driver is out of signal transmission range or the device is offline, damaged, or lost. Wait until:

    • The driver returns to an area within signal transmission range.

    • The driver’s device is back online.

    • The driver contacts you if the device is damaged or lost.

Solera Omnitracs

MComm wouldn’t take message: QTRACS message is not acknowledged. Message is undeliverable.

  • The transmission signal may be weak or lost. Send the message again later, when signal strength improves or the driver returns to signal transmission range.

  • If the message or form is time-critical, telephone. If that fails, send an SMS (phone text) message to the driver. If both of those methods also fail, then the driver is either out of signal transmission range or their device is offline or damaged.

Solera Omnitracs

Web Service Error sending macro message: Destination not found.

Look up the unit ID in the TotalMail 2000 Configuration utility.

  • Make sure that the unit ID exists and is spelled correctly.

  • If the unit ID does not exist, then create or add the unit in the TotalMail 2000 Configuration with the correct ID.

Responses related to a driver’s action

This section applies to responses that you see as the result of a driver’s action.

All numbers in this table represent or are placeholders for the actual numbers that you might see.
Response What the Driver Did How to Troubleshoot

The equipment is already in use on another move! Move# 123456 Equipment already started on move 123456 for DRV: 1234

The driver updated the movement for a resource. That resource now overlaps with another trip. For example, the trailer ID was already on another trip.

  1. Look up the asset’s ID number. Make sure that it is entered correctly.

  2. Verify placement and update the order in TMWSuite, if needed.

WARNING!! DRIVER HAS RESET THIS TRIP TO AVAILABLE. Evaluating FORCEERR

The driver reset an assigned trip to the Available status.

  1. Look up the order in the TotalMail operations or TMWSuite Visual Dispatch app (whichever is available to you). Confirm the status. Look for an attached note that explains the change.

  2. Ask the driver about the status change.

  3. Assign the trip to another driver, if needed.

Move# 123456 Update attempt: Move: 123456, Start Time: 01/02/2034 01:02:03 AM, MatchedStop: 1 : Overlap for TRL: 123456 on Move 123456

The driver sent a trip update but one of the resources has an overlapping assignment on another trip. For example, the trailer is on a different trip.

  1. Look up the asset’s ID number. Make sure that:

    • The ID is correct.

    • The asset is not on another active trip.

  2. Update the order in TMWSuite, if needed.

MComm wouldn’t take message: Invalid or unrecognizable packet type.

This appears if you send a message but the transmission is changed, lost, or damaged between the sending and receiving devices.

Contact Trimble Transportation Support and locate Mobile Comm support. If you do not already have an account, you can create one by Selecting Sign Up.

LatLong failed: New position (11.22, 33.44) is 5678.90 miles from Current position (11, 22)

The driver updated the stop, but the tractor’s device reported a position too far from the address in the profile for the stop company.

  1. Find the company.

    • Use the TMWSuite File Maintenance app.

    • Use the TMWSuite Operations app. Select the company profile menu option.

  2. Make sure that these are true:

    • The address, ZIP code, latitude, and longitude are correct.

    • The set position is correct.

      • In the General Information Table, find the TMUpdCmpLatLongTolerance setting. The number in the Int1 box is the number of miles that the driver can be from the address without getting an error.

    • Make sure that the driver is at the correct stop.

Other responses

This section is for responses that don’t fit in the other categories.

All numbers in this table represent or are placeholders for the actual numbers that you might see.
Response When This Appears How to Troubleshoot

UpdateStopCoreMain: updmove(6.5.2696).
clsUpdateMoveLib.
SetValues:ErrorInSetValues:

This error is not specific.

Contact Trimble Transportation Support and locate Mobile Comm support. If you do not already have an account, you can create one by Selecting Sign Up.

No information returned for view EvalExpr From stored procedure: tm_EvalExpression Evaluating EVALEXPR

When you run Evaluate Expression, no data returns.

Contact Trimble Transportation Support and locate Mobile Comm support. If you do not already have an account, you can create one by Selecting Sign Up.

That Trip Segment is already started Move# 12345 Move 12345 is already started for tractor 54321: Trip already started.

This appears if you enter a new trip with status Started.

Make sure that you entered the correct trip number.

Cannot insert the value NULL into column 'log', table 'TMW_Live.dbo.log_driverlogs'; column does not allow nulls. INSERT fails.

This appears if you update the Driver log but do not enter a number in the log column.

  1. Enter the value and update the Driver log again.

  2. If you still see this, contact your TotalMail system administrator. The admin will run the SQL below.

    ALTER TABLE log_driverlogs ALTER COLUMN [log] char(96) NULL