bob, is this the error that occurs before each crash? i had mentioned the other day that it could be the number of connection..but was thinking more on the db side. however, we had a similar problem (though it was with a java application, Tomcat/Apache). The problem turned out to be licensing issue...we were only licensed for a finite number of connections.
Question,
1)do you see anything about "SQLAllocHandle" preceding the "maximum connections are exceeded" error?
2) is the error "Maximum connections exceeded" or "maximum number of CONCURRENT connections exceeded"
btw, i couldn't get to the link you provided in your post