09-17-2010 07:25 AM - edited 09-17-2010 07:25 AM
Hello again Tim,
ok, I'm posting this here as it's an old issue that has re-appeared. I don't know if this is related to the DLL we're testing or not. Outlook is hanging on exit, requiring killing the process tree in order to clear outlook and restart it (other option is a reboot). With NIS AS off, it doesn't happen. It's intermittent and starts to happen out of nowhere. Any ideas on this?
09-17-2010 08:54 AM - edited 09-17-2010 08:55 AM
The new DLL seems to correct the error that I first posted about which popped up whenever you tried to author a new email message, specifically:
However, I also tried again disabling the AntiSpam feature within the NIS2011 Network settings while leaving the new test DLL plugin active within Outlook2010. This combination still produces the three error dialog prompts on Outlook startup that I referred to in my earlier posting, specifically,
Reenabling the AntiSpam feature in the NIS2011 settings or disabling the AntiSpam plugin within Outlook of course again halts the three errors from popping up.
09-17-2010 10:26 AM - edited 09-17-2010 11:08 AM
Just to toss in my few cents, I just tried messing with all the settings and playing around and have no errors at all (except for outlook hangs). I did however do an uninstall and reinstall using the complete download version of NIS while first testing the DLL. So, It's hard for me to say if your errors would have happened to my system if I would have played more before doing that.
Edited for blue wording...
09-20-2010 01:31 PM
I did a clean install of the OS (Win 7 Ult 32-bit) to make sure that the system was fresh. I then ran the NRT to make sure that any and all traces of any Norton software was completely removed.
09-20-2010 01:40 PM
If you're still looking for testers for the DLL update I'm willing to give it a try.
Below is the information you requested in order to participate in the test.
Outlook 2010 - Version: 14.0.4760.1000 (32-bit)
Windows 7 Ultimate SP1 Beta (32-Bit) - Version 6.1.7601 Service Pack 1, v.178 Build 7601
Norton Internet Security - Version: 220.127.116.11
09-21-2010 04:59 AM - edited 09-21-2010 05:04 AM
I'm also getting this error - using Office 2007 as well.
WinXP, SP3 is the OS, not Win 7 as others have reported.
Problem came up after an upgrade from NI2010 to NIS 2011.
I'm willing to try any new DLL's as suggested to some, in order to stop this annoying behaviour
09-21-2010 04:26 PM
Thank you for your help! We were able to confirm that this issue was indeed fixed with the updated DLL file. We should have this fixed in an upcoming update.
Thank you for your patience while we continue to test and QA the fix to ensure no other issues arise from this fix.
In the meanwhile, those of you who tested the fix should revert to your original DLL file so that future updates do not fail.
09-22-2010 11:58 AM
Thank you all for your help with these problems.
After several users in the forum verified that the original problem was fixed with the dll we sent to them, our QAs were able to reproduce that problem and verify the fix. They also reproduced the second problem mentioned by several users here ("Error found in CustomUI XML ...: Line 10 ..."). We are working on the second problem to fix it too.
09-22-2010 02:52 PM
Thank you Tim and Victor,
We certainly appreciate your team's efforts in working towards resolving these issues and also for letting us know that you were finally able to reproduce both error conditions and the resulting dialogs they trigger. Thank you too for letting us know that a final fix is now in the works. May I suggest that it might be a good idea to PM everyone who was sent the test DLL in order to let them know that they need to restore the original DLL before the final fix is released to wide distribution.
Regards & Thanks again!
09-23-2010 03:50 AM
Thanks for the headsup and answer to my question about reverting the DLL. Also thanks for working with those of us in the community that care to see things fixed quickly. Great job. If you need me to test any further for other issues or concerns, feel free to let me know anytime.