"CLL" <CLL@discussions.microsoft.com> wrote in message
news:0109CAFA-00B7-4E3B-9582-1FA3B51DC6CB@microsoft.com...
> All,
>
> I have been following this thread for some time now. Recently I found
that
> in 2 seperate posts, the MSFT employees responded as there was a QFE to
fix
> this problem. All you need to do is contact PSS.
>
> I was like great, so I contacted them. Then they asked for a kb article
> number (not provided in the post) how about a QFE number? again, not
> provided in the post.
>
> So I am querying now...
>
> What is either A) the kb article number I can give to PSS or B) the QFE
> number I can provide to PSS.
>
> Just an FYI when I called PSS and gave them what I thought was the kb
> article (I later found out this was the kb for what broke the
XmlTextReader),
> they then told me that there currently is no work around for this and they
> are working on a fix. This is a problem. From one side we are getting
told
> there is a QFE (and having them leave out vital information like a product
> number) and on the other hand we are getting told that a QFE does not yet
> exist.
>
> Which is it? If the QFE exists, please provide a number so I can get the
> fix from PSS.
>

"CLL" <CLL@discussions.microsoft.com> wrote in message
news:ACE1BD53-A801-4704-99FB-FCC0E0D30ACD@microsoft.com...
> Sorry about creating a new post, but my old one is 3 pages down and the
older
> posts don't seem to get answered very often. (original post at the bottom)
>
> I called PSS about the QFE fix and gave them the number provided below and
> they told me I need an article number because QFE 1641 fixes many things
and
> the XmlTextReader problem that I described to them wasn't one of them.
>
> Is there an article number I can provide to the PSS team?
>
> Thanks,
>
> Keith
>
>
> I am replying to the following post:
>
> Sorry about the confusion/delay. The QFE number for this problem is 1641.
> Use that for your future reference.
>
> Thanks,
> Amol
>
> "CLL" <CLL@discussions.microsoft.com> wrote in message
> news:0109CAFA-00B7-4E3B-9582-1FA3B51DC6CB@microsoft.com...
> > All,
> >
> > I have been following this thread for some time now. Recently I found
> that
> > in 2 seperate posts, the MSFT employees responded as there was a QFE to
> fix
> > this problem. All you need to do is contact PSS.
> >
> > I was like great, so I contacted them. Then they asked for a kb article
> > number (not provided in the post) how about a QFE number? again, not
> > provided in the post.
> >
> > So I am querying now...
> >
> > What is either A) the kb article number I can give to PSS or B) the QFE
> > number I can provide to PSS.
> >
> > Just an FYI when I called PSS and gave them what I thought was the kb
> > article (I later found out this was the kb for what broke the
> XmlTextReader),
> > they then told me that there currently is no work around for this and
they
> > are working on a fix. This is a problem. From one side we are getting
> told
> > there is a QFE (and having them leave out vital information like a
product
> > number) and on the other hand we are getting told that a QFE does not
yet
> > exist.
> >
> > Which is it? If the QFE exists, please provide a number so I can get
the
> > fix from PSS.
> >
>
>
>
>