#1
|
|||
|
|||
insufficient memory or disk space in Word 2010
Hi all,
I posted before here, and I thought a problem was fixed, but it is back again. Whenever I try to print a couple of docs in MS Word 2010, I keep getting: "There is insufficient memory or disk space. Word cannot display the requested font." This is despite: -deleting normal.dotm -rebooting PC and printer. -running Repair Office 2010. -copying text to another fresh new document I have Windows 10, 32-bit. The odd thing is that before it comes up with the error, there is always a message: "Now printing body..." On the few occasions that printer works in Word 2010 (usually after repeatedly deleting normal.dot), neither above error message appears... instead a warning "the margins of section 1 are outside the printable area of the page. Do you want to continue?", to which I say Yes, and it prints fine. The printer works for other software eg pdf, MS Excel 2010, and other non-MS software. Any help much appreciated. |
#2
|
||||
|
||||
One thing you haven't listed amongst measures you've taken is the remedy from your previous thread on this topic (https://www.msofficeforums.com/word/...ory-error.html) that worked...
The "the margins of section 1 are outside the printable area of the page. Do you want to continue?" message is unlikely to have anything to do with the memory/storage/fonts problem; it concerns your page setup, for which the margins are apparently smaller than the printer manufacturer says are required for your printer.
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#3
|
|||
|
|||
Hi, I just tried that, ie add extra blank lines then saving to blank file, as advised.
It printed ok the first 2 times, but the 3rd time it failed to print again, and again with the 2 error messages ie "Now printing body..." then "There is insufficient memory or disk space. Word cannot display the requested font." I even got a "insufficient memory or disk space" just copying and pasting without printing. I also tried Disk Clean-Up to delete Temp folder and didn't help. In Word 2003, I never had these printing problems, but it is a very common occurrence in Word 2010. The 2 documents that fail to print are only 2 pages long, so I don't understand a memory problem. Any help appreciated. |
#4
|
||||
|
||||
I don't know where you got that idea. I have used Word 2010 extensively for the past 6 years and have never had such an occurrence...
Evidently, if repairing the document and clearing the Temp folder doesn't resolve things, there is something else wrong with your system.
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#5
|
|||
|
|||
insufficient memory or disk space in Word 2010
Re "it is a very common occurrence in Word 2010." should read
"it is a very common occurrence in Word 2010, in my own personal experience". So how can there be something "else wrong with your system" if I only have printing problems with Word 2010, when I don't have printing problems with: -PDF files -Excel -TXT files -Word 2003? Also what is best/safest way to clear temp folder? I tried Windows10 / FileExplorer / C: / Disk-Cleanup. Should I close all apps, and then manually go to temp folder and delete everything (is that safe?) If it helps, refer below Appendix for dump of my current temp folder, which shows lots of folders. Any help much appreciated, as I like Word 2010 apart from printing problem. ---- Volume in drive C is ACER Volume Serial Number is 386E-F4E6 Directory of C:\Users\Sid\AppData\Local\Temp 13-Jan-17 07:44 AM <DIR> . 13-Jan-17 07:44 AM <DIR> .. 13-Jan-17 12:00 AM <DIR> {2212D3CC-32C5-4D49-B88A-2937212AE0F1} 13-Jan-17 12:00 AM <DIR> {516A85A2-FE84-4BEB-908B-DA0E9CCF08E8} 13-Jan-17 12:00 AM <DIR> {B6687B57-C45C-4B05-8B66-64FABBDEB06A} 05-Dec-16 05:33 PM <DIR> {FF0F97AA-AB40-4FD3-AE77-39F81E8961EA} 13-Jan-17 12:00 AM <DIR> 07B2C414-9E4B-4F96-8506-F0F5880B5BA6 13-Jan-17 12:00 AM <DIR> 14972F93-2EAD-456B-9C3D-EDEE0FEE0DD1 13-Jan-17 12:00 AM <DIR> 15FEA2EA-BA0A-481B-96F3-238812F19F5E 13-Jan-17 12:00 AM <DIR> 4E1B8595-34CC-4FCD-89DA-6F759B601E98 13-Jan-17 12:00 AM <DIR> 5167DEDF-060D-4E00-A99C-EA0385B3875E 13-Jan-17 12:00 AM <DIR> 8C6EF91F-A3AD-42E9-AB8E-49196BA3E419 13-Jan-17 12:00 AM <DIR> 9D19F52A-0300-4A5B-AD69-16E2B32C8559 13-Jan-17 12:00 AM <DIR> B440CBE4-B401-467C-A209-EC60009C8FF3 13-Jan-17 12:00 AM <DIR> BAF56DF0-5BB5-428A-B1DA-9665959B04F7 13-Jan-17 12:00 AM <DIR> C60DF6C1-4FE8-408A-9449-C4E6D15DF67B 13-Jan-17 12:00 AM <DIR> C84D0C87-25D3-4914-AA6D-C7F091DF55C6 13-Jan-17 12:00 AM <DIR> EB05BC01-A3D2-4933-8E1D-B606DEE4EB95 25-Nov-16 09:47 PM <DIR> msdtadmin 12-Jan-17 11:45 PM <DIR> msohtmlclip1 01-Dec-16 06:17 PM <DIR> nsd5716704611998 12-Jan-17 06:20 PM <DIR> outlook logging 12-Jan-17 07:35 PM <DIR> SDIAG_3d8a1a8a-fe74-419e-831b-f83bd6b009ac 12-Jan-17 07:25 PM <DIR> SDIAG_a93c51f8-209d-47ea-9ea6-ee8bbdca051f 12-Jan-17 04:35 PM <DIR> Setup000005d0 05-Dec-16 04:18 PM <DIR> TeamViewer 01-Oct-16 01:39 AM <DIR> Trend Micro 09-Jan-17 11:43 AM <DIR> OICE_EEE66078-C1A2-4B63-8FF8-CA6B9D171CFE.0 26-Oct-16 02:21 AM <DIR> CR_B09F9.tmp 12-Jan-17 11:47 PM 4,428 15635000.cvr 08-Jan-17 07:00 PM 0 CVR18BA.tmp.cvr 11-Jan-17 04:53 PM 0 CVR1D29.tmp.cvr 13-Jan-17 12:27 AM 0 CVR2D7E.tmp.cvr 11-Jan-17 06:14 PM 0 CVR4BB3.tmp.cvr 08-Jan-17 03:45 PM 0 CVR4E76.tmp.cvr 11-Jan-17 06:12 PM 0 CVR603F.tmp.cvr 11-Jan-17 05:06 PM 0 CVR613C.tmp.cvr 11-Jan-17 05:16 PM 0 CVR6C7C.tmp.cvr 10-Jan-17 03:53 PM 0 CVR7144.tmp.cvr 09-Jan-17 11:43 AM 0 CVR74D3.tmp.cvr 08-Jan-17 07:22 AM 0 CVR7E08.tmp.cvr 12-Jan-17 06:32 PM 0 CVR874F.tmp.cvr 12-Jan-17 07:35 PM 0 CVR9018.tmp.cvr 11-Jan-17 05:26 PM 0 CVR97D5.tmp.cvr 06-Jan-17 09:08 PM 0 CVRA4B3.tmp.cvr 12-Jan-17 06:20 PM 0 CVRAB67.tmp.cvr 11-Jan-17 06:27 PM 0 CVRAD03.tmp.cvr 11-Jan-17 04:31 PM 0 CVRB6A0.tmp.cvr 09-Jan-17 04:58 PM 0 CVRC4A0.tmp.cvr 11-Jan-17 05:02 PM 0 CVRC960.tmp.cvr 11-Jan-17 05:49 PM 0 CVRCCE9.tmp.cvr 11-Jan-17 05:44 PM 0 CVRDDF9.tmp.cvr 12-Jan-17 02:24 PM 0 CVRDF31.tmp.cvr 11-Jan-17 05:18 PM 0 CVRE4F3.tmp.cvr 12-Jan-17 03:04 PM 0 CVRE64.tmp.cvr 09-Jan-17 10:49 PM 0 CVRE722.tmp.cvr 11-Jan-17 05:56 PM 0 CVREBFD.tmp.cvr 12-Jan-17 12:45 PM 0 CVREC07.tmp.cvr 11-Jan-17 05:20 PM 0 CVRF573.tmp.cvr 11-Jan-17 10:22 AM 624 sa.1A7994D6-5342-8581-71FB-A2BD1C895D93_5__.Public.AppUpdate.dat 01-Apr-15 03:30 PM 9,216 asc10_startupBlack.db 20-Dec-16 02:03 PM 27,648 asc10_startupWhite.db 01-Apr-15 03:30 PM 9,216 sm10_startupBlack.db 20-Dec-16 02:03 PM 27,648 sm10_startupWhite.db 12-Jan-17 07:24 PM 131,072 6A883A09-B28F-4D85-BEFA-AFA3D1C8C617.Diagnose.0.etl 12-Jan-17 07:35 PM 131,072 FB47EC84-9F55-4EAE-8DE9-A9027D349CAC.Diagnose.0.etl 08-Jan-17 05:30 PM 0 CProgram FilesOpera42.0.2393.94opera_autoupdate.download.lo ck 08-Jan-17 05:30 PM 0 CProgram FilesOpera42.0.2393.94opera_autoupdate.metrics.loc k 13-Jan-17 06:10 AM 2,751 AdobeARM.log 12-Jan-17 03:12 AM 1,535 AdobeARM_NotLocked.log 13-Jan-17 03:48 AM 4,713 jusched.log 08-Jan-17 05:30 PM 0 opera_crashreporter.log 12-Jan-17 05:30 PM 99,569 SetupExe(201701121635155D0).log 12-Jan-17 06:05 PM 115,443 SetupExe(201701121741531C98).log 08-Jan-17 11:44 AM 0 #A#3lefzGidYpi,b.tmp 13-Jan-17 12:47 AM 512 ~DF36BE7F082B8DFC0D.TMP 13-Jan-17 12:27 AM 512 ~DF7E43A4A20D70C67A.TMP 12-Jan-17 03:04 PM 0 DMI5564.tmp 08-Jan-17 02:12 PM 0 DMI5D87.tmp 12-Jan-17 07:32 PM 0 DMI9AE4.tmp 08-Jan-17 09:33 AM 0 DMIA275.tmp 12-Jan-17 05:37 PM 0 DMIECD7.tmp 12-Jan-17 05:00 PM 877,368 Hx9D66.tmp 16-Mar-16 08:25 AM 383 wctE7AB.tmp 13-Jan-17 07:44 AM 0 dump.txt 56 File(s) 1,443,710 bytes 29 Dir(s) 153,254,006,784 bytes free |
#6
|
||||
|
||||
Quote:
Quote:
You could close all Office apps, then select & delete everything in the Temp folder.
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#7
|
|||
|
|||
insufficient memory or disk space in Word 2010
Hi,
-Office 2003 was completely installed before installing Office 2010. Are you suggesting I should uninstall Office 2010, and reinstall? -Also, emails print ok too, it's just Word 2010 that mostly don't print. -Also, I closed all apps and deleted entire temp folder, except 2 files which would not allow deletion. -01-Apr-15 03:30 PM 9,216 asc10_startupBlack.db -20-Dec-16 02:03 PM 27,648 asc10_startupWhite.db Any other suggestions? Thanks, Sid |
#8
|
||||
|
||||
That should be sufficient. Since Office 2003 was installed before Office 2010, there should be no need for an Office 2010 reinstall on that account. Do note, however, that Microsoft says that Office 2003 (which is no longer supported) is not compatible with Windows 10 - notwithstanding that you may have been able to install it on that platform.
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#9
|
|||
|
|||
Hi Paul,
I installed Office 2010 before upgrading from Win 7 to Win 10. Do you have other suggestions to fix "insufficient memory or disk space. Word cannot display the requested font" so I can enjoy Word 2010? I have 188GB free, and 4GB RAM, Win 10 32 bit. Thanks, Sid |
#10
|
||||
|
||||
It's possible something went awry with the upgrade - a fairly common scenario. Since you've already done an Office repair, it might be worthwhile running the System File Checker to detect & repair any damaged files. To do that, open a Command Prompt with Administrator privileges, then input:
SFC /scannow and press Enter. The process will likely take quite a while to run, so go and have a cup of coffee or whatever while you're waiting.
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#11
|
|||
|
|||
Hi Paul,
I ran "SFC /scannow", but no errors as per: "100% complete. Windows Resource Protection did not find any integrity violations." I also re-ran Office Repair, then retried printing but same: "insufficient memory or disk space. Word cannot display the requested font". I noticed before the preceding "Now printing body..." message, it briefly said "Not responding". Any other suggestions? Thanks, Sid |
#12
|
||||
|
||||
Evidently, something has gone wrong with your Win 10 upgrade. Short of wiping your system and reinstalling everything (backup all your data first!), Windows 10 included, I'm out of ideas.
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#13
|
|||
|
|||
Hi Paul,
Thanks for trying. It's frustrating having MS Word and not being able to print docs, when I can print fine everything else. No worries, Sid |
#14
|
|||
|
|||
I found a fudge.
Before I print any docx file, I "save as" to pdf format and it prints fine. Thanks again for your help. |
#15
|
|||
|
|||
We are on Word 2010 and upgraded to Windows 10 about 2 months ago. At least two secretaries at my firm have had this problem. We tried the resolutions mentioned above (deleting normal, rebooting PC, etc.). They could print, but only for a short time; the problem would return. When the documents were opened on other pcs, the problem did not occur; no error messages at all, the document would print fine.
We finally upgraded their printer drivers. They were using model HP Universal Printing PS (v.5.3); now they have HP Universal Printing PCL 6 (v6.3.0). They've been stable now for several weeks (fingers crossed). |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
There is not enough memory or disk space to complete the operation. | esjay | Word | 4 | 01-30-2019 02:45 PM |
Word 10 - repeated insufficient memory error | sidr | Word | 3 | 02-10-2017 04:32 AM |
Insufficient memory error when printing to a macro | Rockystock | Word VBA | 8 | 10-21-2016 07:43 AM |
"Not enough memory or disk space" problem | Hickory | Word | 8 | 11-13-2011 06:48 PM |
Outlook Recovery D Low Disk Space | rec | Outlook | 0 | 06-14-2010 10:11 AM |