Applicable versions and levels
Windows versions: V5.0L10 or later
Action 1
Points to check
Are there privileges to execute the application?
Action method
In Windows versions, applications are executed using a local system account. Specify an application that can be executed with these execution privileges.
Action 2
Points to check
Are the path settings correct?
Action method
If the full path has been specified for the application, check if that path exists.
If the full path has not been specified for the application, check if the path in which that application exists has been set in the PATH system environment variable.
Check if the specified path contains invalid characters (for example, uppercase, lowercase, fullwidth, halfwidth).
If the execution file name extension (for example .EXE) is omitted from the definition, the program will start with ".EXE" added to the file name. To start an application with an extension other than ".EXE", specify the extension in the definition.
Action 3
Points to check
Does the application have an executable format?
Action method
To start Windows versions batch files (.bat), define as follows:
Execution file name: cmd.exe
Arguments: /C batchFile parameters
Working directory: Any
Action 4
Points to check
Has the runtime environment of the application been specified?
Action method
The application is started in the same operating environment as Systemwalker, for example by the startup user or by an environment variable. If the application to be started requires a special environment variable (library path, for example), create a batch file to start the target application, and set the required environment variable in this program.
Action 5
Check if the error message below was output. If that is the case, refer to actions 1 to 3, and then perform the appropriate procedure.
Error message
MpAosfB: ERROR: 7011: Error occurred in system function. Calling source: f3crheap.exe System function name: CreateProcess Reason: xxxxx |
Action 6
Points to check
Was the message output to the standard output or standard error output by the application to be started?
Action method
If the message was output by the application to the standard output or standard error output, enter the definition in the batch file so that the application output is redirected to another file, and set that batch file in the action definition as the execution file name for starting the application.
Action 7
Points to check
Does the definition redirect to another file the messages output by the application to be started? If that is the case, is the execution file for starting the application in the action definition correct?
Action method
Enter the definition in the batch file so that the application output is redirected to another file, and set that batch file in the action definition as the execution file name for starting the application.
Alternatively, define as follows:
Execution file name: cmd.exe
Arguments: /C applicationFullName > outFile
Action 8
Points to check
Was an application on the network drive started?
Cause
The "Systemwalker MpAosfB" service is started using a local system account, therefore a network drive cannot be used.
The "Systemwalker MpAosfB" service starts processes that execute applications.
Action method
Start an application on the local drive.
