Word 2003 corruption

Problem:
Mouse does not show or respond in MS Word 2003 and Word does not start with
a blank document.

For no apparent reason, the user will start Word and a blank document will
not automatically load. Then, when any previous document is loaded or a new
document is created, the mouse will not work anywhere on the actual document.
The mouse will work on the toolbars and menu.

There are not errors before or after this happens. There is nothing in
event viewer that would indicate a problem. There is no pattern as to when
this occurs.

Other Office programs are not affected by this.

Other users can log on to the computer and Word works fine.

The ONLY way to fix this problem is to delete the user profile and re-create
it again.
(We have tried using the Microsoft Application Recovery Tool, reinstalling
office, etc etc etc and nothing fixes it.)

We run Windows XP Pro SP2, McAfee Enterprise 8i, Office 2003 SP2.

We re-built the machine and the problem still occurs. The user does have
Visio installed. The user is one of our developers and did have a number of
development tools installed, but since the rebuild, we only put Visio back on
it. Other than Visio he is setup like all other users.

I have 5 other users with the exact same machine. P4 3.0 GHz (with
Hyper-Threading disabled in the BIOS, 1 GB RAM, 80 GB SATA II HD) and none of
the other users have reported this problem.

This user has it happens to him every week or every other week.

When it happens, compare his normal.dot to another's whose is working OK.
Are they the same size? Try replacing his with one that is known good.
I've seen corrupted normal.dots do this to word...



"Tim" wrote in message
...
Problem:
Mouse does not show or respond in MS Word 2003 and Word does not start
with
a blank document.

For no apparent reason, the user will start Word and a blank document will
not automatically load. Then, when any previous document is loaded or a
new
document is created, the mouse will not work anywhere on the actual
document.
The mouse will work on the toolbars and menu.

There are not errors before or after this happens. There is nothing in
event viewer that would indicate a problem. There is no pattern as to
when
this occurs.

Other Office programs are not affected by this.

Other users can log on to the computer and Word works fine.

The ONLY way to fix this problem is to delete the user profile and
re-create
it again.
(We have tried using the Microsoft Application Recovery Tool, reinstalling
office, etc etc etc and nothing fixes it.)

We run Windows XP Pro SP2, McAfee Enterprise 8i, Office 2003 SP2.

We re-built the machine and the problem still occurs. The user does have
Visio installed. The user is one of our developers and did have a number
of
development tools installed, but since the rebuild, we only put Visio back
on
it. Other than Visio he is setup like all other users.

I have 5 other users with the exact same machine. P4 3.0 GHz (with
Hyper-Threading disabled in the BIOS, 1 GB RAM, 80 GB SATA II HD) and none
of
the other users have reported this problem.

This user has it happens to him every week or every other week.

Have you tried deleting the normal.dot file or renaming it and letting Word
rebuild a new normal.dot?

--�
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Tim asked:

| Problem:
| Mouse does not show or respond in MS Word 2003 and Word does not
| start with a blank document.
|
| For no apparent reason, the user will start Word and a blank document
| will not automatically load. Then, when any previous document is
| loaded or a new document is created, the mouse will not work anywhere
| on the actual document. The mouse will work on the toolbars and menu.
|
| There are not errors before or after this happens. There is nothing
| in event viewer that would indicate a problem. There is no pattern
| as to when this occurs.
|
| Other Office programs are not affected by this.
|
| Other users can log on to the computer and Word works fine.
|
| The ONLY way to fix this problem is to delete the user profile and
| re-create it again.
| (We have tried using the Microsoft Application Recovery Tool,
| reinstalling office, etc etc etc and nothing fixes it.)
|
| We run Windows XP Pro SP2, McAfee Enterprise 8i, Office 2003 SP2.
|
| We re-built the machine and the problem still occurs. The user does
| have Visio installed. The user is one of our developers and did have
| a number of development tools installed, but since the rebuild, we
| only put Visio back on it. Other than Visio he is setup like all
| other users.
|
| I have 5 other users with the exact same machine. P4 3.0 GHz (with
| Hyper-Threading disabled in the BIOS, 1 GB RAM, 80 GB SATA II HD) and
| none of the other users have reported this problem.
|
| This user has it happens to him every week or every other week.

No. Looking at or replacing the Normal.dot did not occur to me (it should
have). That seems like a good thing to try at least. Next time we will see
if that works. (Does the normal.dot get accessed\used if you launch Word by
opening up an existing document? That is another "sympton" of this problem.
The user goes to open any existing word document, without Word being loaded,
and that document does not load. Would a corrupt Normal.dot affect this too?)

Well, it was not the "normal.dot" it was the "Send to laserfiche.dot"

http://www.laserfische.com/

This is a program that allows us to scan paper documents into a server on
our network. A few people have the Administration tools on their machines so
they can take a PDF file and scan into the database. I guess Laserfische
uses Word somehow to do this? I don't know, I have to look into it more.

But in C:\documents and settings\user\application data\microsoft\templates

Where Normal.dot is located, there is also a file called: Send to
Laserfische.dot

When we deleted the Send to laserfishe.dot, Word started working again.

wait, our developer just found an article on the Laserfische website about
this exact problem.

==================
In certain situations, the Send to Laserfiche feature may prevent the mouse
from functioning correctly in Microsoft Word 2003.
Resolution
The "Send to Laserfiche.dot" template is corrupted and is incorrectly
affecting Microsoft Word 2003. Delete the template and restart Word 2003. The
template will be automatically regenerated the next time you start Word.
To delete the template
Close all instances of Microsoft Word 2003. Use the Windows Task Manager to
verify that there is no WINWORD.EXE process still running.
Browse to C:\Documents and Settings\YourUserName\Application
Data\Microsoft\Templates.
Delete the "Send to Laserfiche.dot" file.
=====================================



"Tim" wrote:

Problem:
Mouse does not show or respond in MS Word 2003 and Word does not start with
a blank document.

For no apparent reason, the user will start Word and a blank document will
not automatically load. Then, when any previous document is loaded or a new
document is created, the mouse will not work anywhere on the actual document.
The mouse will work on the toolbars and menu.

There are not errors before or after this happens. There is nothing in
event viewer that would indicate a problem. There is no pattern as to when
this occurs.

Other Office programs are not affected by this.

Other users can log on to the computer and Word works fine.

The ONLY way to fix this problem is to delete the user profile and re-create
it again.
(We have tried using the Microsoft Application Recovery Tool, reinstalling
office, etc etc etc and nothing fixes it.)

We run Windows XP Pro SP2, McAfee Enterprise 8i, Office 2003 SP2.

We re-built the machine and the problem still occurs. The user does have
Visio installed. The user is one of our developers and did have a number of
development tools installed, but since the rebuild, we only put Visio back on
it. Other than Visio he is setup like all other users.

I have 5 other users with the exact same machine. P4 3.0 GHz (with
Hyper-Threading disabled in the BIOS, 1 GB RAM, 80 GB SATA II HD) and none of
the other users have reported this problem.

This user has it happens to him every week or every other week.