Running schedules

This topic lists some issues when running schedules.
A schedule didn't run.
You must make a schedule active for its status to be
Waiting to Run
or
Running
.
An operation failed.
  • Certain operations, such as Backup and Compare, may fail if the operation requires that a device has a master file and it does not.
  • The RSLinx path on the client computer where the device's addressing information was set may not match the RSLinx path on the agent computer running the schedule. All computers in the FactoryTalk AssetCentre system must have the same RSLinx drivers and paths.
  • Message: Backup [or Backup and Compare] Failed – Runtime File Not Found…
    This message appears if one asset's location set in the Addressing Info field of the Device Properties dialog box was using another asset's location. For example, if you select Allen-Bradley PanelView Plus in Allen-Bradley MobileView operator interface's Addressing Info field or vice versa and run the Backup or Backup and Compare schedule, the operation would fail. Make sure all the assets' location set in the Addressing Info field is correct before running any schedules.
  • Scheduled events for Allen-Bradley Logix 5000 and PLC-5 controllers would fail if FactoryTalk Security was enabled for earlier versions of RSLogix 5000 and RSLogix 5. The problem is fixed in RSLogix 5000 versions higher than 16 and for RSLogix 5 version 7.30.10.3 and higher.
    This issue does not affect other devices’ schedules (such as robots or Allen-Bradley PanelView devices). If a schedule contains affected controllers and other devices, the scheduled event will only fail for those affected controllers for which FactoryTalk Security is enabled in the programming software; the event will complete for the other devices.
A schedule takes a long time to run or never finishes.
The agent that actually performs the operation may be busy, unavailable, or uninstalled. If
Waiting for Interface
 appears next to the scheduled assets in the lower left pane of the
Schedules
tab and it never changes, then all agents are busy or no agents are online. You can check all schedules on the
Schedules
tab to see whether any are running (and thus using the available agent or agents). You can also check the status bar to see how many agent computers are connected to the system.
Another reason can be that the FactoryTalk AssetCentre server has been updated, but the software on the agent computer has not been updated. If the agent software version is not compatible with the server software, the agent will not run. A message is logged in the System Event log and the AssetCentre Event log. You can also see the number of active agents appears in the status bar of the FactoryTalk AssetCentre desktop client.
Email notifications do not reach their intended recipients.
  • Make sure you are using valid email addresses. Email addresses must be in standard SMTP format (for example, myaddress@domain.com). Other types of email addresses are not handled by FactoryTalk AssetCentre.
  • Check your event log to make sure the scheduled operation is completing.
  • Check your schedule definitions to make sure there are email addresses assigned to receive notifications.
  • Make sure the FactoryTalk AssetCentre server Machine Edition is set up to send email. To do this, log onto the FactoryTalk AssetCentre server computer, and then go to
    FactoryTalk Administration Console
     >
    System
     >
    Policies
     >
    System Policies
     >
    SMTP Policy
    . Consult with your email administrator for the correct settings.
  • If you are using a firewall (such as the Windows Firewall), make sure the ports used to send email traffic are open. Also make sure that SMTP services are permitted to send traffic through your firewall. See the
    FactoryTalk AssetCentre Installation Guide
     for information about configuring the Windows Firewall.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal