i have seen the same behaviour that uninstalling filemaker server corrupts my iis setup. Two things i have seen...
a) one website disappears (as i remember it must have been the second listed in iis console)
b) if you have ftp sites configured, all ftp sites disappear completely from iis console. and when you try to create new ones, oops, the context menu in iis console doesnt have "create ftp site" any more. So i had to go to System conrtrol, Software, Windows components, and had to remove ftp from iis, restart, install ftp again to creae ftp sites again.
System has been Windows 2003 R2, all online patches installed. And as you already have said, it is the same with Filemaker Server 9a and 10a (the small 5 user versions from technet).
Next time i have to uninstall filemaker server from my win2003, i will make a metabase snapshot of websites, ftp, and pools before uninstalling and try to reconfigure after having fmps removed.
Greetings from germany
Not sure if it's any help but I noticed on my system (2003 IIS) it was using a php.ini config file in the Filemaker folder. If it's just php files that are not working then make sure a php.ini file is in the path.
We have had the same problem with 2 different servers running Windows Server 2003. Uninstalling FMS 9 removes all web sites created after FMS 9 installation. Fortunately, we use "iisback" to backup all web site settings regulary so it was easy to restore them. But it should not happen!
We have just encountered this also, in the process of uninstalling FMS9 and Installing FMS10 on a secondary server. What is interesting, is that upon Installing FMS10, the IIS process returned to normal. Has anyone else found that to be the case, or were we just lucky?
We are using Windows Server 2003 R2 and found the same types of issues.
We uninstalled FMS 9 and installed FMS 10, and then had to do the following:
1. re-point PHP application & web service extensions in IIS to fcgiext.dll (this got wiped out)
2. re-add multiple virtual directories back to IIS (these got wiped out)
technerd (et al):
Thank you for your posts.
Here is a note regarding this issue from one of our testers...
"Yes, there are potential issues associated with the modification of the IIS default entries. In most cases with the supported IIS versions, the default uninstall/install should work as expected. I have tested with adding custom virtual directories, and the only modifications removed were under the default web site. My other entries were left intact. The other possibility is if the customer bases a second virtual directory on entries made by FileMaker Server. Then those web sites will not work. However, it should not remove the virtual directory. It appears the users have modified installations, and could be basing new custom entries from what was installed. I would be very interested in their IIS set up and all the entries they are using. With the basic install and adding extra virtual directories, I did not see this behavior"
You can either post your IIS information here, or you can send me a private message (top of this page - right side - just below the blue horizontal bar - envelope icon) with the information. I'll make sure it gets passed back to the tester.