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 causes and solutions
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 causes and solutions
Possible cause
Solution
Journal path has not been defined in the
FactoryTalk Batch
 Services Properties dialog.
Make sure that the
FactoryTalk Batch
 Server has a valid
Event Journal
 path. Make sure that the
Duplicate Journal
 path, if defined, is valid.
TIP: To configure journal paths, right-click an application or area name in
FactoryTalk® Administration Console
Explorer
 and select
Properties
. In the
FactoryTalk Batch Services Properties
 dialog, select the
Project Settings
 tab.
Restart path has not been defined in the
FactoryTalk Batch
 Services Properties dialog.
Make sure that the
FactoryTalk Batch
 Server has a valid
Restart
 path. Make sure that the
Duplicate Restart
 path, if defined, is valid.
TIP: To configure restart paths, right-click an application or area name in
FactoryTalk Administration Console
Explorer
 and select
Properties
. In the
FactoryTalk Batch Services Properties
 dialog, select the
Project Settings
 tab.
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 causes and solutions
Possible cause
Solution
The
FactoryTalk Batch
 Server did not read the product license successfully on startup, and the user selected demo mode 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 find 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 causes and solutions
Possible cause
Solution
The computer where the services are located is not selected.
Select 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 causes and solutions
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 correctly
Possible causes and solutions
Possible cause
Solution
FactoryTalk Batch
 does not support the use of large system fonts.
In the
Display Properties
 dialog, change the default system font size to
Small Fonts
.
Error: Unable to locate files. The Recipe directory file could not be found
Possible causes and solutions
Possible cause
Solution
The
Recipe storage
 section of the
FactoryTalk Batch
 Services Properties dialog is not configured to point to the folder that has the
Recipe.dir
 file.
Make sure that the
FactoryTalk Batch
 Server has a valid
Recipe Directory
 value that is configured to point to the folder containing the
Recipe.dir
 file.
TIP: To configure the
Recipe Directory
, right-click an application or area name in
FactoryTalk Administration Console
Explorer
 and select
Properties
. In the
FactoryTalk Batch Services Properties
 dialog, select the
Project Settings
 tab. Go to the
Recipe storage
 section on the page and select the
Recipe format
 you want to use, and the
Recipe Directory
 where the file is located. Binary and XML file formats have a default path unless you choose
Custom paths
 in the
Server directories
 section of the page. If you choose
Microsoft SQL Server Database
 you need to define both the
Node
 and the
Database
 where you want to store recipes.
Error: Application Log error
The Application log file is full
 is generated
Possible causes and solutions
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 opens.
  3. In the
    Log size
     section, select
    Overwrite events as needed
    .
  4. Select
    OK
    .
Error: Recipes not visible from
FactoryTalk Batch
 View Select a Recipe dialog box
Possible causes and solutions
Possible cause
Solution
The
Release Recipe to Production
 checkbox is not selected in the recipe header data.
For each recipe that should appear in the
Select a Recipe
 dialog, ensure that the
Release Recipe to Production
 checkbox is selected. In
FactoryTalk Batch Recipe Editor
, open the
Recipe
 menu for the recipe and select
Header Data
Release Recipe to Production
.
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, 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 Database selection dialog box
Possible causes and solutions
Possible cause
Solution
When you select the browse button for SQL server databases, no databases are displayed in the
FactoryTalk Batch Services Properties
Project Settings
Recipe storage
Microsoft SQL Server Database
Database
 selection dialog.
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 causes and solutions
Possible cause
Solution
If the primary event journal directory is located on a computer other than the
FactoryTalk Batch
 Server computer, or in a share that the
FactoryTalk Batch
 Server does not have access to, the server can not create event journal files. You can see an error message in the
FactoryTalk Diagnostics
 journal on the
FactoryTalk Batch
 Server machine.
The primary event journal directory must be located on the
FactoryTalk Batch
 Server computer in a share that is accessible. The default is under the
FTBATCH_PROJECT
 share.
To mitigate risk of an event journal loss in your system, we recommend 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.
TIP: To configure journal paths, right-click an application or area name in
FactoryTalk Administration Console
Explorer
 and select
Properties
. In the
FactoryTalk Batch Services Properties
 dialog, select the
Project Settings
 tab.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal