w2k sp4 upgrade unable to connect to metabase

[Scott]

as per kb article 326964, am attmpting to resolve random
Rpcss terminations by upgrading to service pack 4.
however, each time an upgrade is attempted an SP4iis error
occurs while "running processes after installation" and
points to an inability to connect to metabase. am
currently running w2k server sp3 and am exepriencing the
exact symptoms described in kb 326964. any suggestions
would be greatly appreciated.

 

[Jim Walker]

Scott,
I am getting the exact error message on an SP4 upgrade.
Have you gotten anywhere yet? I didn't choose the restore
option, so I am somewhere between SP3 and SP4. Currently,
the server is running, but I am getting distorted pages
and some applications are not working. Did you restore to
SP3, reboot or what. I am hesitant to reboot as I don't
know what I will get. Appreciate any updates on how you
are proceeding. I can't e-mail direct as that doesn't
work either.

Jim

 

[Scott]

Jim,
This is going to sound strange but I'm glad to hear that
someone else is experiencing a similar problem. Have made
no progress in finding a resolution to the sp4iis error
but have considered a possible memory corruption as a
potential cause. There is also the possibility that my
existing RPC problem is preventing successful active
direectory access but that's speculative. I did select
the archive option and have successfully restored to sp3,
don't know if I'd recommend booting if you have not
archived. Was your decision to move to sp4 based on
sevchost.exe or RPC problems ?

 

[Arthur E. Knowles]

I found a similar problem with the SP4 upgrade and script mappings in the
metabase. Removing URLScan 2.0 before the SP4 install solved the problem.


Art

 

[Carsten]

I found a similar problem with the SP4 upgrade and script mappings in the
metabase. Removing URLScan 2.0 before the SP4 install solved the problem.


Art

I´ve the same Problem with SP4. How does it work with removing URLScan
2.0 ??!?
There is maybe a Problem with this SP, because we changed the whole
hardware and get every time the same error....

greetings
Carsten

 

[Scott]

installed Blaster hotfix from Support.microsoft.com site
and RPC failures ceased. metabase connectivity problem
directly related to RPC failures due to dependencies.

 

[Theresa]

What prompted my upgrade to sp4 was because when I tried
to install the Blaster hotfix, it said I needed sp2 or
higher - I was on sp1. Therefore, I can't apply the hotfix
until I apply SP4, but I can't apply sp4 until I apply the
hotfix! MS doesn't list SP3 or lower on their download
site. So now I'm going around in a circle. I've never
heard of URLScan - how does one go about removing it?

 

[SG]

Download SP3
http://www.microsoft.com/windows2000/downloads/servicepacks/sp3/

Apply the Hotfix afterwards....

All the best,
--
George Aker aka SG
NOTE: Please post to the group...email is invalid.





What prompted my upgrade to sp4 was because when I tried
to install the Blaster hotfix, it said I needed sp2 or
higher - I was on sp1. Therefore, I can't apply the hotfix
until I apply SP4, but I can't apply sp4 until I apply the
hotfix! MS doesn't list SP3 or lower on their download
site. So now I'm going around in a circle. I've never
heard of URLScan - how does one go about removing it?

 

[Scott]

get sp3 from
http://www.microsoft.com/Windows2000/downloads/servicepacks
/sp3/download.asp

then get the blaster patch from
http://www.support.microsoft.com

If w32.blaster is causing your RPC problems, you do not
need to upgrade to sp4. The patch seems to do the trick.

good luck