View event log entry properties
From the Windows Event Viewer, double-click any log entry to display its properties.
There are 10 items for a Windows event log entry. Six of these are identical for all
FactoryTalk Batch
Server events. These items, along with a description, are listed below. The Category,
Event ID, and Description are described in the table below the list.Item | Description |
|---|---|
Date | Date that the event occurred. |
Time | Time that the event occurred. |
Type | Type of the event (that is, Information, Error, and so on). |
User | Configured domain user. |
Computer | Computer on which the FactoryTalk Batch Server is running. |
Source | BatchSvr |
Category | Category of the event. |
Event ID | ID of the event. |
Description | Description of the event. |
Data | File and line number within the FactoryTalk Batch Server source code that generated the entry. |
Category | Event ID | Description |
|---|---|---|
Start | 1000 | Server demand started successfully in demo mode. |
Start | 1001 | Server demand started successfully in production mode. |
Start | 1002 | Server auto started successfully. |
Start | 1003 | Server failed to auto start. See the Batchsvr.log file for more information. |
Start | 1004 | Server failed to demand start. See the Batchsvr.log file for more information. |
Important: Do not edit the Batchsvr.log files. The
Batchsvr.log contains critical information Technical Support must
determine the cause of a FactoryTalk Batch Server failure. | ||
Start | 1005 | Command line arguments are inconsistent. |
Start | 1006 | Unexpected command line argument [Descriptive String]. |
Start | 1007 | Service handler not installed. |
Start | 1008 | Not running as a service or StartServiceCtrlDispatcher failed. |
Start | 1009 | Log directory does not exist. Validate ErrorLogDirectory key value in Batchsvr.ini . |
Important: Do not edit the Batchsvr.ini file unless specifically instructed by Technical Support. | ||
Start | 1010 | Unable to start due to access permissions on log directory specified by ErrorLogDirectory key value in Batchsvr.ini . |
Start | 1011 | Batchsvr.log file could not be created/opened. Validate pathname in Batchsvr.ini . |
Start | 1012 | Unable to start. Log file ( Batchsvr.log or Verify.log ) does not have write access permission. |
Start | 1013 | Unable to start. Unable to access log file ( Batchsvr.log or Verify.log ). |
Start | 1014 | Unable to start. Verify.log file does not have write access permission. |
Start | 1015 | Unable to start due to missing Batchsvr.ini file. |
Start | 1016 | Unable to start due to access permissions on Batchsvr.ini file. |
Start | 1017 | Unable to start due to access problem with Batchsvr.ini file. |
Start | 1018 | Access error on Batchsvr.ini detected before logging on as user
specified in Batchsvr.ini . |
Start | 1019 | Access error on Batchsvr.ini detected while running as user specified in Batchsvr.ini . |
Start | 1020 | Access error on log file detected while running as user specified in Batchsvr.ini . |
Start | 1021 | Access error on event files detected while running as user specified in Batchsvr.ini . |
Start | 1022 | Unable to start because primary event file directory specified by
EventDirectoryPath key in Batchsvr.ini is missing. |
Start | 1023 | Unable to start because secondary event file directory specified by EventDirectoryPathSecondary key in Batchsvr.ini is missing. |
Start | 1024 | Unable to start because of access permissions on primary event file directory specified by EventDirectoryPath key in Batchsvr.ini . |
Start | 1025 | Unable to start because of access permissions on secondary event file directory specified by EventDirectoryPathSecondary key in Batchsvr.ini . |
Start | 1026 | Unable to start because of access permissions on Archque.txt file in primary event file directory. |
Start | 1027 | Unable to start because of access permissions on Archque.txt file in secondary event file directory. |
Start | 1028 | Unable to start because of access permissions on Eventdir.txt file in primary event file directory. |
Start | 1029 | Unable to start because of access permissions on Eventdir.txt file in secondary event file directory. |
Start | 1030 | Unable to start because RestartDirectoryPath key not specified in Batchsvr.ini . |
Start | 1031 | Unable to start because RestartDirectoryPath specified in Batchsvr.ini missing. |
Start | 1032 | Unable to start because of access permissions on RestartDirectoryPath specified in Batchsvr.ini . |
Start | 1033 | Unable to start because of access permissions (security?) on
RestartDirectoryPath specified in Batchsvr.ini . |
Start | 1034 | Unable to start because RestartDirectoryPath2 specified in Batchsvr.ini missing. |
Start | 1035 | Unable to start because of access permissions on RestartDirectoryPath2 specified in Batchsvr.ini . |
Start | 1036 | Unable to start because of access permissions (security) on RestartDirectoryPath2 specified in Batchsvr.ini . |
Start | 1037 | Server started by an HMI Controls client. |
Start | 1038 | Domain user name is blank and must be initialized in the SECURITY section of the Batchsvr.ini . The Server will not have any network
credentials, which means it cannot access anything off node (that is, data servers, event journal files, or recipes). |
Start | 1039 | Internal Error. Call to CoInitializeSecurity failed. |
Start | 1040 | Internal Error. Call to RegisterClassObjects failed. |
Start | 1041 | The SQL Server database cannot be opened. |
Boot | 2000 | Server warm booting. |
Boot | 2001 | Server cold booting. |
Boot | 2002 | Server started. |
Boot | 2003 | Server warm all booting. |
Boot | 3000 | Data Server: [Descriptive String] status changed to GOOD. |
Boot | 3001 | Data Server: [Descriptive String] status changed to SUSPECT. |
Boot | 3002 | Data Server: [Descriptive String] status changed to LOST. |
Boot | 3003 | Data Server: [Descriptive String] status changed to BAD. |
Boot | 3004 | Data Server: [Descriptive String] status changed to an unknown
conversation status. |
Boot | 3005 | Data Server: [Descriptive String]. |
Shutdown | 4000 | Server shutting down. |
Shutdown | 4001 | Server exception occurred. See the Batchsvr.log file for information. |
Shutdown | 4002 | Server automatically shutting down from demo mode. |
Tag_Verification | 5000 | Server tag verification process Started. |
Tag_Verification | 5001 | Server tag verification process Aborted. |
Tag_Verification | 5002 | Server tag verification completed, [Descriptive String1] of [Descriptive String2] tags verified successfully. |
Registration | 6000 | Server registered. |
Registration | 6001 | Server unregistered. |
Registration | 6002 | Server registered as a service. |
Control | 7000 | Notify SCM: The service is stopping. |
Control | 7001 | Notify SCM: Service stopped. |
Control | 7002 | Notify SCM: The service is starting. |
Control | 7003 | Notify SCM: The service is running. |
Control | 7004 | SERVICE_CONTROL_STOP received from Service Control Manager. |
Control | 7005 | Unexpected SERVICE_CONTROL_PAUSE received from Service Control Manager. |
Control | 7006 | Unexpected SERVICE_CONTROL_CONTINUE received from
Service Control Manager. |
Control | 7007 | SERVICE_CONTROL_INTERROGATE received from Service
Control Manager. |
Control | 7008 | SERVICE_CONTROL_SHUTDOWN received from Service Control Manager. |
Control | 7009 | Bad Service Request. |
Category_Debug | 8000 | Command Line: [Descriptive String]. |
Category_Debug | 8001 | Argument received from SCM or BatchSCM: [Descriptive String]. |
Category_Debug | 8002 | HRESULT = [Descriptive String]. |
Category_Debug | 8003 | Thread [Descriptive String] started. |
Category_Debug | 8004 | Exception in object [Descriptive String1] in method [Descriptive String2]. |
Category_Debug | 8005 | Service could not be marked for deletion by the SCM. |
Category_Debug | 8006 | Debug: [Descriptive String]. |
Provide Feedback