CryptoAPI function ''CryptAcqureContext'' failed

• Juanita

  SSCertifiable

  Points: 5300

  More actions

  October 24, 2006 at 3:17 pm

  #62220

  HI everyone,

  I have a real strange problem that occurred last week. We ended up rebooting our sql server and all is back to normal but I would like to get more information on what happened to be prepared if there is a next time.

  The scenario:

  Last week on a Tuesday around 11:00 am, all of a sudden we started getting the error: 'connection failed: sql state 28000, error:18452, login failed for user 'null'. This started on that day inconsistently but continued until a reboot was done on Thursday afternoon. Surpisingly enough, users didn't call to complain. So i think they would keep trying and finally get in.

  all was well after reboot till around 9ish on Friday morning. All users that used sql authentication to access their applications started get the following error:

  'Server: Msg 552, Level 16, State1

  [Microsoft][ODBC SQL Server Driver] [SQL Server] CryptoAPI function 'CryptAcquireContext' failed. Error 0x8009001d: Provider DLL failed to initialize correctly.

  A reboot had to be done by noon that day and all has been well since then.We run sql server 2000 standard edition on a windows nt 4 sp 6a server. I did find an article(kb 321459) referencing this kind of error but it referenced sql 2000 personal edition or sql 2000 desktop edition.

  I have no clue as to why this started and hoping somebody can give me a clue as to where to research this.

  Thanks,

  Juanita