GCDS Scheduled task suddenly stopped working

[fiza]

We have successfully been using GCDS in a scheduled task to run every night for almost 6 years.

Suddenly we have found that the task now fails and we have not made any changes.

Running the task gives "No Config Specified - No Configuration file is specified. You cannot perform explicit command line actions without a valid configuration file"

 

The config file has not been changed or moved. It just doesn't make any sense why it would suddenly stop working.

 

Running GCDS manually works fine. It is just the scheduled task with the sync-cmd

 

We have also updated to the latest version of GCDS with no joy.

 

 

Any ideas please?

[Randomperson123]

Did you ever find out what the issue was with the GCDS task scheduler not running? We are having the same exact issue. Nothing has been changed that would cause this issue to happen. If we run it manually it's fine. We have been trying to fix this the last few months and nothing has worked.

[Jaan]

Nothing to do with this is it?

 

https://workspaceupdates.googleblog.com/2023/09/winding-down-google-sync-and-less-secure-apps-support.html

[fiza]

Did you ever find out what the issue was with the GCDS task scheduler not running? We are having the same exact issue. Nothing has been changed that would cause this issue to happen. If we run it manually it's fine. We have been trying to fix this the last few months and nothing has worked.

 

Unfortunately I don’t remember how we resolved it and I no longer work at that school. @DeGrimmy may remember.

[DeGrimmy]

Did you ever find out what the issue was with the GCDS task scheduler not running? We are having the same exact issue. Nothing has been changed that would cause this issue to happen. If we run it manually it's fine. We have been trying to fix this the last few months and nothing has worked.

 

Unfortunately I don’t remember how we resolved it and I no longer work at that school. @DeGrimmy may remember.

I'm afraid I don't remember this particular instance either, sorry. We've since had problems with task scheduler jobs not recognising that the user running them has the Batch Job access in the Local Security Policy on the server. Does it come up with any errors when you look at the job history in the Task Scheduler?