02-01-2012 07:08 AM
Hi, erm i did read all the thread, what exactly do you feel i missed ?
I wasn't responding to you, I was responding to Nobby. I thought quoting his post would make that clear.
02-01-2012 07:11 AM
I have the problem on my desktop computer but not on my laptrop. The both have the same configurations. Ofice 2007 and Windows 7 64bit. Is I pssted in another thread I had no problems with the NIS update on my laptop but could not install the NIS update on my desktop until I uninstalled NIS an reinstalled it again.
02-01-2012 11:07 AM
I can''t open Word-documents directly. An error says you have a open dialogbox and OK and than the document opens.
I did a systemrestore, repaired Office, made registerschanghes and hour after hour I worked on it. Normal.dot new, changed etc. etc.
Suddenly I remembered yesterday there was a change (update) in the NIS engine and had to restart. So I looked and disabled scan of Microsoft Office. Now the document are opening directly at once.
So this is a bug of Symantec software. What are you doing? Can't you check things before you change them. It cost me more than 4 hours.
I can't use the function Automatic scan of MS Office in NIS anymore!
02-01-2012 12:09 PM
Thank you all for your replies. My message was moved from another section of the Community Forum (Norton360 Beta) to this discussion. The reason it was in this section was because I did a search on the error at hand and it took me to Norton360 Beta discussion forum as the same error is beening discussed there I did not realize that there was another forum section discussing this error. Norton Please Explain why there are two discussions with the same problem running at once, If you decided to move my reply to another post why can't you move all of other persons that have the same error from the Beta forum to this forum.
"over a month read Microsoft's Support page on this error. Http://support.microsoft.com/kb/891986 which clearly states that this error started on the 18 September 2011.
02-01-2012 04:53 PM
To all you Norton apologists out there:
This problem has existed for over a month, considering that Microsoft first noted the problem back in September. And whether security has been compromised or not is irrelevant. Security software should never interfere with the normal operations of a computer. When it does, the error should be corrected immediately. This error is not confined to one or two products, but every one of their products that uses their antivirus engine. So it's not just Norton AV and NIS, but also Symantec Endpoint Protection that is affected by this problem. That means that businesses are being affected by this problem on an enterprise wide scale. Companies like my clients, who trusted me when I recommended Symantec products, but are now questioning that trust because those products are interfering with their productivity. And this error is not confined to merely double clicking on a Word file to open it, but is also completely preventing some of my clients from opening Word files that are attached to emails.
The amount of time it has taken Norton/Symantec to address this issue is unacceptable. For those of you who feel that you need to defend the company from those of us who are rightfully upset with this inexcusable delay, I recommend that you not waste your time. They have lawyers and PR people that they pay good money to do that for them. We have every right to be upset with them and express that frustration in order to pressure them into doing what should have been done long ago - fix their own mistakes. I cannot fathom why you would stick up for a company whose product you pay for, when that product fails because the manufacturer screwed up - and continues to screw up by failing to address the issue in a timely fashion.
02-01-2012 05:51 PM
SEP also has this issue? I am unable to find any reports of it on the enterprise product forums. Can you provide a link? Up until it appeared in the 19.5 update, the only reports I am aware of were for the Norton 360 beta - and while you might expect a fix prior to going RTM, it would not be unusual to see such a bug in a beta product.
02-01-2012 06:16 PM
I checked the date of the officeav.dll - it was replace withthe latest update. As I previously stated my laptop and desktop have the same configurations - both with Office 2007 - the desktop has the problem but the laptop does not, so I doubt it is just the officeav.dll file causing the problem.
02-01-2012 08:25 PM
I have personally seen this error occur on machines with NIS and SEP - non-beta versions. So I have no link to provide you. Of those machines, I have seen some running Office 2007, and some running Office 2010.
02-02-2012 02:28 AM
To Tim Lopez (Symantec Corporation):
As per my earlier suggestion re the problems caused by the NIS 2012 version 220.127.116.11 update (i.e. problems opening Word 2007 documents and, more importantly, Identity Safe apparently not autofilling bank logins anymore), can I implore you to seriously consider withdrawing this release and rolling back to the previous version?
I know there are probably other issues that Norton has fixed with this latest release, but the new problems are, in my opinion, more of an issue than the shortcomings of the previous version.
If you don't consider this necessary, or if other users don't agree, perhaps you could get Norton to give users the option of reverting to the previous version (and finding a way not to get LiveUpdate it to upgrade it to the 19.5 version until 19.5 has been fully tested with these important issues fixed).
I, like others, have paid for NIS and as such believe you should give us the option of choosing when to update to the latest release, rather than Norton doing a "push" update when it sees fit to do so. That is, users should always have the option to retain (or revert to) the previous version if we want to, without LiveUpdate forcing the new version on us until we are ready and happy to receive it.