Yea, I've seen this post and we have started the application pools repeatedly everytime this error occurs. However, as soon as we browse the site again it kills the application pool again and deliveres the same HTTP 503 - Service Unavailable. We were convinced that when we first saw this error message that there was a miconfiguration in the permission somewhere but we've rule that out I believe. We've got permissions wide open at this point, in order to debug. We've also gone so far as to narrow the site content itself down to a single default.htm as to be sure there were no .net framework components or application problems in the site causing this problem.
If you share a site configuration, must the recipient server contain all of the exact same content locally on that server? In other words...if my primary server (where I have exported the configuration and establed the sharing relationship) has Exchange's web applications in the default and then a seperate Sharepoint site, etc...must the secondary server (where I am consuming the exported configuration) contain those same products or sites or can those sites be stopped on the secondary server?
Clearly we need more info on Shared Configuration and it's requirements and limitations.
Thx,
Gaylen