从Windows Task Scheduler运行控制台应用程序时遇到CryptographicException

Question

I'm deploying a console app which gathers data on a user base and sends emails to our support team. There is a spreadsheet to read for which Google Spreadsheet Service is employed, therefore the corresponding class opens with the following lines:

const string serviceAccountEmail = "someemailaddresss";

var cert = new X509Certificate2(@"key.p12", "abigsecret", X509KeyStorageFlags.Exportable);

        var credential = new ServiceAccountCredential(
            new ServiceAccountCredential.Initializer(serviceAccountEmail) {
                Scopes = new[] { "https://spreadsheets.google.com/feeds" }
            }.FromCertificate(cert));

I did not have any problems running it locally, nor were there issues when manually launching the executable on the AWS deployment machine. Now this task is to be automated and therefore was set up using Windows Task Scheduler, where it fails with the stack trace below.

Description: The process was terminated due to an unhandled exception.
Exception Info: System.Security.Cryptography.CryptographicException
   at System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32)
   at System.Security.Cryptography.X509Certificates.X509Utils._QueryCertFileType(System.String)
   at System.Security.Cryptography.X509Certificates.X509Certificate.LoadCertificateFromFile(System.String, System.Object, System.Security.Cryptography.X509Certificates.X509KeyStorageFlags)
   at System.Security.Cryptography.X509Certificates.X509Certificate2..ctor(System.String, System.String, System.Security.Cryptography.X509Certificates.X509KeyStorageFlags)
   at (hidden).GoogleSpreadsheetReader.ReadBrokerList(System.String)
   at (hidden).Console.ReportEntryPoint..ctor()
   at (hidden).Console.ReportEntryPoint.Main(System.String[])

I have found answers which pertain to similar errors within web applications where the answer is to properly load the user profile for the app pool within IIS to enable the crypto subsystem. This however is a console app. Would could be the solution?

Answer 1

And here was the actual solution: While configuring the task in Task Scheduler, indicating the exe directory under "start in" in the Actions tab fixed the issue. Even though "start in" is marked as an optional field and the path to the executable was obviously initially provided.