Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Bill Walsh (bwalshWYNTRAC.COM)
Date: Wed Mar 14 2001 - 15:18:04 CST
I debated whether or not this was the correct mailing list, but SSL
implementation regarding NT/2000 systems problems and bugs is definitely a
topic for the Focus-MS list..
I've run into a strange problem with the importing of an SSL certificate on
my Win2000 Server web server.. The certificate is a Verisign certificate
saved in a .PFX file. It imports successfully, and I enter 443 as the port
for SSL in the MMC site properties, but https://sitename will not work..
I am getting the following errors in the Event Log for the web server:
Event ID: 36871
A fatal error occurred while creating an SSL server credential.
I looked it up on the KB, here is the article referencing this:
As an aside, after reading the KB article, I think it's absolutely
ridiculous that MS will not release this patch to the public unless you call
them and possibly pay $250 for a support call.. this is a load of baloney.
I checked the version number of my crypt32.dll that's on the server,
installed from Win2000 SP1, and it's 5.131.2195.1340, which is earlier than
the version referenced in the hotfix from the KB article..
So, has anyone else run into this problem, or found a way around this
implementation bug/problem? Does anyone actually have this patch that I
could swipe it from and see if this is what I'm dealing with?
I would rather not pay another $100 to have the key reissued from Verisign,
and I sure as hell am not going to gamble with a $250 support call to have
MS give me a patch they should make publicly available. I'm a bit