IIS Catastrophic failure

[raton]

Hello all,

We run quite a busy web-based application in Finland and we use easyCrypt for decrypting link data we get from our partners (finnish bank association standard mechanism for moving between sites).

After few weeks easyCrypt gives us error 0x8000FFFF with description "Catastrophic failure". This happens at line:

Crypt.Algorithm = csHash_MD5

after:

Set Crypt = server.createobject("aspCrypt.EasyCRYPT")

After IIS restart, everything works ok, but we're not so happy booting our production servers daytime.. I googled a bit but could'nt found anything useful. We upgraded from 1.x to 2.10 a month ago or so, but it didn't help.

Any pointers? We are running W2k with IIS5. We haven't had any problems in our other components, just this one. We may be getting about 2000 hits for that file per day.

[John]

Seems to be a memory leak on aspEasyCrypt but to make sure we need to get more information.

Does the memory increase? And for the IIS service?

How many hits is stable? ( 2000 hits per day x N days )

Please send this information to support@mitdata.net or reply this post.

[raton]

The memory increases slowly yes, but I'm not sure is it because of this Process is dllhost.exe. Last time all were ok for about a month (08.04.2006 -> 02.05.2006 dd.mm.yyyy) with ~2000 hits/day.

I made a little test script:

<%

const csHash_MD5 = 1
const HashString= 0
const fmtHEX = 1

Set Crypt = server.createobject("aspCrypt.EasyCRYPT")

StringToHash = "jotain " & Now()
Crypt.Algorithm = csHash_MD5
Crypt.Hash StringToHash, HashString
HashResultHex = Crypt.Digest(fmtHex)

Response.Write HashResultHex & "<br>"

Set Crypt = Nothing

%>

.. and ran it about 100 000 times with http_load. Memory usage slowly grew to about 300MB. Few times IIS had probelms:

"
Out of process application '/LM/W3SVC/4/Root' terminated unexpectedly.
For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp
"

and switced dllhost.exe process in the middle. But otherwise I couldn't get the same exact error happen like in our production servers.

Does this help at all?