I have found a critical error in 6.0.4 which sometimes starts my process with the wrong credentials. It seems to only happen after a server restart and when my job is triggered via the System Restart trigger.

This is my setup

Job (Run tasks in order)
Task1 : Run a.cmd with credentials X
Task2 : Run b.cmd with credentials Y
Task3 : Run c.cmd with credentials Y

Task3 is a .cmd file starting a .net console which logs the current credentials to a file.

Sometimes the .net console logs the X credentials, which is absolutely wrong.

Also, why is it i can choose a .bat file in the Task Execute but not a .cmd file?

Sounds strange. What is the code you use for logging the credential?

---

String name = WindowsIdentity.GetCurrent().Name;

And you use the "With profile" option and "API" mode?

---

Yes. Logon type: With profile

and "Run with API code"

And you run the service as SYSTEM?

---

VisualCron "Log On As" = "Local System"

X and Y are both domain users and the server is Windows Server 2008 R2

1. And this is a background Job?
2. it happens every time you use the Server startup Trigger?

---

Changed Task1 and still see the wrong credentials!

Job (Run tasks in order)
Task1 : Run a.cmd with no credentials
Task2 : Run b.cmd with credentials Y
Task3 : Run c.cmd with credentials Y

1) Yes
2) I'm not sure yet.

Hmm..I would say that the probability that the wrong Credential is actually picked up is zero. This sounds more like the Credential that was initially used won't go away.

I presume restarting the service resets the state. We will do some tests.

---

Wait a minute. I see a problem in my setup. I'll write back today.

Stig

I'm very sorry, but I forgot to disable an old Task Scheduler job which was the reason to the odd behaviour.

Thanks

Stig

You are welcome to delete this post.

Stig

Ok, great that it was a natural reason 😁

---