I'm not sure if the following is the solution to your problem or not,
but I'm going to post it here anyway since it is a very real problem
to which this answer may provide some benefit to the masses:
I'm running Win98SE, Norton Personal Firewall, and NAV 2002.
When Symantec put out the new version of LiveUpdate in January, I was
suddenly unable to get it to work.
When I ran LiveUpdate manually, the following occured:
1. LiveUpdate dialog comes up. I click next.
2. The progress bar for the connection to Symantec progresses 25% and
then stops. It will not go any further no matter how long you wait.
3. Iamapp.exe goes to a 'not responding' state.
4. I am unable to terminate LiveUpdate without using the Windows 'End
Task' on both the LiveUpdate task and the lucomserver task.
After weeks of poking around on the Symantec website and
experimenting, I seem to have found the solution:
1. The following website explains what's happening, and offers the
Symantec solution:
http://server1.symantec.com/SUPPORT/sharedtech.nsf/pfdocs/2003082614094613
Basically what they're saying is, a new version of LiveUpdate was
rolled out, and Norton Personal Firewall is blocking it's access to
the internet.
2. I followed the directions on the above link except for one thing: I
didn't 'Check All' after the application scan, as there were numerous
apps that showed up that had nothing to do with this. Rather, I
checked only the Symantec apps and clicked 'Finish'.
After doing this, it did add the new rules to the Firewall, but it
still wouldn't allow LiveUpdate access to the Internet.
3. I pulled up the 'View Event Log' on Norton Personal Firewall. I
found out exactly which modules were trying to access the Internet at
the time that LiveUpdate failed.
4. I went into Norton Personal Firewall -> 'Personal Firewall' ->
'Internet Access Control' and located the rules for the modules in
step 3 above (you can do a mouseover on the rule to get it to tell
you the file name it points to).
I changed the rules for Lucomserve.exe and Iamapp.exe from
'Automatic' to 'Permit All'.
After testing the above changes in steps 3 and 4, I am finally once
again able to run LiveUpdate without interference from the firewall.
Now for a not-so-humble opinion:
I think Symantec ought to be horse-whipped in public for rolling out a
software update in this manner. Both of these productions are Symantec
products, yet they can't seem to be bothered to test it before sending
it out, nor did it seem that they could be bothered to have the
installation properly create new rules in the Firewall. Had they done
this, there would have been no reason for the end-user to do anything.
I'm a paying customer for both the software and the yearly
subscriptions, and yet NOTHING was communicated directly to me or any
other paying customer notifying them that they needed to take these
steps.
Being as I'm a professional programmer by trade, I don't think it was
a reasonable expectation on the part of Symantec to expect that the
average customer could figure out the solution. Even if that were
possible, it's very presumptuous and lazy to push that responsibility
down to the customer, and have their time wasted addressing what
clearly should have been part of paid-for service themselves.
The least they could have done (though albeit still inadequate) is to
have provided clear and accurate directions spelling out what the
end-user needed to do via a large link off of their homepage. Instead
I had to dig for days to find directions that didn't work.
