View Single Post
Old October 20th, 2006, 10:46 AM
ckendellen ckendellen is offline
Registered User
Join Date: Oct 2006
Location: Dublin, , Ireland.
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts

I have found the exact same problem. The wierd thing is the error only occurred when the website was running in the default application pool. As soon as the script was taken out and put into a website in a dedicated app pool it ran fine every time. Not sure if creating a new app pool is a likely option for you?

Also did some 'cleaning' int he default app pool and halved the memory footprint and the script then ran successfully everytime (as far as I could count anyway!). So this problem may indicate wider reaching problems.

Did you find any solution/kb?

Hope this helps!

"What we have to learn to do we learn by doing."

Aristotle 351 BC