Hi All,
I have a couple of cyclic jobs that are failing intermittently with a fork failure.
We are running 6.4.01 on Windows and the agent server is Windows 2003.
The jobs are running something like -
Cscript D:\apps\bob\fred.vbs ukmail.bert.status
Sometimes it works and sometimes it doesn't!
The owner account has the correct permissions to cmd.exe and the language settings are English UK.
Any ideas please?
JOB FAILED TO EXECUTE DUE TO FORK FAILURE
-
rahulsehgal
- Nouveau
- Posts: 148
- Joined: 19 Mar 2009 12:00
- Location: Delhi
- Contact:
Hi,
Please check this post:-
http://www.scheduler-usage.com/modules. ... opic&t=660
regards,
Rahul Sehgal
Please check this post:-
http://www.scheduler-usage.com/modules. ... opic&t=660
regards,
Rahul Sehgal
Which part of it? As I said, the cmd.exe permissions are ok and the language/regional settings are standard.rahulsehgal wrote:Hi,
Please check this post:-
http://www.scheduler-usage.com/modules. ... opic&t=660
regards,
Rahul Sehgal
-
rahulsehgal
- Nouveau
- Posts: 148
- Joined: 19 Mar 2009 12:00
- Location: Delhi
- Contact:
The "Logon as user" should be unchecked on the agent side, please check if it is unchecked?
Also follow these steps:-
Try changing the properties of the Control-M agent service "log on" tab to the user/password, restart the service and rerun the job. If this works, then the system account is not authorized to run the job and there are a few things that can be done.
A.) For those jobs that require more then system permissions and need to be added to the agent password list use the utility “ctmpwd” (or ctmcpt depending on the version) and adjust the local policies. The policies that need the user account added are:
Act as part of the Operating System
Debug Program
Increase Quotas
Logon as Batch job
Logon as service
Replace process level token
This information can be found in the PDF Control-M Agent for Windows Administrator Guide (pg 20).
To remove a user, go to the ctmagent home directory /DATA and locate the passwrds.dat file and remove the line for that user.
B.) The setting in the services "log on" tab can remain, but all jobs executed using this agent will run as that user.
C.) Create a generic local admin account and set the service to run as that account.
'mode' is not recognized as an internal or external command, operable program or batch file. This is one of those gotcha's of the control-m agent on windows. The solution for this silly little sysout message (that doesn't actually affect the job) is to simply copy the "mode.com" file from the c:\windows\system32 directory to the control-m agents home\EXE directory.
Also follow these steps:-
Try changing the properties of the Control-M agent service "log on" tab to the user/password, restart the service and rerun the job. If this works, then the system account is not authorized to run the job and there are a few things that can be done.
A.) For those jobs that require more then system permissions and need to be added to the agent password list use the utility “ctmpwd” (or ctmcpt depending on the version) and adjust the local policies. The policies that need the user account added are:
Act as part of the Operating System
Debug Program
Increase Quotas
Logon as Batch job
Logon as service
Replace process level token
This information can be found in the PDF Control-M Agent for Windows Administrator Guide (pg 20).
To remove a user, go to the ctmagent home directory /DATA and locate the passwrds.dat file and remove the line for that user.
B.) The setting in the services "log on" tab can remain, but all jobs executed using this agent will run as that user.
C.) Create a generic local admin account and set the service to run as that account.
'mode' is not recognized as an internal or external command, operable program or batch file. This is one of those gotcha's of the control-m agent on windows. The solution for this silly little sysout message (that doesn't actually affect the job) is to simply copy the "mode.com" file from the c:\windows\system32 directory to the control-m agents home\EXE directory.