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

how i can fix "MMC could not creat the snap-in" at my new instaled exchange 2003 server.

i am going to upgrade exchange 2000 server software/hardware. i insttalled a new 2003 domain and exchange server in existing win2000 invirment as additional domain controller. but now i have a error in System Manager "MMC could not creat the snap-in"
0
japparfan
Asked:
japparfan
  • 6
  • 5
  • 4
  • +3
2 Solutions
 
SembeeCommented:
If that happens every time you try and start the Exchange management tools I would declare it a bad build and look to remove Exchange, remove the domain functionality and wipe the machine. Exchange should work straight out of the box and if it doesn't then there is no point trying to get it to work - just wipe it. The additional few hours to rebuild it could be saved down the line when the server starts to show signs of playing up.

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.
0
 
Robert Sutton JrSenior Network ManagerCommented:
I would try this:
gpmc.msi

If you already have it great.... If not  you can find it here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=4C84F80B-908D-4B5D-8AA8-27B962566D9F&displaylang=en

There was a similiar post about this previously and can be viewed here:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22637625.html

Let me know how it works for you....
0
 
japparfanAuthor Commented:
when i was instlling the exchange 2003 it gave me this error"Exchange detacted the C:\WINDOWS\STYSTEM32\MAPI32.DLL is not the correct version requied to run Exchange System Manager or Exchange Server 2003. This may cause failures in Exchange System Manager, affect availability if your server, or both.
0
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
SembeeCommented:
No idea what the post above regarding gpmc is on about, as that is group policy, has nothing to do with Exchange.

Have you got Outlook installed on this machine as well? If you have then that is not supported. You need to remove Outlook first.
If you got an error during the Exchange installation then you need to reinstall Exchange. Who knows what else has gone wrong behind the scenes.

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.
0
 
Robert Sutton JrSenior Network ManagerCommented:
Sembee this is why I listed that:

Author quote:
"i insttalled a new 2003 domain and exchange server in existing win2000 invirment as additional domain controller"
0
 
SembeeCommented:
So why does the Group Policy management console have anything to do with the fact that System Manager will not open?

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.
0
 
Robert Sutton JrSenior Network ManagerCommented:
In a few other Q'ns previously addressed along with issues out on Tech net it seems to conflict when adding a 2003 DC to an already established 2k domain environment.
0
 
japparfanAuthor Commented:
Outlook express installed by default on this machine.  I have no idea how i can remove it, because it was install with OS automatically.
0
 
ChiefITCommented:
For all on this post:

There seems to be closely related problem, still open. Can the provider of the solution provide input for additional credit?

Thanks

http://www.experts-exchange.com/Software/System_Utilities/Diagnostics/Q_22858778.html
0
 
Robert Sutton JrSenior Network ManagerCommented:
FTR Sembee, Im not disagreeing with the Uninstall/reinstall if it works and resolves your problem, but that always doesnt clear your issue.....
0
 
SembeeCommented:
Outlook Express is NOT Outlook. OE doesn't use MAPI so wouldn't generate the warning.
Is/was there anything else on the machine? Something else has installed a MAPI interface.

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.
0
 
japparfanAuthor Commented:
on this mashine there are
1-.NET 1.1,
2-Microsoft Exchange,
3-Microsoft Exchange Troubelshooting Assistant,
4-2k3 SP2
only installed.
0
 
SembeeCommented:
Considering the error and the other problems I would be looking to wipe the machine after removing Exchange the domain roles so that it can be rebuilt.

Simon.

--
Once your question has been answered, please remember to accept an answer and close the question.
0
 
japparfanAuthor Commented:
Its mean there is no solution of this problem. only reinstallation will fix it?
0
 
SembeeCommented:
Exchange didn't install correctly. Therefore this could be only one of many other problems the server has that you don't know about. As i wrote in my original post -  a new installation should not give any problems. Therefore if it does then it should redone as something obviously went wrong.

Simon.

--
Once your question has been answered, please remember to accept an answer and close the question.
0
 
satyatechCommented:
To be honest; even if its an exchange broken install you do not need a server rebuild.  
Can you please help with a couple of questions:
- Do all other MMCs(other than Exchange work)?
- Can you get a processmon log when trying to open Exchange MMCs and post them to some web URL?
0
 
japparfanAuthor Commented:
Dear All, i removed SP 2 from the server and just reinstall the exchange with out removing existing one. This exercise resolves the problem of "MMC could not create the snap-in" and now i can open the ESM. But one problem is there, i am unable to open Active Directory Site and Services" it is showing me this Error "C:\windows\system32\dssite.msc"
Is any body have idea to fix it?
0
 
satyatechCommented:
1. Copy dssite.msc and dsadmin.dll from a working server.
2. Run command: regsvr32 C:\Windows\System32\dsadmin.dll
0
 
llhuffCommented:
The crash occurs because of a file (PSAPI.dll) that is updated in IE7, but also exists in system32. To fix this issue, the older version in exchsrvr\bin can be safely renamed. To do this, use these steps:

1) Stop All Exchange and IIS services by stopping the Exchange System Attendant Service and the IIS Admin Service from the Service Control Manager (services.msc).

2) Rename the PSAPI.DLL in the %programfiles%\exchsrvr\bin directory to PSAPI.DLL.OLD

3) Restart all Exchange and IIS services
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 5
  • 4
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now