bug: Getting an Application Error when trying to set up this application to run in windows task scheduler. I am wanting to run your application weekly on the server

[tysonsearls]

Bug Report

1.0.6.0

Current behavior:

Getting an Windows Application Error when trying to set up this application to run in windows task scheduler. It never fully runs in task scheduler and I get a Windows Application Error in the logs:

Faulting application name: AzureDevOpsBackup.exe, version: 1.0.6.0, time stamp: 0xf9244bba
Faulting module name: clr.dll, version: 4.8.4729.0, time stamp: 0x6614c017
Exception code: 0xc00000fd
Fault offset: 0x000000000005ee02
Faulting process id: 0x1dc0
Faulting application start time: 0x01daea744d4837ab
Faulting application path: C:\Program Files\Azure DevOps Backup\1.0.6.0\AzureDevOpsBackup\AzureDevOpsBackup.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 3d999ce7-0033-45e5-bbc6-c63665a214ca
Faulting package full name:
Faulting package-relative application ID:

With some google searching it looks like a clr.dll with a exception code 0xc00000fd is a stack overflow
https://stackoverflow.com/questions/11465674/how-to-solve-stopped-windows-service-clr-dll-error

Expected behavior:

This is a console application. This should normally be able to run without issue using Task Scheduler.
All I am doing in Task Scheduler is under action tab running the exe under "program/script" with the "Add arguments" with the regular arguments that work in a command prompt

Steps to reproduce:

set up your application to run in task scheduler, it will finish with in seconds and send an application error to windows application logs.

Related code:

insert short code snippets here

Other information:

Sorry to find issues with your app. It would really help us out with disaster preparedness if I could run it in a scheduled task once a week. You app would be perfect for our needs. Thanks for your help - Tyson

[michaelmsonne]

Hi @tysonsearls ,

Hmm strange - worked here for a long time on my Windows Server 2022...

My taks here is setup like this:

Program/Script: "D:\Microsoft\Azure DevOps\AzureDevOpsBackup.exe"

Arguments: .\AzureDevOpsBackup.exe --token "token.bin" --org "Sonnes" --backup "D:\Backup\Azure DevOps" --server "xxxxxxcloud.mail.protection.outlook.com" --port "25" --from "[email protected]" --to "[email protected]" --unzip --cleanup --daystokeepbackup 180

Start in: D:\Microsoft\Azure DevOps

How is your setup, also with the permisions to the folder it runs on - as the AzureDevOpsBackup.exe creates the logs in the folder .\Logs behind it (as it is now)

[michaelmsonne]

The updated readme file is updated with this too :)

[tysonsearls]

It was permissions to write to the logs file. It is working now. Thanks!

[michaelmsonne]

Good to hear it´s fixed @tysonsearls ;)

I will update the README a bit with some information like around this - the error handling (and in the logs) should note it around the "UnauthorizedAccessException" in the code in general when saveing backups.

But I see here https://github.com/michaelmsonne/AzureDevOpsBackupTool/blob/master/AzureDevOpsBackup/Class/FileLogger.cs#L75 that its missing here - will add it :)