Warning: Latest Norton Auntie Virus update breaks InCD

It may not be a common thing ?
No problems with NAV 2003 and WinME + WinXP Home, on my PCs.

"Joker" wrote in message
...
No problems here with NAV 2004 Pro and WMP.


On Wed, 8 Oct 2003 19:32:09 -0400, "richard j. boris"
wrote:

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.

"Howard Kaikow" wrote in
:

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.


Same problem here, with Systemworks, 2nd liveupdate did not fix the
problem. And installing the latest symevent files from their FTP also did
not work. Next step will be an uninstall........ To bad.

It depends on when you ran Live Update.
Symantec fixed the problem less than 24 hours after I posted.

--
http://www.standards.com/; See Howard Kaikow's web site.
"Sunny" wrote in message
...
It may not be a common thing ?
No problems with NAV 2003 and WinME + WinXP Home, on my PCs.

"Joker" wrote in message
...
No problems here with NAV 2004 Pro and WMP.


On Wed, 8 Oct 2003 19:32:09 -0400, "richard j. boris"
wrote:

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.

Yes, I too had to uninstall, then re-install, then run the LiveUpdate.

--
http://www.standards.com/; See Howard Kaikow's web site.
"John Doe" wrote in message
...
"Howard Kaikow" wrote in
:

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.


Same problem here, with Systemworks, 2nd liveupdate did not fix the
problem. And installing the latest symevent files from their FTP also did
not work. Next step will be an uninstall........ To bad.

I got lucky, for once. :-)

"Howard Kaikow" wrote in message
...
It depends on when you ran Live Update.
Symantec fixed the problem less than 24 hours after I posted.

--
http://www.standards.com/; See Howard Kaikow's web site.
"Sunny" wrote in message
...
It may not be a common thing ?
No problems with NAV 2003 and WinME + WinXP Home, on my PCs.
snip

I have ecactly the same Error without having installed NAV.!

"Howard Kaikow" wrote in message ...
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.

"Howard Kaikow" wrote in message ...
Yes, I too had to uninstall, then re-install, then run the LiveUpdate.

--
http://www.standards.com/; See Howard Kaikow's web site.
"John Doe" wrote in message
...
"Howard Kaikow" wrote in
:

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.


Same problem here, with Systemworks, 2nd liveupdate did not fix the
problem. And installing the latest symevent files from their FTP also did
not work. Next step will be an uninstall........ To bad.



I too ran liveupdate but that did not fix my problem. And it happens
on some machines because of the hardware/software combo. I have heard
of this happening with cd-rw drives that use aspi layer for their
instructions as opposed to the usual driver layer (2 different things
- aspi layer gives better performance).

Here is a link that they talk about this issue:

http://service1.symantec.com/SUPPORT...is&svy=&csm=no

I have not found it yet but there is another ""article"" buried very
deep that recommends uninstalling and re-installing their software.

That article is the typical Symantec BS, at least as far as InCD is
concerned..

My problem was solved when they released the new version of SymEvent and
killed version 1.09 of the Common Client, issuing 1.08 of the Common Client.

I had to uninstall, then re-install NAV, but that was due to their
corruption of the Common Client with 1.09.


--
http://www.standards.com/; See Howard Kaikow's web site.
"ramses" wrote in message
m...
"Howard Kaikow" wrote in message
...
Yes, I too had to uninstall, then re-install, then run the LiveUpdate.

--
http://www.standards.com/; See Howard Kaikow's web site.
"John Doe" wrote in message
...
"Howard Kaikow" wrote in
:

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.


Same problem here, with Systemworks, 2nd liveupdate did not fix the
problem. And installing the latest symevent files from their FTP also
did
not work. Next step will be an uninstall........ To bad.



I too ran liveupdate but that did not fix my problem. And it happens
on some machines because of the hardware/software combo. I have heard
of this happening with cd-rw drives that use aspi layer for their
instructions as opposed to the usual driver layer (2 different things
- aspi layer gives better performance).

Here is a link that they talk about this issue:


http://service1.symantec.com/SUPPORT...is&svy=&csm=no

I have not found it yet but there is another ""article"" buried very
deep that recommends uninstalling and re-installing their software.