<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Fixing vpmsece.dll errors in outlook</title>
	<atom:link href="http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/feed/" rel="self" type="application/rss+xml" />
	<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/</link>
	<description></description>
	<lastBuildDate>Wed, 01 Feb 2012 15:36:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: anon</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-942</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Fri, 07 Jan 2005 07:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-942</guid>
		<description>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.
</description>
		<content:encoded><![CDATA[<p>Creating the NavNT folder under Program Files and copying the offending .dll to that folder is the quick and dirty fix.</p>
<p>Works here.  W2K, sp4. SAVCE 9.0.0.338</p>
<p>Thanks, and thumbs-up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Reddy</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-941</link>
		<dc:creator>Jeff Reddy</dc:creator>
		<pubDate>Tue, 21 Dec 2004 23:42:29 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-941</guid>
		<description>David Sharpe wrote:
After deleting the extend.dat file and starting Outlook, it just recreated itself.


That is the idea. What&#039;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&#039;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.
</description>
		<content:encoded><![CDATA[<p>David Sharpe wrote:<br />
After deleting the extend.dat file and starting Outlook, it just recreated itself.</p>
<p>That is the idea. What&#8217;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&#8217;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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Sharpe</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-940</link>
		<dc:creator>David Sharpe</dc:creator>
		<pubDate>Fri, 19 Nov 2004 02:12:40 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-940</guid>
		<description>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.
</description>
		<content:encoded><![CDATA[<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-939</link>
		<dc:creator>Philip</dc:creator>
		<pubDate>Thu, 14 Oct 2004 15:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-939</guid>
		<description>Thank you. Deleting the LDVP registry entry worked for me.
</description>
		<content:encoded><![CDATA[<p>Thank you. Deleting the LDVP registry entry worked for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jules</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-938</link>
		<dc:creator>Jules</dc:creator>
		<pubDate>Wed, 09 Jun 2004 21:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-938</guid>
		<description>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
</description>
		<content:encoded><![CDATA[<p>Hi, Jeff.<br />
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.<br />
Good luck,<br />
Jules</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-937</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Thu, 06 May 2004 00:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-937</guid>
		<description>Jules, that was the first thing Google pulled up and it didnt work for me at all.  I&#039;m going to try a few suggestions from above.
Jeff
</description>
		<content:encoded><![CDATA[<p>Jules, that was the first thing Google pulled up and it didnt work for me at all.  I&#8217;m going to try a few suggestions from above.<br />
Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jules</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-936</link>
		<dc:creator>Jules</dc:creator>
		<pubDate>Wed, 07 Apr 2004 23:22:17 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-936</guid>
		<description>Michele&#039;s &quot;uncheck the LDVP property&quot; is very inadvisable because you will no longer have protection against the viruses which can be detected by email scanning. Here is a URL to a document which explains in detail how to solve the problem: &lt;a href=&quot;http://www.tencorp.com/SALESTIP.NSF/0/da53a778550acfae85256e130057d2ec?OpenDocument&quot; rel=&quot;nofollow&quot;&gt;http://www.tencorp.com/SALESTIP.NSF/0/da53a778550acfae85256e130057d2ec?OpenDocument&lt;/a&gt;
</description>
		<content:encoded><![CDATA[<p>Michele&#8217;s &#8220;uncheck the LDVP property&#8221; is very inadvisable because you will no longer have protection against the viruses which can be detected by email scanning. Here is a URL to a document which explains in detail how to solve the problem: <a href="http://www.tencorp.com/SALESTIP.NSF/0/da53a778550acfae85256e130057d2ec?OpenDocument" rel="nofollow">http://www.tencorp.com/SALESTIP.NSF/0/da53a778550acfae85256e130057d2ec?OpenDocument</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-935</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Fri, 02 Apr 2004 00:11:42 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-935</guid>
		<description>Michelle&#039;s fix worked for me!  I don&#039;t know what else that LVDP might have done for me though.
</description>
		<content:encoded><![CDATA[<p>Michelle&#8217;s fix worked for me!  I don&#8217;t know what else that LVDP might have done for me though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Me</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-934</link>
		<dc:creator>Me</dc:creator>
		<pubDate>Tue, 16 Mar 2004 22:32:15 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-934</guid>
		<description>what you have to watch out for with Michele&#039;s solution is that it doesn&#039;t actually ensure that you have the antivirus plugin loaded. All this does is remove the software.
</description>
		<content:encoded><![CDATA[<p>what you have to watch out for with Michele&#8217;s solution is that it doesn&#8217;t actually ensure that you have the antivirus plugin loaded. All this does is remove the software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://absoblogginlutely.net/2003/10/fixing-vpmsecedll-errors-in-outlook/comment-page-1/#comment-933</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Fri, 12 Mar 2004 04:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://absoblogginlutely.net/migrate/?p=1583#comment-933</guid>
		<description>Michele&#039;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!
</description>
		<content:encoded><![CDATA[<p>Michele&#8217;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!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: absoblogginlutely.net @ 2012-02-11 23:12:13 -->
