Autopatcher lockup bug
Posted 12 July 2008 - 08:28 AM
Screenshot attached - has anyone seen anything like this before? (link to screenshot) (left running overnight in case it was running slow, rather than failing)
May be connected somehow to this one -- same shared APUP download folder, but being used to update a different machine.
Posted 15 July 2008 - 07:55 PM
I'll take a look into this one. Your screenshot indicates that you have six other updates, is it always locking up on GPMC? I've never had any issues installing GPMC on a fresh Server 2K3 image but I'll make sure.
In the mean time, go to the components\GPMC_x86_files and run gpmc.msi. What error do you receive?
Posted 16 July 2008 - 05:33 AM
Let me know what happens when you try to install GPMC manually.
Posted 26 July 2008 - 10:35 AM
There have been fairly well documented random instances of the DNS patch destroying Windows 2003 servers due to a port conflict. These are not reproducible on other servers because of the randomization element in the 2500 ports chosen by the patch. Registry edits to solve this are, by now, quite well known.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users