To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87938 Issue #|87938 Summary|Vista x64/Windows Search/Norton 360 V2.0/Windows Mail Component|Installation Version|OOo 2.4.0 Platform|All URL| OS/Version|Windows Vista Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P1 Subcomponent|code Assigned to|of Reported by|rhens
------- Additional comments from [EMAIL PROTECTED] Sun Apr 6 06:12:21 +0000 2008 ------- Windows Vista x64 Norton 360 Version 2.0 Latest Open Office Suite, Complete Install, All Office Compatibility Don't get too excited just yet, but please do read in full. I am very concerned that this is a strange and complicated problem that unfortunately may fatally disable Norton 360 Version 2.0 and damage Windows Search registry keys on thousands of PCs. I am not sure, but this needs further investigation. Let me make clear that if this is the case that this is a problem with Windows, Open Office, and Norton, not one or the other, and may actually not involve Open Office at all, though I need you to confirm that, quickly. I can't confirm that my source information is accurate either and my interpretation of it all may be flawed. I need some sort of expertise to assist in determining any and all of that because I just am not skilled enough to know, but it is potentially serious. Recently I installed the new Open Office 2.4. To my surprise, the day I did I noticed someting odd. My Symantec Norton 360 Version 2.0 suddenly stopped working and started to return errors. The errors are generic, but basically they stop a critical service from running. A reboot restarts the services, but they soon fail again, for reasons explained below. As I started to investigate, I discovered, after reading a few dozen forums online, that the problem may have something to do with a defect in Norton with dll files and that a patch has since resolved the issue. Having updated Norton 360 version 2 to the fullest, I started to wonder what else might be wrong. I kept searching and discovered that in my event viewer Windows tells me: -- "WinMail (3148) WindowsMail0: The database engine stopped the instance (0)." -- "Faulting application ccSvcHst.exe [A Symantec Service]...." -- "The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered." Researching further I discovered that MS is aware of an issue in Windows Vista x64 that causes the last error to appear, but that it should be ignored by Windows as "information." I found some people online, however, who seem to have linked that to a problem in Windows Mail. I noticed that it happened often when I did check my e-mail. I found one site claiming to have resolved that by altering the registry. I tried to do the same. To my surprise, this had something to do with Windows Search needing those keys in order to search for e-mail in Windows Vista. When I re-opened Windows Mail, it gave me some sort of message about reloading files, after I added the changes to the registry, and I could see it was making changes per my registry modifications. Shortly after though, I had the Symantec Norton problem again. Researching further, some programmers I read online suggested that the problem was relarted to Windows Search looking for 64-bit files for searching in a system folder, WOW64, and that these did not exist because the program was inherantly 32-bit. They said, I believe, that some APIs look for 64-bit extensions or something to that effect and that these simply do not exist, so Windows returns errors as if registry keys are missing when they are not. I looked deeper into that, and lo and behold I found 1 blog where a user described linking that to the functions of Norton 360. It all started to make sense. Although, I wondered what in the world started all of this in the first place. I was concerned it was Norton, naturally. So, I contacted Symantec, which as usual played dumb and could not assist me. They insisted that the problem was a Windows issue, which it partially is, but that they had no more information in their knowledge base. I have never had success with them, period. I kept looking after that. What I found next may shed some real light. I started looking more closely at other things coming up on my searches on Google and noticed that other people kept mentioning that this problem only occurrs when you have Microsoft Outlook installed. That hit me like a ton of bricks that the only thing evenly remotely close to that ever put on this PC was Open Office, which just so happens to recognize Office file types. I have never had MS office on this PC, no word, nothing, except perhaps Windows Mail itself, which may be a "lite" Outlook as it were if you understand my drift from a technical standpoint. I am now suggesting though that also perhaps some application extensions of Open Office may utilize some of the same things/paths/whatever that office did, and just like Outlook, Open Office has now become the source of the search error, which in turn disables Norton. That would mean, if true, that anyone with Norton 360 2.0 and Open Office 2.4 may now have the same problem. At present, I know no solution that works, nor have I confirmed that anyone other than me has this problem. Reinstalling Windows Search is also futile. I am reluctant to uninstall Open Office, and it works fine, as does windows and WMail, as MS said, but then my Norton is DOA, since it is or would be in this situation the only program not designed to ignore the error, which may be good since it is a security suite, but it may be dependant on Windows Search to search in Vista you see, so... Given the very incomplete, possibly inaccurate, completely undocumented, and strange and mangled research I have here, I really need the assistance of some sort of expert(s) to sort all of this out and see if it can even be reproduced. I have no other options to test and figure this out/nobody to call, and of course if this is somehow right then thousands may have a problem. I would appreciate any and all assistance that you may provide. I wish I would have kept a log of sites I visited, inclusing official support sites which I moved through, but I did not and have deleted my history without thinking. Perhaps using better methods someone else may find the same or better information. In any case, please investigate to be sure it is not Open Office causing the issue. If nothing else I simply want to be the boy who cried wolf rather than find out later that my odd suspicions were in the ballpark and nobody even knew to look into it. Thanks for listening to me anyway ;P, Ryan H. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
