10 years after the initial post, I received the same error message attempting to open a very small (6x15) spreadsheet embedded in a very small (380K) .DWG file. I have 12 GB of RAM with 9 GB free, and probably overlarge (12 GB) automatic pagefile.
Nobody responded to the original post 10 years ago, I don't expect any assistance today. Which means I won't be disappointed, so at least I have that going for me.
@Anonymous wrote:
10 years after the initial post, I received the same error message attempting to open a very small (6x15) spreadsheet embedded in a very small (380K) .DWG file. I have 12 GB of RAM with 9 GB free, and probably overlarge (12 GB) automatic pagefile.
Nobody responded to the original post 10 years ago, I don't expect any assistance today. Which means I won't be disappointed, so at least I have that going for me.
OS? 32 bit or 64? (I'm assuming 64 bit with all that RAM but just want to make sure)
Have you tried setting your page file to a more realistic number?
Have you rebooted your computer and tried the operation again?
Can you post the exact error message/screenshot?
If possible, can you post the offending file here, it could be a corrupt file problem as well.
In this case I suggest page file as 4 x you physical RAM = 49152 minimum and at least 8 x your physical RAM = 98304 as a maximum and see what effect this has.
Or let Windows manage the memory.
I'm going to go out on a limb and say this error has nothing to do with memory sufficiency, and everything to do with programmers writing presumptuous error messages. Which they sometimes do, hey whaddyagonnadoo.
Now that that's out of the way, along with (hopefully) all of the well-meaning memory-management-related replies:
Does anyone have or know of a solution or workaround such as...
...a way to export or convert the OLE object to something you can actually open
...a way to condense or strip content from the OLE object
...what kinds of content in the OLE object are problematic
etc.
Unfortunatly no, the problem with OLE objects is that only a portion of the data is brough in and linked.
https://en.wikipedia.org/wiki/Object_Linking_and_Embedding
solving the problem :(...
first step print screen excel on autocad page to Jpg file.
Sec. step this site flowing http://www.onlineocr.net/
ı hope solve..
I got same error on one excel ole on a dwg, and I can open another excel ole on same dwg. I tried with autocad 2019 and 2020, same result.
so it is not about pc, windows, ram or autocad. its about broken excel file.