I don't usually bother with IIS these days, but it looks like a text file that the code is trying to open, write to and then close again (perhaps an access log, or something) has either been removed or (more likely) had its permissions changed so that PHP is no longer allowed access to it.
For what it is worth, the problem lies at lines 9, 10 and 11 of your info.php file. Find out what the file is that the code is trying to manipulate and see if a) it's present, and b) what its permissions are. On a wider issue, I'd see if there was any way to stop IIS from spittting out such sensitive data next time Microsoft "fix" it for you ;). It should be possible to change the level of error reporting to prevent information about your machine'sdirectory structure being chocked up any time something like this goes wrong. Ask your developer to alter the error_reporting setting to 'None' or zero (
http://uk.php.net/manual/en/ref.erro...func.constants).
Maybe someone with more recent experience with IIS can be of more help...
By the way, nice websirte: shame about the server!
Dan