John,
Are you able to actually publish with the guest account? If so then
the permissions ended up getting wide open.
One of the most common problems faced when upgrading the extensions
is they basically ask the NTFS subsystem to go and check permissions.
Unfortunately, one little error in the permissions can end up being
propegated and really messing things up throughout the virtual server. This
isn't exactly FrontPage's fault, errors creep into the file structure all
the time as every million or so bits that are written one will get flipped
accidentally, just the nature of magnetic media and it's just asking the OS
to check and make sure things are tidy. One wrong bit at the wrong level
though and everything gets topsy turvey. What I usually do when this happens
is to turn off the site, go into Windows Explorer and select the security
for the root directory of the virtual server (like inetpub\wwwroot for the
default virtual server). I then remove all the permissions except for the
Everyone Group having Full Access. I then turn the site on (after limiting
it so only my IP can access the site until I'm done) and then use FrontPage
to restrict the permissoins correctly by adding my account as admin, then
removing the everyone group from having access (after doing this you may
have to toggle the everyone can browse site option as it might get turned
off when the everyone group is removed). Then, if the permissions are
correctly set, I open the site back up. Of course, another way to do this is
to create a new virtual server instance on the server and just copy the site
to it, check if it works, and then just point the server to use the new
virtual server as your site instead of the old one.
Don't foget though, before you do anything to the site make a backup
just in case there's more to this issue than meets the eye. It's also easy
to accidentally remove enough permissions that you can't access the site
anymore so a backup is definitely handy.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
