WINWORD.EXE Pasting within new documents and old documents

[SkyEyes]

I have about 12 machines that when people go to utilize the copy/paste, they
blow up with the following errors in the Event Viewer. These errors are
consistent with all pcs. They are different images, but all have .NET 2003,
VB 6, Crystal Enterprise, Crystal Enterprise secLDAP Pluggin 9.0, Crystal
Reports Developer 9, Microsoft Office 2000, Project 2000, MSDN Library,
Groupwise, .NET framework 1.1 w/hotfix, Microsoft Visio for Enterprise
Architects SR-1. This always occurs in word 2000.

We have gone so far as to give a person a new pc, along with a new profile
(which means all new settings) and normal.dot. Reloaded Office 2000 on the
server and reran install--still blows up. Deleted the printer from the
broker, her pc along with the driver, rebooted and reinstalled new from
broker with new driver. We've fine tuned the pcs, deleted temp files and
other garbage, ran defrag, etc., and still experience problems. I've followed
the documentation in a microsoft TID to clean and refresh things and we still
have problems.

These are old documents and brand new documents. If I log into the pc, it
also blows up on me after playing with the copy, cut, paste long enough on a
brand new document. A lot of times the clients say they are just moving text
around within the same document. I cannot get it to consistently blow up.

Any help anyone can give would be appreciated. Also, is there a way to trace
back the 0x300 or 0x308 to tell me where this is coming from?

Application popup: WINWORD.EXE - Application Error : The instruction at
"0x30062474" referenced memory at "0x06da97f0". The memory could not be
"read".

Application popup: WINWORD.EXE - Application Error : The instruction at
"0x308c33fb" referenced memory at "0x06a08889". The memory could not be
"written".

Thanks in advance.

 

[TF]

The error is suggesting that the Crystal Reports plug-in is incompatible
with Word 2000. I'd check this out with CA.



:I have about 12 machines that when people go to utilize the copy/paste,
they
: blow up with the following errors in the Event Viewer. These errors are
: consistent with all pcs. They are different images, but all have .NET
2003,
: VB 6, Crystal Enterprise, Crystal Enterprise secLDAP Pluggin 9.0, Crystal
: Reports Developer 9, Microsoft Office 2000, Project 2000, MSDN Library,
: Groupwise, .NET framework 1.1 w/hotfix, Microsoft Visio for Enterprise
: Architects SR-1. This always occurs in word 2000.
:
: We have gone so far as to give a person a new pc, along with a new profile
: (which means all new settings) and normal.dot. Reloaded Office 2000 on the
: server and reran install--still blows up. Deleted the printer from the
: broker, her pc along with the driver, rebooted and reinstalled new from
: broker with new driver. We've fine tuned the pcs, deleted temp files and
: other garbage, ran defrag, etc., and still experience problems. I've
followed
: the documentation in a microsoft TID to clean and refresh things and we
still
: have problems.
:
: These are old documents and brand new documents. If I log into the pc, it
: also blows up on me after playing with the copy, cut, paste long enough on
a
: brand new document. A lot of times the clients say they are just moving
text
: around within the same document. I cannot get it to consistently blow up.
:
: Any help anyone can give would be appreciated. Also, is there a way to
trace
: back the 0x300 or 0x308 to tell me where this is coming from?
:
: Application popup: WINWORD.EXE - Application Error : The instruction at
: "0x30062474" referenced memory at "0x06da97f0". The memory could not be
: "read".
:
: Application popup: WINWORD.EXE - Application Error : The instruction at
: "0x308c33fb" referenced memory at "0x06a08889". The memory could not be
: "written".
:
: Thanks in advance.

 

[SkyEyes]

Thanks...we'll follow up with them. How did you come to this conclusion.
I've been searching for information regarding the instruction at ....., but
could not find anything dealing with .NET or cystal. Just curious. Thanks.