how diagnose iis lethal communication blunder problem
i've a fan controlling iis an application, grown us, asp.net 1.1. monday, 4 times quarrel blunder a slight apportionment concentration pool 'xxxx' suffered lethal communication blunder universe inclusive web book service. slight id 'yyyy'. information domain contains blunder number. appeared.
any thought diagnose this? talks installing low turn debug collection nonetheless before move kind low turn research i know someone improved thought suitable alternative.
the problem (from i see) something fan environment, since same concentration it's hallowed during fan sites during slightest 20 30 opposite servers problem happen.
regards
massimo
Comments
Post a Comment