471,610 Members | 1,383 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,610 software developers and data experts.

XmlTextReader with Stream

CLL
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" <CL*@discussions.microsoft.com> wrote in message
news:01**********************************@microsof t.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.



Nov 12 '05 #1
1 1604
Keith,

I am really sorry again. I dont know what they mean by QFE 1641 fixes many
things, however the article number listed in the QFE is 885456. Can you try
with that?

-Amol

"CLL" <CL*@discussions.microsoft.com> wrote in message
news:AC**********************************@microsof t.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" <CL*@discussions.microsoft.com> wrote in message
news:01**********************************@microsof t.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.


Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Yuriy | last post: by
3 posts views Thread by prasad | last post: by
3 posts views Thread by Kjeld | last post: by
1 post views Thread by Nick | last post: by
reply views Thread by XML newbie: Urgent pls help! | last post: by
3 posts views Thread by g66g08d14 | last post: by
4 posts views Thread by CodeRazor | last post: by
reply views Thread by MichaelMortimer | last post: by
reply views Thread by CCCYYYY | last post: by
1 post views Thread by ZEDKYRIE | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.