[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 450
  • Last Modified:

Exchange 2003 Mail Wizard Error 8004100e



I have a AD server running Windows server 2003 > 3 mths old which is running DHCP,WINS,DNS,IAS and a brand new Exchange 2003 installation on a windows 2000 server sp 3, When i try to run the Internet Mail Wizard in exchange system manager it errors with a "8004100e" error and then says "cannot run set up because server is part of a load balancing cluster". All well and good except the server isnt part of a load balancing cluster !! i dont even have a cluster installed and i never have !. This question has been asked before and i have tryed the fix given but to no avail (was to chage the heurustics value in ADSIEdit on the properties of my exchange server but this only made the exchange server dissapear from the Mail Wizard. Also ifi highlight the servers folder in exchage manage my server type is "clustered" which is a load of poppycock cus it aint!.
I am slowly running out of ideas and hair! I need to have exchange up and running and connecting to my ISP by next tues so a pronto fix would be appreciated !! 250 points to whoever figures this one out and its a good un

  • 2
1 Solution
Is the server on which you are trying to run the IM Wizard dual homed?

garyraifeAuthor Commented:
what do you mean by dual homed ?
garyraifeAuthor Commented:
I have fixed this myself.

0x8004100e means WBEM_E_INVALID_NAMESPACE. I suspect you
need to recreate
the WMI namespace for MicrosoftNLB. Easiest way to do this
is the following

1) Command Prompt
2) cd \WINNT\System32\WBEM
3) MOFCOMP wlbsprov.mof

This will compile and reload the namespace back into the
WBEM repository.

Acording to a Jeff Crawford on microsoft news groups and it works thanks Jeff

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now