If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Warning: Latest Norton Auntie Virus update breaks InCD
My sister ran into a problem installing the most recent update to Norton
Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. -- http://www.standards.com/; See Howard Kaikow's web site. |
#2
|
|||
|
|||
it''s not just to InCD (this say this on their site but it really
happens to other situations as well). I have the same problem with EZ CD Creator 4.05 on WinME with Philips cdd4801 drive. It''s the symevnt.386 virtual device driver. It loads before the aspienum.vxd and seems to block some command instructions to the drive. On the update it messes with the boot sector which causes all of this nonsense. Their support also is at a loss as to how to correct this other than to uninstall and re-install. "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. |
#3
|
|||
|
|||
Can you provide a link to Symantec's site where they acknowledge it's a problem?..Much
appreciated..I have a very very slow startup now on XP PRO.. Thanks "ramses" wrote in message m... it''s not just to InCD (this say this on their site but it really happens to other situations as well). I have the same problem with EZ CD Creator 4.05 on WinME with Philips cdd4801 drive. It''s the symevnt.386 virtual device driver. It loads before the aspienum.vxd and seems to block some command instructions to the drive. On the update it messes with the boot sector which causes all of this nonsense. Their support also is at a loss as to how to correct this other than to uninstall and re-install. "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. |
#4
|
|||
|
|||
Uninstall and install does not fix the problem if you re-install the
Symantec Common Client update -- http://www.standards.com/; See Howard Kaikow's web site. "ramses" wrote in message m... it''s not just to InCD (this say this on their site but it really happens to other situations as well). I have the same problem with EZ CD Creator 4.05 on WinME with Philips cdd4801 drive. It''s the symevnt.386 virtual device driver. It loads before the aspienum.vxd and seems to block some command instructions to the drive. On the update it messes with the boot sector which causes all of this nonsense. Their support also is at a loss as to how to correct this other than to uninstall and re-install. "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. |
#5
|
|||
|
|||
I found 4 articles in Symantec's KB that refer to InCD, but none address the
problems discussed here. -- http://www.standards.com/; See Howard Kaikow's web site. "bobbyjak" wrote in message y.com... Can you provide a link to Symantec's site where they acknowledge it's a problem?..Much appreciated..I have a very very slow startup now on XP PRO.. Thanks "ramses" wrote in message m... it''s not just to InCD (this say this on their site but it really happens to other situations as well). I have the same problem with EZ CD Creator 4.05 on WinME with Philips cdd4801 drive. It''s the symevnt.386 virtual device driver. It loads before the aspienum.vxd and seems to block some command instructions to the drive. On the update it messes with the boot sector which causes all of this nonsense. Their support also is at a loss as to how to correct this other than to uninstall and re-install. "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. |
#6
|
|||
|
|||
it also breaks windows media player 9. until i reinstalled i got the
following error message: "wmp.dll has version number 9.0.0.2980 where 9.0.0.3075 was expected. who knows what's up? "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. -- http://www.standards.com/; See Howard Kaikow's web site. |
#7
|
|||
|
|||
Symantec seems to have fixed the problem.
I just ran Live Update and rebooted, no error message. The latest update adds an update to Sym Event and updates the Common Client to 1.0.8, instead of 1.0.9. -- http://www.standards.com/; See Howard Kaikow's web site. "Howard Kaikow" wrote in message ... It would help if others would report this problem at Symantec's web site. I got the usual useless response from Symantec. If enough people report the problem, Symantec will do something about it. However, I sure ain't gonna download Common Client 1.0.9 (I think that's the version number). Interestingly, I just ran Live Update. There is now also an update to SymEvent. And for Common Client, there is a big X with the following comment. "LiveUpdate could not determine if there is an update for this product because the update list for this product is corrupted." I'll boot to my test system and try the update tonight or tomorrow. -- http://www.standards.com/; See Howard Kaikow's web site. "richard j. boris" wrote in message ... it also breaks windows media player 9. until i reinstalled i got the following error message: "wmp.dll has version number 9.0.0.2980 where 9.0.0.3075 was expected. who knows what's up? "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. -- http://www.standards.com/; See Howard Kaikow's web site. |
#8
|
|||
|
|||
Hi,
That's interesting. I ran live update for NIS 2003 and received the message for Symantec Common Client Updates - "LiveUpdate could not determine if there is an update for this product because the update list for this product is corrupted." It also offered an update to Sym Event 11.3.0. After downloading this update, it states that all components are up to date - no mention of Common Client Updates. Andy "Howard Kaikow" wrote in message ... Symantec seems to have fixed the problem. I just ran Live Update and rebooted, no error message. The latest update adds an update to Sym Event and updates the Common Client to 1.0.8, instead of 1.0.9. -- http://www.standards.com/; See Howard Kaikow's web site. "Howard Kaikow" wrote in message ... It would help if others would report this problem at Symantec's web site. I got the usual useless response from Symantec. If enough people report the problem, Symantec will do something about it. However, I sure ain't gonna download Common Client 1.0.9 (I think that's the version number). Interestingly, I just ran Live Update. There is now also an update to SymEvent. And for Common Client, there is a big X with the following comment. "LiveUpdate could not determine if there is an update for this product because the update list for this product is corrupted." I'll boot to my test system and try the update tonight or tomorrow. -- http://www.standards.com/; See Howard Kaikow's web site. "richard j. boris" wrote in message ... it also breaks windows media player 9. until i reinstalled i got the following error message: "wmp.dll has version number 9.0.0.2980 where 9.0.0.3075 was expected. who knows what's up? "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. -- http://www.standards.com/; See Howard Kaikow's web site. |
#9
|
|||
|
|||
It would help if others would report this problem at Symantec's web site.
I got the usual useless response from Symantec. If enough people report the problem, Symantec will do something about it. However, I sure ain't gonna download Common Client 1.0.9 (I think that's the version number). Interestingly, I just ran Live Update. There is now also an update to SymEvent. And for Common Client, there is a big X with the following comment. "LiveUpdate could not determine if there is an update for this product because the update list for this product is corrupted." I'll boot to my test system and try the update tonight or tomorrow. -- http://www.standards.com/; See Howard Kaikow's web site. "richard j. boris" wrote in message ... it also breaks windows media player 9. until i reinstalled i got the following error message: "wmp.dll has version number 9.0.0.2980 where 9.0.0.3075 was expected. who knows what's up? "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. -- http://www.standards.com/; See Howard Kaikow's web site. |
#10
|
|||
|
|||
Me too.
You need to uninstall, then re-install NAV, then run LiveUpdate again. version 1.0.8.1 of the Common Client will be installed instead of 1.0.9. -- http://www.standards.com/; See Howard Kaikow's web site. "Andy" wrote in message ... Hi, That's interesting. I ran live update for NIS 2003 and received the message for Symantec Common Client Updates - "LiveUpdate could not determine if there is an update for this product because the update list for this product is corrupted." It also offered an update to Sym Event 11.3.0. After downloading this update, it states that all components are up to date - no mention of Common Client Updates. Andy "Howard Kaikow" wrote in message ... Symantec seems to have fixed the problem. I just ran Live Update and rebooted, no error message. The latest update adds an update to Sym Event and updates the Common Client to 1.0.8, instead of 1.0.9. -- http://www.standards.com/; See Howard Kaikow's web site. "Howard Kaikow" wrote in message ... It would help if others would report this problem at Symantec's web site. I got the usual useless response from Symantec. If enough people report the problem, Symantec will do something about it. However, I sure ain't gonna download Common Client 1.0.9 (I think that's the version number). Interestingly, I just ran Live Update. There is now also an update to SymEvent. And for Common Client, there is a big X with the following comment. "LiveUpdate could not determine if there is an update for this product because the update list for this product is corrupted." I'll boot to my test system and try the update tonight or tomorrow. -- http://www.standards.com/; See Howard Kaikow's web site. "richard j. boris" wrote in message ... it also breaks windows media player 9. until i reinstalled i got the following error message: "wmp.dll has version number 9.0.0.2980 where 9.0.0.3075 was expected. who knows what's up? "Howard Kaikow" wrote in message ... My sister ran into a problem installing the most recent update to Norton Auntie Virus 2003. Same problem might occur with other NAV versions, I do not know for sure. The most recent NAV update includes an update to the Symantec Common Client ("SCC"). Do NOT install that update. Here's what I experienced. On a system that has both NAV 2003 and InCD 4.0.5.6, I ran Live Update and installed the update to SCC. When I rebooted, I got an error message from InCD that stated something like: "Cannot connect to file system. InCD service not running." I first tried uninstalling, then re-installing InCD. Still had the problem. My gut feeling, and I do have a big gut, was that I should try uninstalling NAV. Sure enough, after uninstalling NAV, the InCD error went away. However, one cannot run a system without AV software, so I re-installed NAV 2003. Doing so does not include the latest NAV updates. After re-installing NAV, InCD still worked. So I then ran Live Update, but chose to install only the program updates for NAV and the virus definition updates. I explicitly chose to NOT install the SCC update. Voila, InCD still worked. Conclusion: There is some conflict between the updated Symantec Common Client and InCD at startup. My sister's problem had nothing to do with InCD, so the problem appears to lie in SCC. -- http://www.standards.com/; See Howard Kaikow's web site. |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Need to know if ABIT TH7II (i850) with latest BIOS update support P4 2666/133 processor | BIGdady | Abit Motherboards | 1 | January 21st 04 08:00 PM |
ECC Memory Breaks Norton Antivirus?? | Al Franz | Homebuilt PC's | 1 | January 16th 04 12:02 PM |
Norton Anti Virus 2004 sends computer into reboot loop | Glenn M | Homebuilt PC's | 6 | September 26th 03 03:31 AM |