Hi.
Windows 2003 sp1 broke websites that utilized IIS6.0 + FPSE 2002 about 1
year ago +/-. The breakage was similar to what Lisa describes above.
We had to remove sp1 in order to get the websites to work again.
For the longest time there was no resolution - only the typical know-it-alls
posting telling us we were not the sharpest tack in the box for utilizing
FPSE 2002 rather than running other types website servers.
We eventually had the problem resolve itself when the system crashed and we
installed from fresh a different server o/s.
To reiterate:
The best fix - at the time - was to just remove SP1 (do not remove IIS6.0 or
FPSE 2002 - just roll back the sp1)
Although I monitored the ngs periodically - I did not consistently monitor
them sufficiently to state if a better resolution became apparent. We had
to lock up our server in other ways to prevent vulnerabilty intrusions.
I will look to see if I have the posts anywhere because if one did not
follow in a set sequence the whole system was broken (eg: it is best to NOT
uninstall FPSE & IIS6.0 as some were directing us).
Hope this helps.
Lisa said:
I've Windows 2003 SP1 suddenly a shared folders that the users used to
access became read only and i cann't manage by any means to get it
back to read write !!!! what can be the reason for that and how can i
solve this?
Although it may appear to be read-only, folders are never read-only and the
read-only attribute is ignored for
folders.