FactoryTalk Batch Server configuration errors
This section outlines
FactoryTalk® Diagnostics
messages that may occur due to FactoryTalk Batch
Server configuration errors in the FactoryTalk® Directory
. Messages apply to the configured role on a FactoryTalk Batch
Server's machine, which can be either a primary or secondary
server.For messages that reference the
FactoryTalk
Batch Server configuration
location, '%s'
represents the full path to the FactoryTalk Batch
Server configuration object in the FactoryTalk Directory
.Error: Unable to start because directory not found: Primary
Journal directory configured for this computer in
FactoryTalk Directory
Batch
Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the directory path specified
as the Primary Journal directory—now known as
the Event Journal directory—cannot be
found. | Make sure that the directory path specified is valid.
TIP:
To configure the
Event Journal directory path,
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. |
Error: Unable to start because directory not found: Secondary
Journal directory configured for this computer in
FactoryTalk Directory
Batch
Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the directory path specified
as the Secondary Journal directory—now known
as the Duplicate Journal directory—cannot be
found. | Make sure that the directory path specified is valid.
TIP:
To configure the
Duplicate
Journal directory path, 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. |
Error: Unable to start because of directory access permissions:
Primary Journal directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when a check for Read/Write access
permissions on the directory path specified as the
Primary Journal directory—now known as
the Event Journal directory—fails. | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the Event
Journal directory path resides.
TIP:
To configure the
Event
Journal directory path, 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. |
Error: Unable to start because of directory access permissions:
Secondary Journal directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when a check for Read/Write access
permissions on the directory path specified as the
Secondary Journal directory—now known as
the Duplicate Journal directory—fails. | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the Duplicate
Journal directory path resides.
TIP:
To configure the
Duplicate
Journal directory path, 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. |
Error: Unable to start because directory not specified: Primary
Restart directory configured for this computer in
FactoryTalk Directory
Batch
Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the configured path for the
Primary Restart directory—now known as
the Restart directory—is a zero length
string. | Make sure that the directory path specified is valid.
TIP:
To configure the
Restart directory path, 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. |
Error: Unable to start because directory not found: Primary
Restart directory configured for this computer in
FactoryTalk Directory
Batch
Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the directory path specified
as the Primary Restart directory—now known as
the Restart directory—cannot be found. | Make sure that the directory path specified is valid.
TIP:
To configure the
Restart directory path, 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. |
Error: Unable to start because of directory access permissions:
Primary Restart directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when a check for Write access
permission on the directory path specified as the Primary
Restart directory—now known as the
Restart directory—fails. | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the
Restart directory path resides.
TIP:
To configure the
Restart path, 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. |
Error: Unable to start because of directory access permissions
(possibly security related): Primary Restart directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when an attempt to create a test
file in the Primary Restart directory—now
known as the Restart directory—fails. | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the
Restart directory path resides.
TIP:
To configure the
Restart directory path, 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. |
Error: Unable to start because directory not found: Secondary
Restart directory configured for this computer in
FactoryTalk Directory
Batch
Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the directory path specified
as the Secondary Restart directory—now known
as the Duplicate Restart directory—cannot be
found. | Make sure that the directory path specified is valid.
TIP:
To configure the
Duplicate
Restart directory path, 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. |
Error: Unable to start because of directory access permissions:
Secondary Restart directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when a check for Write access
permission on the directory path specified as the
Secondary Restart directory—now known as the
Duplicate Restart directory—fails. | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the Duplicate
Restart directory path resides.
TIP:
To configure the
Duplicate
Restart directory path, 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. |
Error: Unable to start because of directory access permissions
(possibly security related): Secondary Restart directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when an attempt to create a test
file in the Secondary Restart directory—now
known as the Duplicate Restart
directory—fails. | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the Duplicate
Restart directory path resides.
TIP:
To configure the
Duplicate
Restart directory path, 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. |
Error: Unable to start because of nonstandard directory path
format: Primary Restart directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the directory path configured
for the Primary Restart directory—now known
as the Restart directory—uses a non-standard
path format. This may be caused by the path using double backslash
characters not at the beginning of the path (for example
C:\Dir1\\Dir2\\Dir3 ). | Make sure that the directory path specified is valid.
TIP:
To configure the
Restart directory path, 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. |
Error: Unable to start because of incorrect directory path
format: Primary Restart directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the directory path configured
for the Primary Restart directory—now known
as the Restart directory—is not a valid
path. | Make sure that the directory path specified is valid.
TIP:
To configure the
Restart directory path, 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. |
Error: Unable to start because of nonstandard directory path
format: Secondary Restart directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the directory path configured
for the Secondary Restart directory—now known
as the Duplicate Restart directory—uses a
non-standard path format. This may be caused by the path using
double backslash characters not at the beginning of the path (for
example C:\Dir1\\Dir2\\Dir3 ). | Make sure that the directory path specified is valid.
TIP:
To configure the
Duplicate
Restart directory path, 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. |
Error: Unable to start because of incorrect directory path
format: Secondary Restart directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the directory path configured
for the Secondary Restart directory—now known
as the Duplicate Restart directory—is not a
valid path. | Make sure that the directory path specified is valid.
TIP:
To configure the
Duplicate
Restart directory path, 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. |
Error: Unable to start because directory not found: Error
logging directory configured for this computer in
FactoryTalk Directory
Batch
Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the configured
Error logging directory cannot be
found. | Make sure that the directory path specified is valid.
TIP:
To configure the
Error
logging directory path, 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. |
Error: Unable to start because of directory access permissions:
Error logging directory configured for this computer in
FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the Batch Server does not have
write access permission to the configured Error
logging directory. | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the Error
logging directory path resides.
TIP:
To configure the
Error
logging directory path, 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. |
Error: Unable to start because the
BATCHSVR.LOG
file could not be created or opened. Validate the
configured Error logging path for this computer in FactoryTalk Directory
Batch
Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure message when the batch server was unable to
create the BATCHSVR.LOG file. (This error may
not be possible due to earlier error checks.) | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the Error
logging directory path resides.
TIP:
To configure the
Error
logging directory path, 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. |
Error: Unable to start due to file access permission. Log file
BATCHSVR.LOG
or VERIFY.LOG
in Error
logging directory configured for this computer in FactoryTalk Directory
Batch
Server '%s' configuration does not have write access permission.Possible cause | Solution |
|---|---|
Generated startup failure message when the batch server does not have
write access permission to the BATCHSVR.LOG or
VERIFY.LOG file. | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the Error
logging directory path resides.
TIP:
To configure the
Error
logging directory path, 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. |
Error: Unable to start because file creation denied. Unable to
create or open log file
BATCHSVR.LOG
or
VERIFY.LOG
in Error logging directory configured for this
computer in FactoryTalk Directory
Batch Server '%s' configuration.Possible cause | Solution |
|---|---|
Generated startup failure because the batch server was unable to
create or open the log file BATCHSVR.LOG or
VERIFY.LOG . | Make sure that the FactoryTalk Batch Server user has
permissions to the project folder where the Error
logging directory path resides.
TIP:
To configure the
Error
logging directory path, 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