G
Greg
One of my users is having a very strange intermittent problem. They'll be
working using Excel 2007 with no problems but then they'll open a document
(any random document, different ones each time and all very small - 32k, 40k,
etc...) and Excel will start throwing resource errors such as:
insufficient memory to create the bitmap. close one or more applications to
increase available
excel cannot complete this task with available resources. choose less data
or close other.
not enough system resources to display correctly.
The crazy thing is, there's 1Gb of RAM on this machine and I open
TaskManager and it's not maxed out. Excel isn't even gobbling it up.
I looked at CPU utilization this time when it happened and I noticed Excel
was hovering around 50% for about 5 minutes while I let it run. The screen
gets all choppy (can only see part of the Excel layout/menus/data). I can go
to other programs and open them but Excel is hosed. Ultimately I END TASK
and start again and it works fine.
It's almost like it spikes right away when opening the file and never
recovers. Anyone have any ideas?
Thanks!
Greg
working using Excel 2007 with no problems but then they'll open a document
(any random document, different ones each time and all very small - 32k, 40k,
etc...) and Excel will start throwing resource errors such as:
insufficient memory to create the bitmap. close one or more applications to
increase available
excel cannot complete this task with available resources. choose less data
or close other.
not enough system resources to display correctly.
The crazy thing is, there's 1Gb of RAM on this machine and I open
TaskManager and it's not maxed out. Excel isn't even gobbling it up.
I looked at CPU utilization this time when it happened and I noticed Excel
was hovering around 50% for about 5 minutes while I let it run. The screen
gets all choppy (can only see part of the Excel layout/menus/data). I can go
to other programs and open them but Excel is hosed. Ultimately I END TASK
and start again and it works fine.
It's almost like it spikes right away when opening the file and never
recovers. Anyone have any ideas?
Thanks!
Greg