Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have setup incoming Email on my first WEF and it looks like it is working OK and I don't see any error messages. However, I have added a second WEF and I see error messages in Event Logs on the second WEF about incoming email. A critical error occurred while processing the incoming e-mail drop folder . The error was: Value cannot be null.

I am guessing it has got to do with the drop folder. The drop folder on the first WEF which the SMTP Service is running is poiting to the C drive. Is it because the second WEF doesn't have access to that foler? if so, what is the best way to set it up?


share|improve this question
Can you give some more information about your setup? Specifically, the central admin incoming email settings, and where the MX record is pointing (at your load balancer or at the first WFE server). – MattB Aug 4 '09 at 19:25

Actually all you need to do is create a drop folder on your 2nd front end on the C drive - whatever path it is looking for. I've seen this before - and it's remedied by just creating a drop folder where it says it needs to be. Don't try to share the drop folder from WFE #1 - they operate independently - and #2 just needs to be set up like #1.

share|improve this answer
One of the key points to MOSS WFEs is that all paths must be the same and exist on all WFEs otherwise you'll see errors or things may not work as expected. As noted, you won't use the drop folder on WFE2, but it needs to exist otherwise MOSS will complain. – shufler Aug 21 '09 at 20:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.