Forum Discussion
TechMerc
8 years agoLevel 4
I've seen this issue recently, and I've seen it happen for a small variety of reasons. In our case, it was because we had an entry in the Host Name of the Default Web Site bindings.
To check that, go to IIS and select the Default Web Site. Under 'Edit Site', click on 'Bindings...' and verify that the bindings there have blank host names. If there's a host name in any of them, get rid of it and restart IIS.
If that doesn't work, I'd recommend starting a DTrace on w3wp and attempting a search. It's likely that the Event ID listed in your article will crop up, but the following error/exception will be slightly different from that in the article.
Good luck!
Related Content
- 14 years ago
- 12 years ago