I recently received an error message stating that the “Keyset does not exist” for all scheduled tasks on a Windows 2003 server. This error caused the scheduled tasks from not running, and caused some problems with a few applications. This is the first time I had seen the error, and so I wasn’t sure what the problem was.
While I have experienced Microsoft Word Errors in the past, this was a first for cryptography in Windows 2003. The error caused the inability to view the “Run as” user ID, let alone change it to something else. Because of this, the tasks couldn’t run, so I had to find a solution to fix it. Fortunately, the solution was easy, and only took a few minutes to implement.