Folks,
This seems to be a known issue. Folks from eJungle and Treefort have encountered this on both Windows Server 2008 and Windows Server 2003 operating systems. I tried contacting nSoftware on this and this is the response I got:
I see. There may be an issue here, but I'm not aware of it. We've actually moved to a new version in release (V4) but I'd also suggest trying the latest version of V3 on this system since the version you have is a bit older. You can find the latest version of V3 here:
http://www.nsoftware.com/download/?filter=retired (about 3/4 of the way down the page).
As for converting to a PFX you can either use OpenSSL to do this if you have that, or I can convert it here, or you can use other tools out there like
Crypto4 PKI (http://www.brothersoft.com/crypto4-pki-39633.html) to do this.
As for the file lock on the file after you started seeing the new error I'm not sure why that would happen. That is something we'd have to investigate separately.
If you keep running into problems I can send you a trial version of V4 (the latest version) to test as that should definitely not have any problems with PEM keys in Server 2008.
There are really 2 problems here:
1. The first time you try to do a CC transaction, the pem file is not completely read. Because of this it throws an error.
2. If you immediately try to process further CC transactions, they will fail with a different error. Thats because the first operation locked the pem file and further processes are not able to read the pem file because its locked by another process. SO you will get a different error message.
NSoftware Tech Support doesnt know why this occurs and how to fix it. The only solution I got from them was to upgrade to the latest version.
However, this does not happen on all servers. I am not sure as to what causes this problem. If anybody has figured out a solution, please post. As I said before, this does not seem to be an issue with BV as such.