• Facebook
  • RSS Feed
  • Instagram
  • LinkedIn
  • Twitter
Jan 122011

I’ve just finished working on an issue with the folks in Support, relating to PSTDisableGrow.  A customer had the key set per :


  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:HKEY_CURRENT_USER  \  Software  \  Microsoft  \  Office  \  12.0  \  Outlook  \  PST
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type PstDisableGrow, and then press ENTER.
  5. Right-click PstDisableGrow, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.

When they upgraded the Enterprise Vault Outlook Add-in to 9.0.1, they had a problem whereby opening an archived item gave them just the shortcut.  The banner across which when click showed :


The item could not be downloaded. [OIOM] 80070005


There was a change made to the 9.0.1 client to fully utilise the Outlook Object Model.  We use that to display items.  In order to display an item using the Outlook Object Model you have to have the item in a message store – previously we used an in-memory object.  So, we download the item you double click on, and add it to a temporary PST file, and then use the Outlook Object Model to display the item.  You can see the problem, I hope!  We can create a PST file…. but we can’t “grow” it to put the retrieved message in it.. so errors are thrown in to the client log, and the net result is the item fails to display, giving the end user just the shortcut.


The fix is two fold.

First of all the PSTDisableGrow must be in :

HKEY_CURRENT_USER  \  Software  \  Policies  \  Microsoft  \  Office  \  <version>  \ Outlook  \  PST

Secondly you have to add the key, PSTDisableGrowAllowAuthenticodeOverrides :

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following registry subkey:HKEY_CURRENT_USER  \  Software  \  Policies  \  Microsoft  \  Office  \  <version>  \  Outlook  \  PST
  3. Click the Edit menu, point to New, and then click DWORD Value.
  4. Type PSTDisableGrowAllowAuthenticodeOverrides, and then press ENTER.
  5. Right-click PSTDisableGrowAllowAuthenticodeOverrides, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

After that, restart Outlook, everything will work.

Version is 12.0 for Outlook 2007, and 14.0 for Outlook 2010.  You can find out the other versions easily enough, and it’s shown in the EV Outlook Add-in client log, if needed.


This information will land in a technote near you, very soon !





If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

  20 Responses to “PSTDisableGrow and the Enterprise Vault Outlook Addin 9.0.1”

  1. Hello Rob.
    What if we also use DisablePST? Would that affect the temp-creation of a pst to retrieve messages? I believe not, but need to be sure, or incorporate this in the technote 😉

  2. Good question, I will test that today or Monday, and post results.

  3. Setting DisablePST has no effect on the Outlook Addin functionality. The only thing I can see is one line in the trace saying whether it is set or not.

    With it set, I can open archived items, and my VC builds just fine.

    Hope that helps,

  4. Your my hero!
    had tried a lot of different solutions but none seem to apply.
    ive doen a repair client, deleted some reg keys, replaced outlvb.dll and ran the msiexec to install vbs etc..
    the is the one start works for me! THANKS!

    Im running office 2010 on a windows server 2008 citrix environment.


  5. This solution does not resolve on Outlook 2010 RTM and EV client 9.0.2 🙁 Any other ideas?

    • So, I think the first step is to provide some environmentals… eg what registry keys have you put where, on which version of Windows (and which bitness of Windows), and which bitness of Office 2010.

      Then grab a full client trace of trying to retrieve an item. That should show a bit more about what’s going on.

      Also would be worth indicating how you have set the keys, eg manually or via GPO etc.

  6. Could you please let me know how we can configure the “PSTDisableGrowAllowAuthenticodeOverrides” key via GPO.
    Our domain is 2003 and Exchange/Outlook is 2007 [12.0].
    As i’m not good in GPO, it will great if you can provide the steps.

    Thanks in advance.

  7. Ding,
    Sorry for dredging up a old post but we are having this problem and we have been working with Symantec tech support for nearly 3 months now and I believe we’ve stumped them. We have Office 2010 32bit and Windows 7 64bit being used via a XenDesktop VDI solution. In the beginning we were getting an error when attempting to open any vault item. After Symantec support put in the two registry keys you mention in this article (Except with 14.0 since we’re on Office 2010) we can now open any items in the active mailbox but if you do a search using Search Vaults or use Archive Exlorer you can restore approximately 4-6 times (depends on size of item you restore) and then you get a message “Could not show this item. Try agan. If it still fails, contact your Help Desk. The item could not be downloaded. [OIOM] [CBVI]” This will continue to happen until you close Outlook or if using Archive Explorer both Outlook and Internet Explorer. We are currently using EV add-in though per Symantec’s troubleshooting we’ve tried it with the 9.0.3 client as well and it behaves the same way. You mention that EV creates PST files. Where does it store the PST file as I’ve done searches and can’t find one. Thanks for any help you can provide! I’d be happy to send an log files you like and if you still have access to Symantec’s support database my current case number is 415-903-838.

    • By all means have the support tech drop me an email internally at Symantec, I’d be happy to take a look at the data that they have gathered.
      The PSTs are stored in the users ‘temp’ folder… and deleted once used. [I also believe they don’t have a .pst extension, but can’t confirm without checking the code]

      Do you have this same problem on non-Citrix machines?

      • Thanks very much for the offer of assistance! I don’t see an e-mail address or a real name listed for you so I’ll just mention the blog and maybe they’ll know how to get in touch with you. To answer your question, yes, this happens outside of our VDI environment as well. I happens to all but one of our computers and that computer is very non-standard as it’s a network admin’s computer.

  8. Okay, the Support Tech should be able to find me, given the link. I’ve also just checked on my About Me page, and put my details there, so that should help too.

    It’s interesting that you have the same issue on non-Citrix machines. It certainly will make it easier to troubleshoot.

    It *might* be an IIS related issue, seeing as you mentioned it depends on the size of the items that you restore. It could also be client side antivirus. At least, they’re the two places that I would begin looking 🙂

    • Thanks again for the offer to help. I just received an e-mail from the EV Sr. Remote Produt Specialist asking for a batch file to be run that captures registry and policy information on the client machine. I mentioned you and your blog to him on the e-mail providing him with the resulting log file. Hopefully he’s willing to share. Some techs don’t like multiple eyes on a issue so can’t say for sure he’ll do anything.

      The XenDesktop’s do not have AntiVirus running directly on them. We have it running on the server in the backend instead monitoring the remote profiles. So I can at least rule that out for you. Not sure how I might troubleshoot an IIS issue but am willing to try anything at this point. We are moving to Office 2010 and Win7 as a company and the more we do the larger this issue is becoming. Right now it’s up to just 20 machines but it will be over 100 soon.

  9. I wish I could explain why but after not hearing back from anyone in weeks I started trying some variations of the registry keys Symantec put in. I rolled my test XenDesktop images back to square one (thus removing all the keys Symantec put in to fix the issue the first time) and now it all works fine. Even the machines outside of XenDesktop are now working without change. I’m guessing either the networking crew in my IT group change a group policy (though nothing is logged in our change control) or a change on the EV server (again nothing logged in the change control recently) fixed it. Not sure if the tech ended up including you in his research or not but if you spent any time on this I appreciate your efforts!

  10. […] PSTDisableGrow and the Enterprise Vault Outlook Addin 9.0.1 […]

  11. These two fixes also worked for Outlook 2013 too 🙂

    I’m using Terminal Service too – so applied the following fixes:
    1) REG FIXES ABOVE 9 changed to the HKCU\Software\POLICIES path
    2) Installed the missing VBScript component of the MS Office Suite… read here:
    3) Changed the EV Desktop Policy | Search Behaviour to “In Browser”
    No idea why, but integrated mode didn’t work at all.

    Client worked perfectly!

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>