Word 2003 and Vista hanging for 30 minutes

[pclsposts]

Hi all. Happy holidays to you!

First off, I wouldn't have posted this here in the Vista group if I
didn't think it was a problem introduced by Vista.

Multiple PC's with Vista Home (with all patches) and Word 2003 (no SP)
with no patches at all. Computer Associates Security Suite. A word
file opened on these systems hangs Word for 30 minutes. Spinning Vista
ball is all we get. Eventually the file opens.

I have seen other people posting reports of this Vista and Word
conflict. With the same file the problem does not exist on an XP
computer with Word 2003 (pack and patch levels unknown).


Here is dump info if we kill the Word app instead of waiting

Description:

A problem caused this program to stop interacting with Windows.


Problem signature:

Problem Event Name: AppHangB1

Application Name: WINWORD.EXE

Application Version: 11.0.5604.0

Application Timestamp: 3f314a2f

Hang Signature: 309e

Hang Type: 0

OS Version:
6.0.6000.2.0.0.768.3

Locale ID: 1033

Additional Hang Signature 1:
6fd50df731eb6156bfa5fecf71f5329e

Additional Hang Signature 2: a1ad

Additional Hang Signature 3:
b7d6bfad2946844aedd022d70053cb8e

Additional Hang Signature 4: 309e

Additional Hang Signature 5:
6fd50df731eb6156bfa5fecf71f5329e

Additional Hang Signature 6: a1ad

Additional Hang Signature 7:
b7d6bfad2946844aedd022d70053cb8e



We have tried disabling the CA suite (antivirus section) but problem
persists.


I have tried to recreate the problem on my system here with Vista
Business (at first with no patches, then updated) and Word 2003 (no SP
no patches). Never could recreate the problem therefore I cannot fix
it :^)

I have installed Computer Associates Security Suite here , as well as
updated my Vista to all current packs. Still can't break the Vista/
Word combo here.

30 minutes to open the file but eventually it opens. What's the
timeout?

Thanks for any thoughts you can offer. I am ready to install
OpenOffice on these computers until I can find a fix..

Rich

 

[Slap]

Hi all. Happy holidays to you!

First off, I wouldn't have posted this here in the Vista group if I
didn't think it was a problem introduced by Vista.

Multiple PC's with Vista Home (with all patches) and Word 2003 (no SP)
with no patches at all.

I have seen other people posting reports of this Vista and Word
conflict. With the same file the problem does not exist on an XP
computer with Word 2003 (pack and patch levels unknown).

Rich

I've no problems with Word 2003 running under Vista. Start Word, click on
Help, click on About.

After doing that you will know what version and what service pack if any is
installed. This works for many programs by the way so you should never
again have to type in "(pack and patch levels unknown)".

Word 2003 should say SP3. If it does not go to Windows Update and get it
updated. That may fix your problem but if it doesn't you at least have a
better starting point to begin your problem solving.

--

 

[Bill Yanaire]

Did you install Office (or Word if you just have Word) with administrator
privleges? If not, uninstall Word then reinstall with as admin. You
shouldn't need to apply any service packs just to open a document. Once you
uninstall and reinstall see if this helps.

I would still update to the latest SP's on Office or Word.

 

[pclsposts]

Thanks for the thoughts Slap n Bill. I will report what the final
outcome is once we get to the bottom of it. Since the problem
originally surfaced we have seen emailed Word files that do NOT
exhibit the problem so I think the problem is likely rooted in a
missing template or something like that . Like someone created the
file with a template that is not available , and therefore Word
searches the network for days until giving up.. Thanks to Terry
Farrell - MS Word MVP for that thought.

Best to you all. I hope everyone has a wonderful 2008

Rich

 

[pclsposts]

btw, we found out that these errors were being caused by a DNS entry
in the firewall's DHCP settings.

Once we installed an SBS server at the customer site (and started
using the xxxxx.local DNS space) the problem immediately went away.

I bet the bogus DNS we used in the firewall's config was the cause. I
pinged the bogus domain name we used before we used it, to be sure it
wouldn't resolve and was really bogus......so I don't know for sure
why this happened.

But it's no longer a problem so we aren't going to break it to see if
we can fix it.

HTH someone.