Software

Ask something
Discussion Locked

reference in word97 normal.dot corruptin

0 helpful
9 replies

by taterater 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a netware network. With word97, Users normal.dots are stored in there home dir. The normal.dot has a reference to a print.dot template (shared on the network also). On some days (not all) the normal.dot loses its reference to print.dot, and instead references a tmp file on the workstation. So when word starts Vbediter comes up as the tmp file does not exist. Replacing normal.dot with one that has the original reference fixes the problem. This will be fine for a few days and then all users will get the error. Anyone have any ideas???

9 replies

by vinnyd

The easiest way I know of to have the normal.dot file damaged is with a computer virus.

You better check for viruses.

The bad news is that you may have to check each workstation on the network.

You may be able to the SALVAGE on the novell server to see if someone is deleting the file and replacing it with another one to limit the search to see who corrupts it.

by taterater

Our Virus scanning software is completly up-to-date.

It is also happening to all normal.dot's but users only have rights to see their own normal.dot as it lives in each users home directory. So it is not a case of someone replacing them.

by philthegreat

1) Virus is less probable choice; because you must have an anti-virus program in your network;
2) normal.dot corruption is usually related unstable winword: so you must figure out which computers or users usually have the problem. It may be relatedto the problem of winword (re-install it in this computer); check for the RAM and harddisk memory too. Too few can cause the same problems; besides, sometimes the SR-1 of word97 will fix some problems.

by taterater

1. Virus software fully up-todate
2. the same corruption is happening to many normal.dots at once on many PC's, It is not machine related.
3. Office is patched to SR2

by jcombs

Is the print.dot stored in the users home directory? If not I would edit the Normal.dot reference to point to a print.dot file stored in the same directory. Test this on a handfull of machines that commonly have the problem when the rest of the group does. I bet you will find this resolves the issue, then apply network wide.

by paul d. masley

It appears that you have a hidden memory virus that your AV cannot detect since this is only happening on certain days. Look in the storage directory for it. You may have to do a file by file visual scan to detect it. It also may be on only one of the users machines and is corrupting the network only when that user is activating it.

Paul.

This discussion is closed to new replies.