benskolnick

Forgot to mention during the upgrade I also installed the latest FastCGI for IIS and upgraded PHP from 5.2.9 to 5.2.13. I guess it could be possible that one of these other items is causing this behavior but it seems most likely that it has to do with the Cache since I can recreate the problem reliably, as well as remedy it.

I think it might have to do with Windows Cache Extension for PHP

I had a second server running WP 3.0 from an upgrade on 2.9.2 that had no problems. When I did a fresh install of WP 3.0 on the other server it had a few dependencies and one of them was the cache extensions. Now the fresh WP 3.0 has the same issue and my brand new OS box.

Because IIS is caching the resources the deletion/creation process WP uses fails when it tries to recreate the resources that are still in the cache. Cycling IIS clears this up and the install works.

I have a feeling a lot of Sites will get hosed because of this when WP releases a 3.0.1 patch if this doesn’t get resolved before then. I recommend patching manually or cycling IIS before any patching needs to be done.

I am having the same issues. Fresh install of Windows Server 2008 SP2 fully patched running IIS7. I used the Microsoft Platform Installer to install PHP MySQL and the wordpress blog. Then I restored a previous blog from backup that I made before I re-insalled the OS to try and fix this issue.

IIS seems to be caching something because I can updated the plugins if I restart IIS right before I do the upgrade. If the site has been active for a while trying to upgrade the plugins gives me the same error you have above. Checking the directory shows a phatom folder that cannot be taken over or name changed or anything. Cycling IIS will release these resources and the folders completely disappear and then I can install the plugin again.

It seems like IIS is holding some sort of cache on the plugin resources so when they are deleted by WP IIS doesn’t know what to do and just locks those resource names so you cannot finish the update.

I never ran into this in previous versions of WP but the platform installer also adds other items like cache dependencies so it might not be a WP issue at all and could be some other piece installed by Microsoft that is causing this blockage.

I have a feeling more people will start running into this and I hope someone out there is listening.

Thanks