This will only occur on installations of Internet Scanner that have been
previously uninstalled and then installed. What happens is the first XPU from
SiteProtector (7.0.1) will fail with the "CommNotify" Error, a second attempt
to install the XPU will yield the "Installation of update failed" Error. By
editing the issdaemon.policy, you are letting the XPU take the second time, but
will fail on the next.... and so on... and so on with this:
=======================================
"Installation of update failed.ERROR: CommNotify - the wait for an event timed
out. [ID=0xc742000e]"
and then
"Installation of update failed. The update package has already been installed
on this component. An update cannot be installed more than once. Uninstall it
before trying this operation. [ID=0x8733002d]"
=======================================
What is going on is the follwoing. The XPU gets transferred over to Internet
Scanner, runs itself, and UNINSTALLs itself because of InstallSheild
information left over from the previous install (look at the .xml logs in
C:\WINNT\ that the XPu creates - you will see install, then uninstall, then
install, etc.). Because InstallSheild thinks the XPU is applied, it will
uninstall the XPU instead of installing it and the Installsheild information
gets removed, so that after you edit the daemon and apply it again.. this info
is not there and the XPU will apply, but the next will uninstall... etc. etc.
Here's how to fix it. Stop the issDaemon. Determine the XPU that is installed
successfully at this time (look in the modules directory of the scanner) and
remove the directories below so that the updates will install rather than
uninstall. Before you reinstall make sure all these are gone or you will run
into this problem again and again:
.\Program Files\InstallShield Installation Information\
7.0.1 - {AABB0300-3801-11D4-812E-00902774099E}
7.0.2 - {5128CA7A-947A-43F3-A4E9-ED87E0EBEE30}
7.0.3 - {11CB6BBB-3357-4529-9C15-1B1EA84F7E6E}
7.0.4 - {11CB6BBB-3357-4529-9C15-1B1EA84F7E6F}
7.0.5 - {D43A87BE-CB2D-43CB-8F8D-D52850669F9F}
7.0.6 - {FFAA0706-3801-11D4-812E-00902774099E}
7.0.7 - {FFAA0707-3801-11D4-812E-00902774099E}
7.0.8 - {FFAA0708-3801-11D4-812E-00902774099E}
7.0.9 - {FFAA0709-3801-11D4-812E-00902774099E}
7.0.10 - {FFAA0710-3801-11D4-812E-00902774099E}
Forgot what the GUIDs are for XPUs, 7.0.11-7.0.13 are. TechSupport can help you
out there (or look in the uninstall .xml file in C:\Winnt if you already
applied these previously - should be somewhere in there)
==============================
Hey,
It seems as though there are a few things contributing to the timeout�s I have
noticed while updating the Internet Scanner. Firstly renaming the scanner
sensor name to all lower-case allowed the procedure to begin, however only one
update installed and it continued to hang.
A work-around I discovered was to delete the later XPU�s presence from the
issDaemon.policy file located on the scanner machine and re-apply one at a
time, reboot the scanner and restart all services on the SiteProtector machine.
This one XPU will now install, and each XPU requires that exhaustive procedure.
The sensor history looks like:
[date] Apply Update Completed
[date] Apply Update Unknown
[date] Apply Update Completed
[date] Apply Update Unknown
�
If I don�t do this the two outcomes are an indefinite hang waiting for the
remote machine to complete, or an error saying the remote machine already has
the XPU installed (even though RealSecure doesn�t recognize this).
Anyone had the same problems? Any comments and suggestions are welcome.
-a
_______________________________________________
ISSForum mailing list
[EMAIL PROTECTED]
TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to
https://atla-mm1.iss.net/mailman/listinfo
