Re: Publisher 2000 Disaster

I am sorry, Syd, you find our help worthless. Norton security does block some
Office documents from opening. Disabling the Office Plug-in usually solves the
issue. I have script blocking disabled as well.
The update is not the problem, if you search the messages in this newsgroup you
will find your issue is unique when it comes to the security patch.
If you think IE7 caused your problems, then ask your questions in the Internet
Explorer newsgroup.
Have you checked the file associations to be sure Publisher is still associated
with .pub files? Were your Publisher files created from earlier versions?
--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com
http://officebeta.iponet.net/en-us/publisher/FX100649111033.aspx

<analog@xxxxxxxxxxx> wrote in message
news:oc6ql2hvra93r7ip5kj220euonm4sum96e@xxxxxxxxxx
A typical M$ response. M$ does not own Norton, so it must be the cause of all
problems with M$ programs. Of course it does cause way too many problems, but
not in this case.

The problem is a M$ update, probably KB894540. Reinstalling Office 2000 fixed
the problem, but I am still hours away from getting all the machines back to
normal and patched.

M$ tried to charge me for talking to an escalation guy in the publisher group,
but dropped that idea after presumably sensing my homicidal state of mind.
Incidentally, the case guy and the escalation guy were clueless about the
problem. At one point the escalation guy tried to give me a free copy of
Publisher 2003, totally worthless to me since I use Publisher for a large
website.

This is an inexcusable episode brought on by the release of a half-baked
security patch.

And the MVPs in here were no help at all!


On Thu, 16 Nov 2006 06:03:15 -0500, "Mary Sauer"
<mary-sauer@xxxxxxxxxxxxxxxxx>
wrote:

Check your firewall settings.

How to use Office programs with the Norton AntiVirus Office plug-in
http://support.microsoft.com/kb/329820/en-us



.

Relevant Pages

  • Re: SSL 2.0
    ... this is the classic tradeoff between compatibility and security. ... by default from Windows 2000 Server to Windows 2003 Server. ... may look at the instructions for disabling SSL3 and SSL3.5 and say ...
    (microsoft.public.inetserver.iis.security)
  • Re: Office 2003 Service Pack 3--subsequent problems opening Publis
    ... According to the description there is no known issues with the security patch. ... Vulnerability in Microsoft Publisher could allow remote code execution ... Mary Sauer MSFT MVP ... I then installed Service Pack 3 and no other updates. ...
    (microsoft.public.publisher)
  • [NT] Microsoft Publisher 2007 Arbitrary Pointer Dereference (MS07-037)
    ... Get your security news from a reliable source. ... Microsoft Publisher 2007 Arbitrary Pointer Dereference ... PUBCONV.DLL included with Microsoft's Publisher ... The vulnerability affecting Publisher 2007 is a two stage pointer ...
    (Securiteam)
  • [NT] Vulnerabilities in Microsoft Office Publisher Allows Code Execution (MS08-012)
    ... Get your security news from a reliable source. ... Vulnerabilities in Microsoft Office Publisher Allows Code Execution ... Publisher Invalid Memory Reference Vulnerability - CVE-2008-0102 ...
    (Securiteam)
  • Re: lets vote for better security
    ... Liberals and security professionals who occassionally wear a black hat. ... Then MSFT started disabling things by default and a lot of the community ... Since when is an app responsible for the ... :>: default installation and be disable-able by Group Policy. ...
    (microsoft.public.security)