Re: For XML Problem with IIS6 and W2k3

UPDATE:
the site has been stable for a week now using the SQLXMLOLEDB provider, so
I'm assuming that the problem is indeed in the SQLOLEDB files themselves.
I'm loading the MDAC 2.8 hotfixes now (from
http://support.microsoft.com/kb/838976/), after which I will switch back to
the original SQLOLEDB connection string. I'll post a followup with my
results.

//bob

"Bob Hobnob" wrote:

> Thanks for the tip, Paul. It looks like the most promising lead I've seen.
>
> As a possible workaround, I switched to the SQLXMLOLEDB provider, since this
> is a straight XML request. Although it's too soon to tell, the page has been
> stable for 3 days now, which is the longest it's gone so far without a
> freeze-up. I'm going to let it go a full week, and then I'll install the
> hotfix from Paul's KB link and switch back to the SQLOLEDB provider to test.
> I'll report my results back here.
>
> //bob
>
>
> "spamgone@xxxxxxx" wrote:
>
> > Well, my company called into Microsoft yesterday and they gave us a
> > couple of solutions. We haven't implemented any of them yet, so take
> > them with a grain of salt. The problem is that the sqlxmlx.dll is
> > unloading unexpectedly, which causes the web pages to lockup.
> >
> > There at three possible solutions.
> >
> > 1. Install the hotfix associated to this KB:
> > http://support.microsoft.com/?kbid=838976
> >
> > 2. Install the MDAC 2.8 hotfixes associated to this KB:
> > http://support.microsoft.com/?kbid=839801 (includes the above hotfix)
> >
> > 3. Install W2K3 Service Pack 1 (includes both of the above)
> >
> > I think we are going to try solution one first and go from there.
> > Again, we haven't tried them yet and since the problem doesn't happen
> > daily, when we do implement them we won't know for a while if it is
> > successful. Hopefully this helps.
> >
> > Paul
> >
> >
.