Have you tried recovering one of these files and tested the recovered copy?
Things to keep in mind about Recover:
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
Yes, I took one file offline, then performed recovery on the file through Filemaker Pro. No problems or issues were found. I then published that file and the same problem exists.
The person who did the reboot indicated that he also updated .NET to NGEN V4.0.x. Is .NET used with Filemaker ?
Problem appears to be resolved. Since I knew that .NET was upgraded, I checked IIS and it was using the new version of .NET as seen under the ASP.NET tab. I changed the version back to V2, restarted IIS, and all 46 Filermaker database are now accessible on the web server! Person who did the reboot said it had been V1 prior to this change which I learned after making the change to V2 with IIS.
When I open one of the database with Filemaker Pro, however, all of the options under "Instant Web Publishing access to file" are still grayed out. To test a theory, I closed a database on the web server, then opened it again with FP. These options are no longer grayed out, so apparently, you can't change this section if the file is opened / published on the FM Server.