K
Kevin Wallace
Hi,
After days of trying I have found a way to cleaning
install SP4 on my cluster system. Previously I was getting
ScriptMaps and regsvr32 errors during the 'sp4iis.exe'
processing part, for which I posted the question but never
received an answer that worked.
Although I stopped all non-essential services before the
installion it appears that launching the SP4 installation
program (update.exe) starts the IIS Admin Service - after
launching the update program leave it in the
first 'Welcome' window for around 20 seconds, then check
the tasks that are running. If 'inetinfo.exe' is one of
them stop the IIS Admin Service using the Windows Service
Controller.
Now continue with the SP4 installation and, hopefully, you
will have no ScriptMaps or regsvr32 errors. (Note inetinfo
will start during the sp4iis.exe installation part but
that is okay)
BTW: After the installation I checked the IIS Metabase and
found the '.htr' map had been updated.
So it looks like the SP4 installation 'may' have a bug in
it.
Hopefully this works for you too - comments are welcome
(particulary from MS as to when they will fix it!)
Kevin
After days of trying I have found a way to cleaning
install SP4 on my cluster system. Previously I was getting
ScriptMaps and regsvr32 errors during the 'sp4iis.exe'
processing part, for which I posted the question but never
received an answer that worked.
Although I stopped all non-essential services before the
installion it appears that launching the SP4 installation
program (update.exe) starts the IIS Admin Service - after
launching the update program leave it in the
first 'Welcome' window for around 20 seconds, then check
the tasks that are running. If 'inetinfo.exe' is one of
them stop the IIS Admin Service using the Windows Service
Controller.
Now continue with the SP4 installation and, hopefully, you
will have no ScriptMaps or regsvr32 errors. (Note inetinfo
will start during the sp4iis.exe installation part but
that is okay)
BTW: After the installation I checked the IIS Metabase and
found the '.htr' map had been updated.
So it looks like the SP4 installation 'may' have a bug in
it.
Hopefully this works for you too - comments are welcome
(particulary from MS as to when they will fix it!)
Kevin