General troubleshooting errors

This section outlines errors that may occur while installing and running
FactoryTalk Batch
 and possible solutions.
Error: Automatic repair of batch component installation fails
Possible cause
Solution
This may occur if one or more folders were moved in Windows explorer.
For example, if the Schema folder gets moved from its original directory, the installation package starts up automatically and tries to repair the problem. This may clear out the Model and Server keys in the registry, which will prevent the batch client editors from finding the Network Model.
Completely uninstall the application and then reinstall it.
Error:
FactoryTalk Batch
 Server does not start
Possible cause
Solution
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.
The
FactoryTalk Batch
 Server is always installed with the default user and password.
Verify that the
FactoryTalk Batch
 Server service user account is correct.
  1. Navigate to the Windows services and the
    FactoryTalk Batch
     Server.
  2. Open the service.
  3. On the Log On tab, verify “This account” is selected and the batch server account and password are correct by re-entering the user name and password.
Error:
FactoryTalk Batch
 Server runs for a specific period of time and then stops, and consistently stops at the same two-hour interval
Possible cause
Solution
The
FactoryTalk Batch
 Server did not read the product license successfully on startup, and demo mode was selected by the user to start the FactoryTalk Batch Server service.
Check the
FactoryTalk Batch
 Activation Server and make sure there is a working
FactoryTalk Batch
 server license. You can also check the batchsvr.log file to determine how the batch server is starting (demo mode or license mode) and change to license mode.
Error:
FactoryTalk Batch
 Service Manager does not display the
FactoryTalk Batch
 Server or
FactoryTalk Event Archiver
Possible cause
Solution
The computer where the services are located is not selected.
Click the
Select Computer
 button and select the appropriate computer.
The
FactoryTalk Batch
 Server,
FactoryTalk Event Archiver
, and
FactoryTalk
e
Procedure
 services are installed but are not registered with the Windows Registry.
To register a service:
  1. Select
    Start > Windows System > Command Prompt
    .
  2. Navigate to the
    Program Files (x86)\Rockwell Software\Batch\bin
     directory.
    • To register the
      FactoryTalk Batch
       Server, type
      batchsrv /service
       at the command prompt, and then press
      Enter
      .
    • To register
      FactoryTalk Event Archiver
      , type
      batcharc /service
       at the command prompt, and then press
      Enter
      .
    • To register
      FactoryTalk
      e
      Procedure
      , type
      batchmbs /service
       at the command prompt, and then press
      Enter
      .
Error:
FactoryTalk Batch
 Service Manager displays the class name (Batch.Server Class) instead of the display name (Batch Server)
Possible cause
Solution
DCOMCNFG
 configures 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.
Error: The text in
FactoryTalk Batch
 dialog boxes does not display properly
Possible cause
Solution
FactoryTalk Batch
 does not support the use of large system fonts.
In the
Display Properties
 dialog box, change the default system font size to
Small Fonts
.
Error: Unable to locate files. The Recipe directory file could not be found
Possible cause
Solution
The server options for the
FactoryTalk Batch
 Server are not configured to point to the folder that contains the
Recipe.dir
file.
Configure the server options to point to the folder containing the
Recipe.dir
file.
See
Edit the
FactoryTalk Batch
 server options
 for more information.
Error: Application Log error
The Application log file is full
is generated
Possible cause
Solution
The Windows 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
    > Windows Administrative Tools > 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. Click
    OK
    .
Error: Recipes not visible from
FactoryTalk Batch
 View Select a Recipe dialog box
Possible cause
Solution
The
Release Recipe to Production
 check box is not selected in the recipe header data.
For each recipe that should appear in the
Select a Recipe
 dialog box, ensure that the
Release Recipe to Production
 check box is selected. This can be done by selecting the
Header Data
 menu option from the
Recipe Editor Recipe
menu for the recipe and selecting the
Release Recipe to Production
 check box.
If recipe approvals are enabled, the
Release Recipe to Production
 step is not approved.
For each recipe that should appear in the
Select a Recipe
 dialog box, ensure that the
Release Recipe to Production
 step is approved. This can be done by signing off on the
Release Recipe to Production
approval step as part of the approval process defined in the area model for the recipe.
Error: List of available SQL server databases not displayed in the Server Options or Database Selection dialog box
Possible cause
Solution
When the browse button for SQL server databases is clicked, no databases are displayed in the
Database Selection
dialog box.
Install the SQL Server Client Tools Connectivity option. Do a custom install of SQL server to install the SQL Server Client Tools Connectivity option. Or just type in the database name.
Error: Event Journal files are not being created
Possible cause
Solution
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.
The primary journal directory must be located on the
FactoryTalk Batch
 Server computer in the
BATCHCTL
share.
To mitigate risk of an event journal loss in your system, it is recommended that a secondary event journal path be established to a local and separate physical drive on the
FactoryTalk Batch
 Server node, or to a location for networked storage.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal