This is caused by encryption issues with being able to read the Package Access Password on the Notification Server. This may be due to encryption version differences or corruption with the RSA on the local workstation. Having policies to lockout users after multiple failed attempts of login will potentially cause the AppId user to be locked on the system depending on if the AppId is being used for package delivery or not.
Locate the key container. Under Windows XP this is a file under the path (or a very similar path to)… C:\Documents and Settings\All Users.WINDOWS\Application Data\Microsoft\Crypto\RSA\MachineKeys. The particular key container file in use by Notification Server will most likely have the first 32 characters in its name as 9a0698c0f27abf0e8ffdfb7f8dd44239, followed by a GUID identifying the computer. (To be absolutely certain which key container is in use, a program like filemon can be used to see what file is being accessed in this directory when the problem occurs).
After going to C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys\ and finding a file that looked similar to this, it was found that it did not contain any data after opening it: 9a0698c0f27abf0e8ffdfb7f8dd44239_ca66f9b6-3683-424a-9035-2a6e0e08d09d.
Remove the file and then reboot the computer. A new file should be created and it should resolve the issue.
Applies To Notification Server 6.0 SP3 R2, R3, R4 CMS 6.0 and 6.1
Imported Document ID: TECH15764
Subscribing will provide email updates when this Article is updated. Login is required.