After I installed NIS 2013 on my PC (running under XP, sp3, Windows all up-to-date), last week (March 29/30), I run to the famous Service Framework error. Previous to it, I had Norton 360 vs 6.0, which ended March 30. I installed NIS from the origal disk I bought in January.
The symptoms: problems NIS showing -within a few minutes after I start-up my machine, after NIS has start-ed up, the message "Symantec Service Framework encountered a problem and needs to close" pops up. If I click it away, it comes back within short time. If I start up the GUI or control screen, new instances of NIS appear in the right-down corner, they all close down successively within half a minute including the original one on the start bar, indiciating that NIS closes down completely. I also get the message my pc is not protected. The same result if I try to start the GUI using the desktop-icon (of course). So I even cannot start live-update or have it perform any other command; somewhere in an earlier attempt I did manage somehow to have it perform the live-update or a check for updates but finally I got the message it was up-to-date.
The first time I installed, during the installation NIS, indicated that it had encountered another product -or something the like) and started up un-installing that. This took a very long time (more than 45, maybe >60 min) and finally seemed to hang. When i restarted from the ROM, it started to install NIS, seemed to finish this fine, but after some time, the SSF-message and described problems occurred. Thinking that the uninstall hadn't worked out well, i downloaded and run the NRT and reinstalled; but this didn't help.
I don't remember everything exactly in the right order, but I tried I think nearly any kind of action advised in the support and many mentioned on this Forum. The version is 20.3....36, which has been downloaded somewhere during the installation procedure, because on disk was the previous version (20.2.... ). I un-installed and re-installed many times, including running the NRT 2 or even 3 times after another before reinstalling again, checking if there was something left via the control panel/software.
More then one time the automatic repair screen of NIS (don't have the exact name now) tried to repair something, two or three times it said it didn't succeed, one time it said either succesfully or it didn't find something (i forgot during HOURS of attempts, starts and restarts, uninstalls and re-installs). Didn't make a difference though.
In the beginning, I for 2 or 3 times installed from the disk-version first times, later i used the download on my account (the most actual update).
I checked if it had something to do with Firefox, but even if i didn't even look at the icon to start it up, NIS popped-up with th ssf message etc...
I updated my screen driver to the last available version, no effect.
In a final attempt to be sure everything remaining had been removed, after running NRT and restarting two times I checked the register for words like Sym, Symantec, Norton, 360, an maybe some others, and removed, run NRT again, checked the software via control panel. Run ccleaner, with in between each step restarts. Then I re-installed from the (freshly downloaded) Download in my account.
After a few minutes, again the same problems...
From the information about the error, it seems that there is a ccsvhst. problem with a verifiaction problem in comm.dll (maybe though, this is just the beginning and NIS just doesn't proceed to further problems...).
I'm not in reach of this PC now, so i cannot write down the exact numbers and verifications mentioned. I will add later in a next post. But i have the txt-file that is also made (see attachment). About the comm.dll it shows this line:
<MATCHING_FILE NAME="Comm.dll" SIZE="1392944" CHECKSUM="0x29E7DABD" BIN_FILE_VERSION="4.3.0.40" BIN_PRODUCT_VERSION="4.3.0.0" PRODUCT_VERSION="4.3" FILE_DESCRIPTION="Communications Service" COMPANY_NAME="Symantec Corporation" PRODUCT_NAME="Oxygen Client" FILE_VERSION="4.3.0.40" ORIGINAL_FILENAME="Comm.dll" INTERNAL_NAME="Comm" LEGAL_COPYRIGHT="Copyright © 2013 Symantec Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x157186" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.3.0.40" UPTO_BIN_PRODUCT_VERSION="4.3.0.0" LINK_DATE="02/02/2013 01:29:48" UPTO_LINK_DATE="02/02/2013 01:29:48" VER_LANGUAGE="Engels (Verenigde Staten) [0x409]" />
My question: anyone knows what is the reason of my problem? This pc is quite old (2000) with small RAM (256 MB), but it meets up with the requirements
What does the comm.dll do? From internet I found that it is a norton file and has something to do with its communiciation, so not a file shared by other programs which i had feared. So can i try to remove it if the NRT doesn't do so in a next run?
Anyone any other suggestions? I already spent 1,5 day... without solving the problem...