Troubleshoot errors

This section outlines errors that may be encountered while running
FactoryTalk Batch
 and possible solutions to these errors.
Automatic repair of Batch component installation fails
This can happen if one or more necessary folders were unintentionally moved (in Windows explorer). For example, if the Schema folder gets moved away from its original install path, the install package starts up automatically and tries to ‘repair’ the problem. This ‘repair’ can clear out the Model and Server keys in the registry, which can make the Batch client editors generate warning dialogs because they are not able to find the Network Model.
If this happens, completely uninstall the application and then reinstall.
FactoryTalk Batch
 Server does not start
Error Message:
(none)
  • Journal path has not been defined in
    FactoryTalk Batch
     Server options.
    Modify the
    FactoryTalk Batch
     Server options to include a valid Primary Journal path. Verify that the Secondary Journal path, if defined, is valid.
  • Restart path has not been defined in
    FactoryTalk Batch
     Server options.
    Modify the
    FactoryTalk Batch
     Server options to include a valid Primary Restart path. Verify that the Secondary Restart path, if defined, is valid.
  • Incorrect
    Net
     registry key value.
    The
    FactoryTalk Batch
     Server is always installed with the default user and password.
    The
    FactoryTalk Batch
     Server’s logon/password settings are not migrated from the Server
    .ini
     file during an upgrade. To run the Server as a different user, you must change the logon/password settings, using the Control Panel
    Services
     dialog box, after a new installation.
FactoryTalk Batch
 Server runs for a specific period of time and then stops, and consistently stops at the same time interval.
Error Message:
(none)
  • Check the
    FactoryTalk Batch
     Service Manager. If the
    Allow Demo Mode
     check box is selected, this could be the problem.
FactoryTalk Batch
 Service Manager does not display the
FactoryTalk Batch
 Server and/or Event Archiver.
Error Message:
(none)
  • The computer where the services are located is not selected.
    Use the
    Select Computer
     button to select the appropriate computer.
  • The
    FactoryTalk Batch
     Server and/or Archiver services are not registered with the Windows Registry.
    To register a service, click the
    Start
     button, point to
    All Programs
    , and then select
    Command Prompt
    . Navigate to the
    Program Files\Rockwell Software\Batch\bin
     directory. To register the
    FactoryTalk Batch
     Server type
    batchsrv /service
     at the command prompt, and then press enter. To register the
    FactoryTalk
     Event Archiver, type
    batcharc /service
     at the command prompt, and then press enter.
FactoryTalk Batch
 Service Manager displays "Batch.Server Class" instead of "Batch Server".
Error Message:
(none)
  • The service displays the class name instead of the display name.
    This is caused by DCOMCNFG configuring the
    FactoryTalk Batch
     Server service to display the class name of the service instead of the display name. When this occurs, the Server no longer supports its COM interface and must be reinstalled.
The
FactoryTalk Batch
 View/Client is properly configured, but can’t view the Event Journals.
Error Message:
(none)
  • There may be a version conflict in one or more of the required files.
The text in
FactoryTalk Batch
 dialog boxes does not display properly.
Error Message:
(none)
  • FactoryTalk Batch
     does not support the use of large system fonts.
    Use the
    Display Properties
     dialog box to change the default system font size to
    Small Fonts
    .
Unable to locate files.
Error Message: "The Recipe directory file could not be found."
  • The server options for the
    FactoryTalk Batch
     Server are not configured to point to the folder that contains the
    Recipe.dir
    file. (See
    FactoryTalk Batch
     Server option configuration
     in the
    FactoryTalk Batch
     Administrator Guide
     for more information.)
An Application Log error is generated.
Error Message: "The Application log file is full."
  • The Application log is not set for wrapping.
Use the
Event Viewer
 to change the Application Event Log Wrapping setting to
Overwrite Events as Needed
:
  1. Select
    Start
    , point to
    All Programs > Administrative Tools
    , and then select
    Event Viewer
    . The
    Event Viewer
     opens.
  2. Right-click
    Application
    Log
    , and select
    Properties
    . The
    Application Log Properties
     dialog box opens.
  3. In the Log size section, select
    Overwrite events as needed
    .
  4. Select
    OK
    .
  5. Exit the
    Event Viewer
    .
List of available SQL Server databases not displayed in the Server Options dialog box.
Error Message:
(none)
When the browse button for SQL Server databases is clicked, no databases are displayed in the
Database Selection
dialog box.
Install SQL Server’s ClientTools Connectivity option. Do a custom installation of SQL Server to install the Client Tools Connectivity option.
Event Journal files are not being created.
Error Message:
(none)
  • The primary journal directory must be located on the
    FactoryTalk Batch
     Server computer in the
    BATCHCTL
     share. If the Primary Journals directory is located on a computer other than the Server computer, or not within the
    BATCHCTL
     share, and that computer becomes inaccessible, the Server continues executing batches but is unable to create event journals for those batches. You will not receive a notification of the problem.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal