SusanBradleyGeek while it's disappointing that updates for Exchange and potentially other products have this quirk, that's not what I'm really bothered by. It's a known issue, so why isn't there a reference to how to resolve it if the problem is experienced? I'm not trying to suggest the post should include in-depth resolutions to the potential issue(s), but rather, a brief note such as EXPTA suggests, resetting the virtual directory (assuming that works) or a link to another post concerning recovering from that issue should it have occurred.
I'm not looking to troubleshoot this here, so if Jeff's solution doesn't work, I'll be posting to other forums tomorrow. Just frustrated that a known issue exists and Microsoft, while acknowledging it's a known issue, posts absolutely no information about recovering from it if it occurs.