Insufficient memory or disk space, cannot display the requested font; Outlook fonts garbled

Anonymous
2009-07-06T18:36:45+00:00

After I've been using Word and Outlook for a while, I receive the following message: there is insufficient memory or disk space. Word cannot display the requested font. Once I get this error message, my fonts are garbled in both Word and Outlook.

I am running Windows Vista 64-bit Home Premium, with Office 2007. I have 4 GB RAM, with settings set on automatic (Windows detects).

I am not a power user. I have Googled and searched Microsoft help, to no avail.

My brand new computer is becoming almost unusable! Please help.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2009-07-07T03:24:20+00:00

kimlife,

Thank you for visiting the Microsoft Answers community forum.

There are a couple of things that can cause this.  One is a corrupted normal.dot template, one is a corrupted printer driver, and the other would be some sort of third part add in.  So let's start witht he simplest to try and that is replacing the normal.dot template.

Click on Start, go to Search, and in the Search box type normal.dot.  There should be a search option that you can check for 'search hidden files', make sure that is checked.  If it does not find it, try searching for *.dot.  It may be hard to find because it is a hidden file.  You may have to go into folder options and be sure "show hidden files" is checked.  Whenever you find normal.dot, rename it old.dot and restart your computer.  Open Word and it will create a new normal.dot template, which is what Word uses as a default blank document.

If that does not work, read this article about a third party add in that can cause this issue:

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

Let us know how that works out and if you need additional help.

Thank you,


Gloria

Microsoft Answers Support Engineer

Visit our Microsoft Answers Feedback Forum and let us know what you think.

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments

59 additional answers

Sort by: Newest
  1. Anonymous
    2011-05-16T19:52:08+00:00

    Hi Gloria,

    I've got the same issue, but in a different way.  I've just installed Microsoft Office 2010, the student package. I've been trying to open old and make new Microsoft Word files.  Upon opening, it gives the same message.  I am running Windows 7 on a 1 year old laptop.  I uninstalled the Microsoft Office 2007 package that was previously installed before installing the new one.  I'm not sure why there'd be anything missing from the Word package when I've only just installed it.

    Any information you could give to help me fix this issue would be great.

    Thanks,

    Harriet

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-04-07T06:49:20+00:00

    After trying various suggestions to no avail, I rebooted the laptop and that fixed it.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-01-04T08:50:50+00:00

    I think I've found a solution for us - SessionViewSize and SessionPoolSize were too small (Google SessionViewSize). However, this might only be applicable to terminal services although the remote desktop post above is probably related (RD uses terminal services).

    http://forums.citrix.com/message.jspa?messageID=708148

    The problem has occured due to increased monitor resolution (wide screens) and specifically for me, dual monitors.

    Cheers, Rob.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2011-01-03T23:34:18+00:00

    I had the same issue on a brand new install of server 2008r2 with remote desktop. The solution was to restart the server.

    An hour of trouble shooting just to restart the server, I have done this a dozen times for clients and seem to have had a different issue each time.

    Was this answer helpful?

    0 comments No comments