Fixing vpmsece.dll errors in outlook

when you open your first email after starting Outlook, you see the error message Error: “VPMSECE.DLL could not be installed or loaded. It may be missing or there may not be enough resources.” The error message may or may not reference a location, as in: “C:\Program Files\NavNT\vpmsece.dll could not be installed or loaded. It may be missing or there may not be enough resources.”
The documented solution is to uninstall the symantec security client, delete extend.dat (search your computer for this file) and start outlook. If this doesn’t work, reinstall outlook (in my case office). There is no way I was going to uninstall office and then reinstall it so I went hunting.
10 minutes later I had a solution.
A quick search on the registry for vpmsece.dll comes up with LDVP under hklm\software\microsoft\exchange\client\extensions. Disabling LDVP under tools/options/other/Advanced Options/AddInManager and restarting Outlook and everything was ok. Re-enabling the extension and the problem re-occurs.
Deleting the registry entry hklm\software\microsoft\exchange\client\extensions\LDVP and restarting outlook means I don’t get the error message and the LDVP addon is not listed in the registry.
I then installed Symantec Client Security again and all seems to be ok. The cryptic LDVP has been replaced with SavCorp810 in the extension manager which is a lot easier to work out what the extension is.

23 thoughts on “Fixing vpmsece.dll errors in outlook

  1. I deleted extend.dat too – problem just repeats itself when outlook starts. Whats the real fix? Roger.

  2. ok – if you don’t understand registry settings or not confident about changing your registry settings then show this to someone who does.

    The steps you need to do are as follows:-

    1.Exit and logoff of outlook
    2.delete extend.dat from your computer (start/search/find files, extend.dat in c:\
    3. click, start, run and type regedit (hit return)
    4. navigate to hkey_local_machine\software\microsoft\exchange\client\extensions
    5. Select ldvp in the right hand side and press delete yes to any “are you sure” prompts.
    6. Close regedit
    7. Start outlook.
    8. Try to read the body of an email and ensure that you do NOT get the error message. If you do, then unfortunately my fix did not help you.
    9. If you can read ok with no error message then reinstall Symantec AntiVirus

  3. Deleting extend.dat worked for me. Needed to turn on advanced settings’ search hidden files and folders to find extend.dat

  4. Me: Your process worked for me. I had to uninstall SAV 8.1 and reinstall again in the last step to see SAV listed again in Add-In Manager in Outlook 2000.

  5. Comment? Sure. It’s too bad screams of outrage can’t be heard from helpful sites like this one!

    Most of us hate new laws — especially unenforceable laws — but we ought to have a special law for programmers who foist mind-boggling errors, such as the NavNT\vpmsece.dll dilemma, on those of us who aren’t computer-literate.

    Dammit, when MS or whomever releases software the software should work. Period.

    How about a couple of weeks in a Chinese work-camp for any programmer who doesn’t do his homework and releases such garbage on an unsuspecting public? Or, if the programmer is being pressed to release applications prematurely, how about TEN years in the same slammer for the programmers boss, or TWENTY years for the CEO?

  6. Has anyone else (besides me, that is), had any success simply
    1) Creating a subdirectory C:\Program Files\NavNT
    2) Copying the vpmsece.dll file from C:\Program Files\Symantec_Client_Security\Symantec AntiVirus
    3) Pasting the vpmsece.dll into the C:\Program Files\NavNT

    and then restarting Outlook?
    Or have I created more problems than I fixed?

  7. “Disabling LDVP under tools/options/other/Advanced Options/AddInManager and restarting Outlook and everything was ok”

    It was as simple as that for me!
    No registry change.
    No deleting files.
    Just a simple ‘click’ on a box…

  8. I created the directory C:\Program Files\NavNT\ and in this folder added a shortcut to vpmsece.dll. After doing so, I still received the error message upon restarting MS LookOut! So, I actually copied the file to the new folder, and after that was able to start the program with no error.

  9. Michele’s post is for those who have the problem after completely removing NAV, and all the registry editing and extend.dat deleting fails to works. Thanks Michele!

  10. what you have to watch out for with Michele’s solution is that it doesn’t actually ensure that you have the antivirus plugin loaded. All this does is remove the software.

  11. Michelle’s fix worked for me! I don’t know what else that LVDP might have done for me though.

  12. Jules, that was the first thing Google pulled up and it didnt work for me at all. I’m going to try a few suggestions from above.
    Jeff

  13. Hi, Jeff.
    Try uninstalling the current version of NAV, reboot, delete ALL instances of extend.dat on the hard-drive, remove ALL references to vpmsece.dll and all remnant keys related to NAV in the registry, reboot, and then install the new version of NAV. It worked for me on several machines.
    Good luck,
    Jules

  14. Thanks to everyone. Disabling the LDVP under tools did it for me. After deleting the extend.dat file and starting Outlook, it just recreated itself.

  15. David Sharpe wrote:
    After deleting the extend.dat file and starting Outlook, it just recreated itself.

    That is the idea. What’s happening is that the extend.dat file is created, based on values from the registry. However, when installing anti-virus software, the registry values are changed but the extend.dat file isn’t updated with those changes. However, by deleting the file, Outlook detects that and rebuilds the file with the correct settings. So, you are not deleting the file as if the file is the problem, you are deleting the file with bad data so that it will be replace by another file with the correct data.

  16. Creating the NavNT folder under Program Files and copying the offending .dll to that folder is the quick and dirty fix.

    Works here. W2K, sp4. SAVCE 9.0.0.338

    Thanks, and thumbs-up.

Comments are closed.