Difference between revisions of "Batch Error Handling"

From BESA® Wiki
Jump to: navigation, search
 
(3 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
|title = Module information
 
|title = Module information
 
|module = BESA Research Basic or higher
 
|module = BESA Research Basic or higher
|version = 5.2 or higher
+
|version = BESA Research 5.2 till 6.0
 +
 
 
}}
 
}}
  
Line 8: Line 9:
 
This page informs about possible issues when running batches, and how to resolve them.
 
This page informs about possible issues when running batches, and how to resolve them.
  
=== Several batches info ===
+
=== Several batches message box ===
 
If upon starting a batch the following info box appears:
 
If upon starting a batch the following info box appears:
[[File:Batch_error_1.png]]
+
[[File:Batch_error_1.png|none]]
  
 
Then it is possible that a previous instance of BESA Research has not shut down correctly, and there may still be a process of BESA Research running in the background. You can check for this by  
 
Then it is possible that a previous instance of BESA Research has not shut down correctly, and there may still be a process of BESA Research running in the background. You can check for this by  
 
* closing BESA Research
 
* closing BESA Research
* right-clicking in the task bar at the bottom of your window, and selecting the Task Manager. Select the tab "Processes" and display the background processes. There should be no background process running for BESA Research. If there is:
+
* right-clicking in the taskbar at the bottom of your window, and selecting the Task Manager. Select the tab "Processes" and display the background processes. There should be no background process running for BESA Research. However, it is likely that there are (hence the message box above). In this case:
* Either log off and on again, or  
+
** Either log off and on again, or  
* Close the BESA Research background processes in the Task Manager.
+
** Close the BESA Research background processes in the Task Manager (by right-click on the corresponding row in the Task Manager display).
  
 
Then re-start BESA Research.
 
Then re-start BESA Research.
  
 +
=== Batch error 183 ===
 +
It can occasionally happen that a batch can not be started, and informs you that the batch error 183 occurred (could not set up batch logging).
 +
The reason (and the fix) is most likely the same as described above. If not, logging off and on again (or, in the worst-case scenario, re-booting the computer) will unlock the handle to the log file.
 +
 +
'''Note''': This problem should be fixed from version 6.1 January 2017 onwards.
  
It can occasionally happen that a batch can not be started, and informs you that the batch error 183 occurred.
+
[[Category:Troubleshooting]]

Latest revision as of 15:56, 5 May 2021

Module information
Modules BESA Research Basic or higher
Version BESA Research 5.2 till 6.0

Overview

This page informs about possible issues when running batches, and how to resolve them.

Several batches message box

If upon starting a batch the following info box appears:

Batch error 1.png

Then it is possible that a previous instance of BESA Research has not shut down correctly, and there may still be a process of BESA Research running in the background. You can check for this by

  • closing BESA Research
  • right-clicking in the taskbar at the bottom of your window, and selecting the Task Manager. Select the tab "Processes" and display the background processes. There should be no background process running for BESA Research. However, it is likely that there are (hence the message box above). In this case:
    • Either log off and on again, or
    • Close the BESA Research background processes in the Task Manager (by right-click on the corresponding row in the Task Manager display).

Then re-start BESA Research.

Batch error 183

It can occasionally happen that a batch can not be started, and informs you that the batch error 183 occurred (could not set up batch logging). The reason (and the fix) is most likely the same as described above. If not, logging off and on again (or, in the worst-case scenario, re-booting the computer) will unlock the handle to the log file.

Note: This problem should be fixed from version 6.1 January 2017 onwards.