Snaphot viewer security patch - out of memory error

[Guest Tim_D]

Hi,

After applying a security patch (http://support.microsoft.com/kb/955617) to

our servers ,we found that the snapshot viewer would error with an 'Out Of

Memory' exception. We managed to roll back to the previous version of the

..ocx but what is the correct route to reporting security patch issues to

Microsoft? Looking at other posts on the internet it looks like others have

also been affected by this patch.

T

[Guest MowGreen [MVP]]

Tim,

 

http://support.microsoft.com/kb/955617

<span style="color:blue">

> How to obtain help and support for this security update

> For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and

> Canada or by contacting your local Microsoft subsidiary. For more information about how to contact

> your local Microsoft subsidiary for support issues with security updates, visit the Microsoft

> International Support Web site:

> http://support.microsoft.com/common/intern...l.aspx?rdpath=4

> North American customers can also obtain instant access to unlimited no-charge e-mail support or to

> unlimited individual chat support by visiting the following Microsoft Web site:

> http://support.microsoft.com/oas/default.aspx?&prid=7552</span>

 

Suggest first trying the email/chat support to report the issue. If no

joy, use the 'no-charge' support phone number and ask to speak to a

Level 2 tech if the initial responder appears to be 'lost'. <w>

 

MowGreen [MVP 2003-2009]

===============

-343- FDNY

Never Forgotten

===============

 

 

 

Tim_D wrote:

<span style="color:blue">

> Hi,

> After applying a security patch (http://support.microsoft.com/kb/955617) to

> our servers ,we found that the snapshot viewer would error with an 'Out Of

> Memory' exception. We managed to roll back to the previous version of the

> .ocx but what is the correct route to reporting security patch issues to

> Microsoft? Looking at other posts on the internet it looks like others have

> also been affected by this patch.

> T</span>