Datastage sequence job aborted because of ExecCommand stage
As the picture shows, datastage sequence job aborted without any other error messages. The execCommand stage is to call a linux shell script. And I could run the script successfully by logging to the server as the user 'dsadm'.(By the way, I logged on datastage client as dsuser1, also having admin privileges)
Related
I am using Azure DevOps pipeline to run my automation test cases.
I am facing an issue that whenever my test run task fails, it doesn't display me the exact error that why the task failed, it just displays "cmd.exe exited with code '1' " for all test lists in the Summary section and the email.
Is there a way I can recieve the information that which test case failed and why in the summary section and email?
I have 5 cmd tasks in my pipeline, each of them has same configuraion, just the test list name is different.
There is a scheduled task that executes a script. It was running fine until one day it started to fail with 'Task Scheduler failed to start "Task" task for user "domain account". Additional Data: Error Value: 2147944309.' It failed on a Friday, ran on a Saturday, then began failing daily after that. My research on this found that 2147944309 means the account is either disabled or locked out. I double checked the account and it was neither. Server is Windows 2012. It's an RDS server so it reboots every morning. After it reboots a warning message shows in history for the task "Task Scheduler did not launch task "Task" as it missed its schedule. Consider using the configuration option to start the task when available, if schedule is missed."
What I was able to determine:
account is not locked or disabled
account is in the administrator group on the server
permissions are correct on the script
set it to run with highest privileges
able to manually kick off the task
the task is in a folder under Task Scheduler Library
created a test task to run notepad under the same account in the folder. It did not run
created a test task in a test folder under Task Scheduler Library to run notepad under the same account. It did not run
created a test task directly Task Scheduler Library to run notepad under the same account. It ran
moved the task under directly under Task Scheduler Library.
The scheduled task kicked off for four days in a row and then began failing with the same error. Yesterday, I set the option to restart every minute three times if it fails. It didn't execute a second or third time after failing. Any ideas what the heck is going with this?
I have a Deployment Group Job in a Release Pipeline where I have a step to execute an Inline powershell script. 3 out of 10 times, the step generates the following error
Windows Powershell terminated with the following error The type
initializer for
System.Management.Automation.Runspaces.InitialSessionState threw an
exception
Not only that, the error message appears to be in some weird codepage where each character is 2 bytes and the console prints a ? for the unknown byte in between each two letters.
What could be happening? These are my on-premise agent registered with Azure DevOPS.
I am creating job in SQL Agent, which will execute one TSQL Batch for shrink log file.
A also create schedule to run this job every month. After initial successful testing, I just wanted to see TSQL batch again, double click on job, choose Steps, and click on Edit step, but then I got an error:
Creating an instance of the COM component with CLSID {some guid}
from the IClassFactory failed due to the
following error: c001f011 (Microsoft.SqlServer.ManagedDTS)
Problem was, in fact, in missing some fixes to service packs.
Here is explanation:
FIX
I've been working on a system in which task scheduler is used to run few applications every night. Recently i've noticed that the tasks which i scheduled are not running and it is giving the following error message
the scheduled task did not run because an incorrect password or user name was entered
Recently i've changed the system password. Is that the reason for the task scheduler failure?
Should i change the password in the task scheduler too?
Yes you should change the password in Task Scheduler to match the password of the account it's executing code under.
If it can run with a less privileged account, I would take the opportunity to create an account with least privileges needed to complete it's work and setup Task Scheduler to use that restricted account.