MBSA and MSXML 2.6

Dear All,
MBSA is saying that I currently have MSXML 2.6 SP2, and that I should
upgrade to SP3. When I did a search on the net, not only is SP3 not
publicly available, it is also included in MS SQL 2000 SP3 that I
already have installed.
How come I am still getting these errors from MBSA despite my servers
having MS SQL 2000 SP3 installed?
Is there a way to manually check my version of MSXML 2.6?
Has anyone had a similar problem?
Thanks.
Aramid"Aramid" <aramid@.hotmail.com> wrote in message
news:63drc112j512d4dntnt2t5q3butk2v51h3@.
4ax.com...
> Dear All,
> MBSA is saying that I currently have MSXML 2.6 SP2, and that I should
> upgrade to SP3. When I did a search on the net, not only is SP3 not
> publicly available, it is also included in MS SQL 2000 SP3 that I
> already have installed.
> How come I am still getting these errors from MBSA despite my servers
> having MS SQL 2000 SP3 installed?
> Is there a way to manually check my version of MSXML 2.6?
This may seem funny but it's no joke: the only KB article I could find, for
checking the XML version called by IE was to get filemon.exe from the
SysInternals.com site, open an XML file with IE, locate the reference to
msxml?.dll in filemon output, and get its properties to check its version.
Here's the article, it's a scream:
http://support.microsoft.com/defaul...kb;en-us;296647
This one is also an interesting read, and it contains links to the how-to
for upgrading your installed parser:
http://support.microsoft.com/defaul...kb;en-us;269238
-Mark

> Has anyone had a similar problem?
> Thanks.
> Aramid

maximum width

When loading a report that another developer created, I got an error
message saying that the deserialization failed because the width value
needs to be between 0 and 85.3333 in. I was able to get around this by
opening the RDL file in notepad and changing the width values manually.
But my questions is, how was the developer able to set the width >
85.3333 if it was not allowed?Probably, the report was manually edited.
As for the 85.3 in limit - in RS 2000 SP2 it will increase to 160 in.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bucky" <uw_badgers@.mail.com> wrote in message
news:1103826459.105803.261470@.f14g2000cwb.googlegroups.com...
> When loading a report that another developer created, I got an error
> message saying that the deserialization failed because the width value
> needs to be between 0 and 85.3333 in. I was able to get around this by
> opening the RDL file in notepad and changing the width values manually.
>
> But my questions is, how was the developer able to set the width >
> 85.3333 if it was not allowed?
>