Re: Warning: Beware of Office 2003 Service Pack 3

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm not sure these are 'bugs' though, in the traditional sense. My understanding was this is a "known issue", hence the release notes and kb's available at the SP release.

Obviously, not all of the issues are known ;-).

You might have to do a community KB when you get it sorted, Gary.

--
Les Connor [SBS MVP]


"Gary Karasik" <gkarasik@xxxxxxx> wrote in message news:%23VFbVJV$HHA.5360@xxxxxxxxxxxxxxxxxxxxxxx
'Tis the nature of bugs. Often unpredictable. One clue to my problems is that none of the reg keys that the upgrades were supposed to install and that the KBs cite for fixes (eg HKLM/Software/Microsoft/Office/11.0/Word/Securyity/FileBlockOpen) are in any of my systems. Adding them seems to help, and I am in the process of creating them, then exporting them and consolidating them into a single reg file for merging into other systems to speed up the fixing process.

--

GaryK


"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message news:8C088691-AE43-451F-9ADE-3FCF38B0889D@xxxxxxxxxxxxxxxx
Yeah, I saw the release notes/warnings, and was expecting issues so installed the update on one network and then went ghostbusting. I was surprised I couldn't find the problem, especially after looking at your post.

--
Les Connor [SBS MVP]


"Gary Karasik" <gkarasik@xxxxxxx> wrote in message news:OCgBhWN$HHA.3940@xxxxxxxxxxxxxxxxxxxxxxx
Wish I could say that. OTOH, it's not just me--lots of MSKB articles about this one.

--

GaryK


"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message news:71510819-05A8-44F9-98DD-A4107CB9A5D4@xxxxxxxxxxxxxxxx
I tried to find a file I couldn't open. The oldest files I could easily find were created in 1997, but I'm not sure with which version of Office.

The files all opened without error (word/excel).

--
Les Connor [SBS MVP]


"Gary Karasik" <gkarasik@xxxxxxx> wrote in message news:O2OZj0K$HHA.4732@xxxxxxxxxxxxxxxxxxxxxxx
How old of versions of files are these?

Office 2000.

Is this a mixed network of 2002/2000/xp Office versions?
No. Everything is O2K3Pro. Which makes the "find a machine with an earler
version of Office loaded" workaround a bit problematic. The other suggestion
I've gotten so far from the managed NG is to use an "exempt folder." Works,
but is extremely cumbersome. MS just have their heads up their butts on this
one.

Do report back as all this 'should' be doing is bringing up Office 2003 in
line with 2007 and I can open older files just fine.
Wish I could say that. This is causing a special problem with pre-Office
2003 Word and Excel files attached to Outlook emails. For instance, one
client has a bank that sends a credit-card account file to an internal
distribution list. No one can open the file. So someone has to save it to
the exempt directory, open it, save it in Word 2003, then redistribute it.
Very annoying to my client. And she doesn't feel like telling Bank of
America to upgrade it's Office version.

--

GaryK


"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
wrote in message news:%23pWudnK$HHA.3716@xxxxxxxxxxxxxxxxxxxxxxx
And I've seen reports from folks with no issues.

How old of versions of files are these?
Is this a mixed network of 2002/2000/xp Office versions?

Do report back as all this 'should' be doing is bringing up Office 2003 in
line with 2007 and I can open older files just fine.

Gary Karasik wrote:
Including the registry edits in the associated KB 938810 that goes into
the specific details of which file types are blocked?


Correct, Steve. They do not work.












.

Quantcast