Computer build lists Cisco Comcast FCC Intel Microsoft Network Management Network Neutrality Security Verizon
Written by: Justin James 10/16/2008 9:37 AM
I've been slaving away over a hot Exchange 2007 server on Windows 2008 for a week now. Great product, except for the Outlook Anywhere component, which does not install itself properly. The issues are well documented by everyone except for Microsoft, it seems like. In any event, over the course of my work, I started seeing event ID 4001 in the logs a lot, with a message that said, "A transient failure has occured. The problem may resolve itself in a while. The service will retry in 56 seconds." Another symptom I saw was that OWA (Outlook Web Access) would state that there was a transient failure as well when people tried to access it. The diagnostic information mumbled some stuff about not being able to open a mailbox. This is caused by an inability for the OWA server to communicate properly with the CAS, usually itself. In this case, while following some troubleshooting documents, I had added lines like: 192.168.1.XYZ NETBIOSNAME 192.168.1.XYZ FQDN to my hosts file. Taking those out and running "ipconfig /flushdns" corrected the issue. I did not see any information on the Web about this, so I figured I should post some. J.Ja
I've been slaving away over a hot Exchange 2007 server on Windows 2008 for a week now. Great product, except for the Outlook Anywhere component, which does not install itself properly. The issues are well documented by everyone except for Microsoft, it seems like. In any event, over the course of my work, I started seeing event ID 4001 in the logs a lot, with a message that said, "A transient failure has occured. The problem may resolve itself in a while. The service will retry in 56 seconds."
Another symptom I saw was that OWA (Outlook Web Access) would state that there was a transient failure as well when people tried to access it. The diagnostic information mumbled some stuff about not being able to open a mailbox. This is caused by an inability for the OWA server to communicate properly with the CAS, usually itself. In this case, while following some troubleshooting documents, I had added lines like:
192.168.1.XYZ NETBIOSNAME 192.168.1.XYZ FQDN
to my hosts file. Taking those out and running "ipconfig /flushdns" corrected the issue. I did not see any information on the Web about this, so I figured I should post some.
J.Ja
0 comments so far...
Adrian's PC Doctor blog Deb Shinder's blog Deb Shinder on Vista Dietrich T. Schmit on Linux Erratasec blog - Security Ed Bott on Microsoft Jason Hiner's blog John Carroll Justin James' developer blog Matt Sherman's blog Martin McKeay Paul Mah, Tech at play Richard Bennett's blog Sunbelt Blog - Security Tom Shinder on ISA Tom Shinder on security ZDNet - Zero day Rich Tehrani - VoIP