Font corrupt for network home user

[imyrvold]

I am the IT administrator in our company, for around 25 Macintoshes,
mostly iMac G5 20'', where the users are network home users. All
machines have Office 2004 installed. In the last month, several users
have been complaining that they are unable to launch Word or Excel on
their machines. When launched, a message is popping up, saying that
font this and that is corrupt. Clicking away the message window, only
makes it reappear in a couple of seconds with a similar message. The
only way to get out of this is to force quit the application.

The strange thing is that if the user goes to another machine, and
logging on as the same user, he is able to launch Word or Excel just
fine. Also, if another user logs in as a network user to the machine
with the problem, he also is able to launch Word or Excel.

Have anyone else seen this problem?

 

[Nathan Herring [MSFT]]

Network home directories are not a supported configuration of Office 2004.

That being said, are these folks running Office apps on multiple machines
while logged into the same user account (and thus using the same home
directory)? If so, one application is probably locking the font cache file,
causing the application being launched on the other machine to have this
problem.

If you remove Microsoft Office 2004:Office:Support Files:FontCacheTool, we
will bypass the process that's probably causing you the problem. If you have
corrupt fonts, we won't know not to use them, and may crash during normal
use.

-nh

 

[John Wiles]

Nathan,

On the same topic, I am running network homes with users logged in
multiple times. Although unsuported, I cannot feasibly run my network
any other way.

It does work for the most part. However I've found that lots of dummy
files get created in the home/Library/Preferences/Microsoft folder.
Thousands and thousands over time. This seems to slow word down, and
cause launching problems, freezes etc.
Deleting the folder fixes the problem. But I would prefer to avoid that
solution.
Also only user accounts that are used as multiple-login-at-once develop
this problem.

Is there anyway that you know of to fix this problem? Is there a
webpage where someone has sucessfully created a system where users have
network homes and are logged in multiple times? I cannot find any
information (suprisingly).

What would you suggest?

Kind Regards,

John W

 

[Loren]

If you remove Microsoft Office 2004:Office:Support Files:FontCacheTool, we
will bypass the process that's probably causing you the problem. If you have
corrupt fonts, we won't know not to use them, and may crash during normal
use.

-nh

5-10-06 07:12:02 -0400, "Nathan Herring [MSF

Nathan,

After the umpteenth (literally umpteenth) time I couldn't start word on
Tiger because of all the corrupted font messages, I finally archived
and removed the FontCacheTool, and for now it works wonderfully.

I even immediately went to a number of fonts that Word was erroneously
reporting corrupted at startup, in the Font menu, which is no longer
WYSIWYG which is fine with me, and tried them. NO PROBLEMS. So they
are NOT corrupt.

I do not like removing components of software, so I hope this doesn't
crash on me.

In case this helps fix this problem already:

-- i finally resorted to deleting the FCT because this time neither
deep cleaning in Tiger Cache Cleaner NOR removing all font caches with
Smasher resolved the problem this time. (TCC deep cleaning caches and
restart temporarily resolved problem before.)

-- i also went into Font Book and MANUALLY removed all duplicate fonts,
keeping in this order:

/System/Library/Fonts/
/Library/Fonts/
~/Library/Fonts/
/System Folder/Fonts/

I restarted again after doing that, but that also DID NOT HELP.

-- I tried deleting ~/Library/Preferences/Microsoft/Word Font Substitutes
this also did not help.

--- finally stuffed FontCacheTool and removed original and emptied trash

Now works.

I have approximately 400 fonts listed in font book and NO duplicates (anymore).

Please fix this problem already. Thank you.

 

[Oriflame CDC]

Great!
Removing the FontCacheTool file seems to help.

Also good to know that Office won't warn for corrupted fonts when that file
is removed, but it seems to work fine now. So far...

 

[ke3ht]

*On 2005-10-06 07:12:02 -0400, "Nathan Herring [MSFT]"

If you remove Microsoft Office 2004:Office:Suppor Files:FontCacheTool, we
will bypass the process that's probably causing you the problem. I you have
corrupt fonts, we won't know not to use them, and may crash durin normal
use.

-nh

5-10-06 07:12:02 -0400, "Nathan Herring [MSF

Nathan,

After the umpteenth (literally umpteenth) time I couldn't start wor
on
Tiger because of all the corrupted font messages, I finally archived
and removed the FontCacheTool, and for now it works wonderfully.

I even immediately went to a number of fonts that Word wa
erroneously
reporting corrupted at startup, in the Font menu, which is no longer
WYSIWYG which is fine with me, and tried them. NO PROBLEMS. S
they
are NOT corrupt.

I do not like removing components of software, so I hope thi
doesn't
crash on me.

In case this helps fix this problem already:

-- i finally resorted to deleting the FCT because this time neither
deep cleaning in Tiger Cache Cleaner NOR removing all font cache
with
Smasher resolved the problem this time. (TCC deep cleaning cache
and
restart temporarily resolved problem before.)

-- i also went into Font Book and MANUALLY removed all duplicat
fonts,
keeping in this order:

/System/Library/Fonts/
/Library/Fonts/
~/Library/Fonts/
/System Folder/Fonts/

I restarted again after doing that, but that also DID NOT HELP.

-- I tried deleting ~/Library/Preferences/Microsoft/Word Fon
Substitutes
this also did not help.

--- finally stuffed FontCacheTool and removed original and emptie
trash

Now works.

I have approximately 400 fonts listed in font book and NO duplicate
(anymore).

Please fix this problem already. Thank you.

Loren! Wow, not much on this problem ANYWHERE on the net. Microsoft o
Mac. Thanks for posting the work around. fontcachtool apparently ha
something of a bug that makes it loop forever and calls fonts corrup
when they are not. I am unsure how this all began but again THANKS fo
posting the work around.

,,,Ti


-
ke3h

 

[ke3ht]

*On 2005-10-06 07:12:02 -0400, "Nathan Herring [MSFT]"

If you remove Microsoft Office 2004:Office:Suppor Files:FontCacheTool, we
will bypass the process that's probably causing you the problem. I you have
corrupt fonts, we won't know not to use them, and may crash durin normal
use.

-nh

5-10-06 07:12:02 -0400, "Nathan Herring [MSF

Nathan,

After the umpteenth (literally umpteenth) time I couldn't start wor
on
Tiger because of all the corrupted font messages, I finally archived
and removed the FontCacheTool, and for now it works wonderfully.

I even immediately went to a number of fonts that Word wa
erroneously
reporting corrupted at startup, in the Font menu, which is no longer
WYSIWYG which is fine with me, and tried them. NO PROBLEMS. S
they
are NOT corrupt.

I do not like removing components of software, so I hope thi
doesn't
crash on me.

In case this helps fix this problem already:

-- i finally resorted to deleting the FCT because this time neither
deep cleaning in Tiger Cache Cleaner NOR removing all font cache
with
Smasher resolved the problem this time. (TCC deep cleaning cache
and
restart temporarily resolved problem before.)

-- i also went into Font Book and MANUALLY removed all duplicat
fonts,
keeping in this order:

/System/Library/Fonts/
/Library/Fonts/
~/Library/Fonts/
/System Folder/Fonts/

I restarted again after doing that, but that also DID NOT HELP.

-- I tried deleting ~/Library/Preferences/Microsoft/Word Fon
Substitutes
this also did not help.

--- finally stuffed FontCacheTool and removed original and emptie
trash

Now works.

I have approximately 400 fonts listed in font book and NO duplicate
(anymore).

Please fix this problem already. Thank you.

Loren! Wow, not much on this problem ANYWHERE on the net. Microsoft o
Mac. Thanks for posting the work around. fontcachtool apparently ha
something of a bug that makes it loop forever and calls fonts corrup
when they are not. I am unsure how this all began but again THANKS fo
posting the work around.

,,,Ti


-
ke3h