Many thanks for the reply.
We have MDAC 2.6 SP2 RTM installed on this dev. server.
We were not too keen to upgrade earlier because our production servers also
run MDAC 2.6 and we wanted to keep the same environments on dev, QA and
production servers.
However, we will proceed with the upgrade and I'll post any feedback here.
It's also interesting to know how you came to the conclusion it was MDAC,
based on the IIIState dump?
Regards
"Pat [MSFT]" wrote:
> This is a bug in MDAC. Basically, the MDAC stack is contending for the CPU
> in an unhealthy way (basically bouncing around w/out making forward
> progress). Install the latest MDAC (www.microsoft.com/data) and see if that
> helps.
>
>
> Pat
>
> "Mapster" <Mapster.DeleteThis@discussions.microsoft.com> wrote in message
> news:1C57C8DB-B670-495B-AD69-2DBA696526D6@microsoft.com...
> > We run W2K Server, IIS 5.0 and SQL Server2000 and we had to kill the
> > dllhost
> > process because it was running so high on CPU - although it's not all the
> > time (more in the morning). The log file from IIState is below. Threads
> > 12-26
> > show very large kernel time and user time. Please can you help to pinpoint
> > where the problem may be:
> ><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: IIState Log file: dllhost.exe at 95% usage