Outlook Out of Memory to Open Large Folder
-
@black3dynamite said in Outlook Out of Memory to Open Large Folder:
@scottalanmiller said in Outlook Out of Memory to Open Large Folder:
Outlook 2016, user has 8GB of RAM, is only using about 4.5GB of it, so loads of RAM available. When trying to open the sent folder in Outlook, they get "Unable to display the folder. There is not enough free memory to run this program. Quit one or more programs, and then try again". Clearly this has to be incorrect.
But where to go from here? It can't be a heap issue, can it, given it is a fresh build and nothing else being used?
Bad Outlook addon?
No add ons! That's the crazy part. This is a vanilla install, new build.
-
This is the most blatant "not appropriate software for normal uses" situation I've ever run into with Outlook. Unthinkable that MS expects end users monkeying around with the registry to use Outlook.
Nothing on Linux ever compares to this!
-
It ran out of heap again. Maxed it out this time. Fingers crossed.
-
You gonna move them to TB or something so they don't have anymore email issues and get more features?
-
@obsolesce said in Outlook Out of Memory to Open Large Folder:
You gonna move them to TB or something so they don't have anymore email issues and get more features?
Nope, they refuse to try anything else.
-
@scottalanmiller : Office defaults to 32 bit installation for compatibility with 3rd party plugins -- most of which are only written for the 32 bit version of office. This effectively means that Office can only address 2GB of the memory that's available.
As this user has such a large sent folder (though I've never experienced what you're describing), why not do a reinstall using the 64 bit version of Office? All settings and configuration is stored in the registry and will not be overridden.
-
@manxam said in Outlook Out of Memory to Open Large Folder:
@scottalanmiller : Office defaults to 32 bit installation for compatibility with 3rd party plugins -- most of which are only written for the 32 bit version of office. This effectively means that Office can only address 2GB of the memory that's available.
As this user has such a large sent folder (though I've never experienced what you're describing), why not do a reinstall using the 64 bit version of Office? All settings and configuration is stored in the registry and will not be overridden.
Good idea, I'll look into that if the heap expansion to 800,00h doesn't do the trick.
-
This is weird. I think something else is going on here. I'm assuming you installed 64 bit in the first place. I've never had to modify the registry after a new install.
-
Just to add more info, it is an Office 365 64bit install.
-
Not once in 10 years have i had to change this setting for an Outlook user.
Not even people with 15GB mailboxes who have never erased an email from Inbox or Sent folder. -
@jmoore said in Outlook Out of Memory to Open Large Folder:
This is weird. I think something else is going on here. I'm assuming you installed 64 bit in the first place. I've never had to modify the registry after a new install.
We never have either!
-
@scottalanmiller said in Outlook Out of Memory to Open Large Folder:
Turns out, you have to adjust the heap. This is a normal end user just trying to open her sent folder, and they need to manually make registry keys and DWORD values and increase it.
They actually require end users to manually edit the registry to be able to use MS Office? This is insane.
Anyway, it works now.
It would be like expecting a Linux end user to do bash and work on the command line, doesn't seem to be different in my eyes.
-
@dbeato said in Outlook Out of Memory to Open Large Folder:
It would be like expecting a Linux end user to do bash and work on the command line, doesn't seem to be different in my eyes.
I'd say even worse. BASH commands are trivial compared to Regedit. Regedit is difficult to explain, takes many steps, and is not repeatable.
BASH commands can be copy/paste.
And even still, expecting Linux end users to open a shell is ridiculous.
-
@scottalanmiller said in Outlook Out of Memory to Open Large Folder:
@dbeato said in Outlook Out of Memory to Open Large Folder:
It would be like expecting a Linux end user to do bash and work on the command line, doesn't seem to be different in my eyes.
I'd say even worse. BASH commands are trivial compared to Regedit. Regedit is difficult to explain, takes many steps, and is not repeatable.
BASH commands can be copy/paste.
And even still, expecting Linux end users to open a shell is ridiculous.
But some programs do ask for it. Microsoft can however make a line for that registry change too, they just make it with more steps since it is a GUI that is doing the changes.
-
@dbeato said in Outlook Out of Memory to Open Large Folder:
@scottalanmiller said in Outlook Out of Memory to Open Large Folder:
@dbeato said in Outlook Out of Memory to Open Large Folder:
It would be like expecting a Linux end user to do bash and work on the command line, doesn't seem to be different in my eyes.
I'd say even worse. BASH commands are trivial compared to Regedit. Regedit is difficult to explain, takes many steps, and is not repeatable.
BASH commands can be copy/paste.
And even still, expecting Linux end users to open a shell is ridiculous.
But some programs do ask for it. Microsoft can however make a line for that registry change too, they just make it with more steps since it is a GUI that is doing the changes.
Not applications on par to MS Office. Sure, a crappy third party product on any OS might do it. But apples to apples, you'd be talking about LibreOffice, for example. Trust me, LibreOffice works out of the box, you don't need to go into a registry, add new keys that didn't exist before, get admin access, and be super risky, just to open a spreadsheet.
This is MS Office we are talking about, not Windows. Name any software comparable to MS Office that requires this from end users on any platform.
-
Seeing as how it IS a 64 installation and is not using more than a couple of gigs of ram as stated in your title post, I'd suggest it's a corrupt profile.
Is this connected to IMAP or Exchange? If so, why not spin up a new profile and let the mail sync and see what happens?
The only issues that we ever run into with Outlook are fixed with a new profile which, thankfully, is a quick process -- unless you're using POP3 (kill me now!)
-
@manxam said in Outlook Out of Memory to Open Large Folder:
Seeing as how it IS a 64 installation and is not using more than a couple of gigs of ram as stated in your title post, I'd suggest it's a corrupt profile.
Is this connected to IMAP or Exchange? If so, why not spin up a new profile and let the mail sync and see what happens?
The only issues that we ever run into with Outlook are fixed with a new profile which, thankfully, is a quick process -- unless you're using POP3 (kill me now!)
Connected to Exchange. It is O365.
-
@scottalanmiller said in Outlook Out of Memory to Open Large Folder:
@dbeato said in Outlook Out of Memory to Open Large Folder:
It would be like expecting a Linux end user to do bash and work on the command line, doesn't seem to be different in my eyes.
I'd say even worse. BASH commands are trivial compared to Regedit. Regedit is difficult to explain, takes many steps, and is not repeatable.
BASH commands can be copy/paste.
And even still, expecting Linux end users to open a shell is ridiculous.
you can edit the registry from a single command line
-
@manxam said in Outlook Out of Memory to Open Large Folder:
Seeing as how it IS a 64 installation and is not using more than a couple of gigs of ram as stated in your title post, I'd suggest it's a corrupt profile.
Is this connected to IMAP or Exchange? If so, why not spin up a new profile and let the mail sync and see what happens?
The only issues that we ever run into with Outlook are fixed with a new profile which, thankfully, is a quick process -- unless you're using POP3 (kill me now!)
I tend to agree - this sounds like corruption somewhere, could be the OST, a PST, the user's profile, etc.
-
@manxam said in Outlook Out of Memory to Open Large Folder:
Seeing as how it IS a 64 installation and is not using more than a couple of gigs of ram as stated in your title post, I'd suggest it's a corrupt profile.
Is this connected to IMAP or Exchange? If so, why not spin up a new profile and let the mail sync and see what happens?
The only issues that we ever run into with Outlook are fixed with a new profile which, thankfully, is a quick process -- unless you're using POP3 (kill me now!)
The user has 2 ost files:
And using cached Exchange Mode
She has around 43 user mailboxes as well, thinking this could be whats causing the issues.
