Word 2002 and Open Office Writer Open Command Crashes App

"Peter Foldes" wrote:

> Which Office newsgroup did you post this to. I am there in most but I have not seen > your post. Can you tell me the Office group where you posted to. Thank you

Here's the link:
http://www.microsoft.com/communities...e-3e581a42c38c

"Andrew McLaren" wrote:

> Another thought ... you should also check in the "Problem Reports and
> Solutions" applet in Control Panel. Go to Control Panel, "Problem Reports
> and Solutions"m, and select the "View problem history" option. See if Office
> or OpenOffice are mentioned in any of the logged problems. If so,
> double-click on the problem to get module names and error codes (and report
> back here with details).
>
> Typically, problems are logged here only when an application crashes (in th
> strict technical sense). Unresponsive apps, and hung apps do not activate
> the operating system's exception handling mechanism, so they are harder to
> detect and log.

I will be back in the office tomorrow, so I will check out all the things
you have suggested and report back with any relevant error messages if I can
locate them. Thanks for the help.

Have you tried what Garfield-n-odie MVP for Office suggested as below

>In Windows Vista, click Start | Computer | Tools | Disconnect Network
>Drive. If you don't see the Tools menu, press ALT. Click the drive
>that you want to disconnect from, and then click OK.

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Fwedfwelldown" <Fwedfwelldown@discussions.microsoft.com> wrote in message news:BA91C860-024C-41D0-92B0-27EABB041022@microsoft.com...
>
>
> "Peter Foldes" wrote:
>
>> Which Office newsgroup did you post this to. I am there in most but I have not seen > your post. Can you tell me the Office group where you posted to. Thank you
>
> Here's the link:
> http://www.microsoft.com/communities...e-3e581a42c38c

"Peter Foldes" wrote:

> Have you tried what Garfield-n-odie MVP for Office suggested as below

I don't have access to the machine at the moment, but I will be trying
everything everyone has suggested when I'm at my office tomorrow. I'll post
back here to let everyone know if the problem is solved, and if not, I'll
come bearing more details from the error logs.

All the suggestions have been greatly appreciated.

"Andrew McLaren" wrote:

> Another thought ... you should also check in the "Problem Reports and
> Solutions" applet in Control Panel. Go to Control Panel, "Problem Reports
> and Solutions"m, and select the "View problem history" option. See if Office
> or OpenOffice are mentioned in any of the logged problems. If so,
> double-click on the problem to get module names and error codes (and report
> back here with details).

OK, I've made a bit of progress and found the culprit. Here's the problem
report I pulled up under Problem Reports and Solutions.

Problem signature
Problem Event Name: APPCRASH
Application Name: WINWORD.EXE
Application Version: 10.0.2627.0
Application Timestamp: 3a9cdbe7
Fault Module Name: PROPSYS.dll
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bd96
Exception Code: c0000005
Exception Offset: 0000a8f9
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033


The villain is PROPSYS.dll

I haven't figured out how to fix it yet.

I have tried uninstalling Office XP and Open Office and then reinstalling
only Office XP as you suggested, but I still have the same problem with it.

I brought the computer home today so I could use my broadband connection.
I'm currently downloading all the updates to Vista that Microsoft says I
need. We'll see if that does anything.

> The villain is PROPSYS.dll
>
> I haven't figured out how to fix it yet.
>
> I have tried uninstalling Office XP and Open Office and then reinstalling
> only Office XP as you suggested, but I still have the same problem with it.
>
> I brought the computer home today so I could use my broadband connection.
> I'm currently downloading all the updates to Vista that Microsoft says I
> need. We'll see if that does anything.

Now I've done all that.. I actually ran Windows Update about six times,
until it finally quit finding updates. I installed every one..and it's still
doing the same thing.

"Fwedfwelldown" <Fwedfwelldown@discussions.microsoft.com> wrote ...
>
> Problem Event Name: APPCRASH
> Application Name: WINWORD.EXE
> Application Version: 10.0.2627.0
> Fault Module Name: PROPSYS.dll
> Fault Module Version: 6.0.6000.16386
> Exception Code: c0000005

Okay, so now we know it is an Access Violation (0xC0000005) in Winword.exe.

("access violation" is nothing to do with security, it's an improper memory
reference - a process tried to touch an area of memory it cannot access)

> The villain is PROPSYS.dll

PROPSYS.DLL is one of the files from the Windows Explorer shell - it handles
COM calls from GUI applications to get file properties. There's probably
nothing wrong with the binary image of this file itself. Rather, something
is calling one of PROPSYS's exported functions with a bad parameter, thus
causing the access violation. Either one of the DLLs lower down in the
call-stack is bad, or there is a problem in the runtime enviornment.

It's one of those problems which would be fairly easy for a skilled computer
technician to solve, by slapping a debugger onto the machine and capturing
the crash. However, I can't quite reach your keyboard, from over here where
I'm sitting :-)

The only short-term remedy I can think of now is to re-register PROPSYS.DLL,
in case its COM registration has been damaged:
- find Command Prompt in the Start menu
- right-click the Command Prompt menu item and select "Run as Administrator"
- enter Administrator credentials
- at a command prompt, cd to C:\Windows\System32
- run this command: "regsvr32 propsys.dll"
- you should get the response "DllRegisterServer in propsys.dll succeeded"
- log out and log in again, to restart the Shell process (no need to reboot,
as such)
- Run Word and try to open a file.

If that doesn't fix it, I think you'll need to take the problem to a forum
which specialises in Word issues. Yes: Word is crashing in an Operating
System supplied DLL; but the actual process which is crashing is
Winword.exe; and clearly, this is not any kind of "well-known problem" in
Vista which causes Word users the world over to crash. Any debugging will
focus on the Winword process. Office experts would have a better idea how
PROPSYS.DLL sits in the Word process space.

Alternatively - and I know this is an ugly solution, but it should restore
availability - back up your user data, reformat the C: drive, re-install
Vista from scratch, and then re-install Office XP from scratch. We know that
a clean install of Office XP on Windows Vista is officially supported by
Microsoft, and should work reliably. Once you have verified that works
correctly, make a full system backup so you can easily get back to this
"known good" configuration. Then add your other apps etc, one by one, making
sure that File, Open continues to work after each major system change.

Hope it helps a bit,
Andrew

posted to the word.application.errors via crosspost


"Fwedfwelldown" <Fwedfwelldown@discussions.microsoft.com> wrote in message news:53CF6E62-EC47-4A9F-A479-275387AFBA25@microsoft.com...
>
>
>
> OK, I've made a bit of progress and found the culprit. Here's the problem
> report I pulled up under Problem Reports and Solutions.
>
> Problem signature
> Problem Event Name: APPCRASH
> Application Name: WINWORD.EXE
> Application Version: 10.0.2627.0
> Application Timestamp: 3a9cdbe7
> Fault Module Name: PROPSYS.dll
> Fault Module Version: 6.0.6000.16386
> Fault Module Timestamp: 4549bd96
> Exception Code: c0000005
> Exception Offset: 0000a8f9
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
>
> The villain is PROPSYS.dll
>
> I haven't figured out how to fix it yet.
>
> I have tried uninstalling Office XP and Open Office and then reinstalling
> only Office XP as you suggested, but I still have the same problem with it.
>
> I brought the computer home today so I could use my broadband connection.
> I'm currently downloading all the updates to Vista that Microsoft says I
> need. We'll see if that does anything.

This MSKB article may be a solution.

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

--
Terry Farrell - MS Word MVP

"Peter Foldes" <okf22@hotmail.com> wrote in message
news:%234SnsjRvHHA.3444@TK2MSFTNGP04.phx.gbl...
posted to the word.application.errors via crosspost


"Fwedfwelldown" <Fwedfwelldown@discussions.microsoft.com> wrote in message
news:53CF6E62-EC47-4A9F-A479-275387AFBA25@microsoft.com...
>
>
>
> OK, I've made a bit of progress and found the culprit. Here's the problem
> report I pulled up under Problem Reports and Solutions.
>
> Problem signature
> Problem Event Name: APPCRASH
> Application Name: WINWORD.EXE
> Application Version: 10.0.2627.0
> Application Timestamp: 3a9cdbe7
> Fault Module Name: PROPSYS.dll
> Fault Module Version: 6.0.6000.16386
> Fault Module Timestamp: 4549bd96
> Exception Code: c0000005
> Exception Offset: 0000a8f9
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
>
> The villain is PROPSYS.dll
>
> I haven't figured out how to fix it yet.
>
> I have tried uninstalling Office XP and Open Office and then reinstalling
> only Office XP as you suggested, but I still have the same problem with
> it.
>
> I brought the computer home today so I could use my broadband connection.
> I'm currently downloading all the updates to Vista that Microsoft says I
> need. We'll see if that does anything.

And this post resolved some problems for anyone?

Terry

"SMHealthNick" <SMHealth@gmail.com> wrote in message
news:1183488326.174665.56120@a26g2000pre.googlegro ups.com...
> On Jul 3, 1:50 am, "Terry Farrell" <terryfarr...@msn.com> wrote:
>> This MSKB article may be a solution.
>>
>> http://support.microsoft.com/kb/928149
>>
>> --
>> Terry Farrell - MS Word MVP
>>
>> "Peter Foldes" <o...@hotmail.com> wrote in message
>>
>> news:%234SnsjRvHHA.3444@TK2MSFTNGP04.phx.gbl...
>> posted to the word.application.errors via crosspost
>>
>> "Fwedfwelldown" <Fwedfwelld...@discussions.microsoft.com> wrote in
>> message
>>
>> news:53CF6E62-EC47-4A9F-A479-275387AFBA25@microsoft.com...
>>
>>
>>
>>
>>
>> > OK, I've made a bit of progress and found the culprit. Here's the
>> > problem
>> > report I pulled up under Problem Reports and Solutions.
>>
>> > Problem signature
>> > Problem Event Name: APPCRASH
>> > Application Name: WINWORD.EXE
>> > Application Version: 10.0.2627.0
>> > Application Timestamp: 3a9cdbe7
>> > Fault Module Name: PROPSYS.dll
>> > Fault Module Version: 6.0.6000.16386
>> > Fault Module Timestamp: 4549bd96
>> > Exception Code: c0000005
>> > Exception Offset: 0000a8f9
>> > OS Version: 6.0.6000.2.0.0.768.3
>> > Locale ID: 1033
>>
>> > The villain is PROPSYS.dll
>>
>> > I haven't figured out how to fix it yet.
>>
>> > I have tried uninstalling Office XP and Open Office and then
>> > reinstalling
>> > only Office XP as you suggested, but I still have the same problem with
>> > it.
>>
>> > I brought the computer home today so I could use my broadband
>> > connection.
>> > I'm currently downloading all the updates to Vista that Microsoft says
>> > I
>> > need. We'll see if that does anything.- Hide quoted text -
>>
>> - Show quoted text -
>
> You know what? It's just way way way too late in the history of
> personal computers for people to have to screw with this sort of
> thing. Ten years ago Bill Gates was talking about applicance
> computers. They turn on instantly, are as reliable as your
> television, never blue screen. It hasn't happened. Some kind of
> weird freaks must have hijacked development at Microsoft. They had 5
> years and gigabucks to make Windows work better. Instead they made it
> work worse.
>
> If the early eighties Microsoft release of DOS 3.0 and the early
> nineties release of Windows 3.1 are what propelled Microsoft to
> success, the release of Vista and the incredibly pitiful Office 2007
> will be what destroy Microsoft or at least marginalize it. Don't
> blame Google. Microsoft is in self destruct mode.
>
>