Norton Internet Security / Norton AntiVirus

[avjohnnie]

Just checking in to find out how well the final fix is coming along …

Regards,

John Burns

Software Research

[Tim_Lopez Administrator]

Hi John,

We are going to include the fix with one of our upcoming inline patches. You may continue to use the workaround if you wish in the meanwhile. Please keep in mind that future patches may fail if you're using the unreleased DLL when the patch is distributed. Keep the old DLL handy. 

I don't have a time-frame yet for the patch, so I'll just say "in the next few months". As we get closer to the release, I may be able to publicly communicate a more precise time-frame. 

Thanks for your patience!

[DitroniX]

Jus to add that this delay in resolving this correctly is not very professional.

We have had histrorical issues with Symantec which is why we moved to another provider.  Out of curiosity I though I would download NIS2011 and was impressed with its speed and lower resources than previous versions.  However getting the described error in this thread and tha fact that the AntiSpam folder is not displayed, together with no ability to mark mail as spam or not, it not good!

Guess we will keep with our other provider and probably continue not to recommend Symantec to customers.  After all, if we have isues and we work in IT, then its an unwanted headache to support your issues for our customers too!

[AllenM Norton Fighter]

Hi Folks,

I thought I would chime in with my two cents worth on this one.

I myself am a software engineer and have worked in this industry for over 20 years.

Though I know a problem like this is frustrating I also feel very strongly that Symantec is taking this problem very seriously. But they do have to strike a balance between speed of resolution and release to the world wide community vs proper Quality Assurance. If you act too quickly to release a formal fix for something like this you run a significant risk of introducing new problems and I know none of us want that to happen.

As referenced earlier in the thread Symantec released patches to a few people who requested it. I think this also strongly indicates that Symantec is taking this very seriously.

So I think we need to let this play out and support Symantec in doing proper Quality Assurance.

Just my thoughts on the matter.

Best wishes All.

Allen

[ourclemonsfamil]

We agree.  We tested the DLL and are happy to have had the chance to help with this.  I have seen the changes with NIS over the years and am now happy to suggest NIS.  All software has an occasional blip that must be fixed, but with the right timing.  This is a minor blip and should be tested and allowed that timing to prevent any further ones.

[thelion99]

hi,

I had the same error messages after I upgraded to NIS 2011 last night. I contacted Norton Support, which promptly informed me I had to remove and reinstall Norton. I didn't agree with this, and eventually ended the session with "Praveen" then did my own research. Here's what I found out. If you've already resolved the error, I apologize for the intrusion.

The error is caused by a failure to properly initialize a call within the new version of NIS 2011. Simply put, something changed within the NIS 2011 code that caused working code within OL to fail. There's no way to disable error messages for add-ins within OL 2007 (that I could find) so I went in to MS Word, chose Word Options | Add Ins | Disable Error Messages. While the error condition still exists between OL 2007 and the new version of NIS, the functionality of OL 2007 and NIS are not affected. So, I basically told all MS ribbon applications to ignore add in errors. I closed OL 2007, reopened it, and viola! no more annoying error messages.

Don't listen to NIS support - they will take you down a path that won't fix the problem and will waste your time. Good luck!

[Tomos12]

Hi thelion99

I have the same problem with NIS2011 and OL 2007 Pro an I was succesfull in disabling error messages for add-ins within OL 2007 : Menu Tools | Options | Other | Advanced Options, then disable "Show add-in user interface errors".

At my side (Vista Ultimate 32-bit) worked fine, however I would prefer Symantec finally solves this long present problem.

[avjohnnie]

---

Tomos12 wrote:

Hi thelion99

I have the same problem with NIS2011 and OL 2007 Pro an I was succesfull in disabling error messages for add-ins within OL 2007 : Menu Tools | Options | Other | Advanced Options, then disable "Show add-in user interface errors".

At my side (Vista Ultimate 32-bit) worked fine, however I would prefer Symantec finally solves this long present problem.

---

FWIW:

Symantec’s development team did come up with an updated plugin DLL for this back in September, shortly after the problem was first discovered.  A few of us were selected to test and verify that it corrected the problem.  Shortly after that however, we were instructed to revert to the original DLL in order to prevent problems arising from subsequent LiveUpdates.  And so we are all still waiting.  My guess is that their team subsequently discovered other (and possibly worse) issues with the test version that we received. My solution for this has been to fully disable the plugin and simply rely on Outlook’s built-in spam filter solution.

ALSO NOTE THAT:

Since then I’ve also discovered that NIS2011’s firewall inhibits the Windows7 TRACERT command unless you first disable the NIS Stateful Protocol Filter.  Supposedly they’ve been working on a fix for this problem as well, and for about the same amount of time that they been working on the Outlook plugin problem.

Regards,

John Burns

Software Research

[ourclemonsfamil]

The problem with Outlook has been fixed it seems.  I re-enabled the plugins and changed the setting back in Outlook after the last updated version was installed, and don't have the errors.

NIS Version: 18.5.0.125

[SendOfJive Norton Fighter]

18.5.0.125, which is still not yet generally available, is also said to fix the tracert problem as well.  As soon as it is released to distribution by LiveUpdate, both of avjohnnie's issues should be resolved.