Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Hiya mate, that's excellent now we know where the schema master is, what need need to do now is follow this article on the working domain controller: http://support.microsoft.com/kb/318698
This hopefully will sort out the replication issues in the domain.
This may sound stupid, but what is the ADSI edit and where do I start it? I think this headache is getting to me. I am of course the only once here again tonight and have been busy with the regular daily 'problems'...lol.
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Hiya mate, from the Windows 2000 CD-ROM there is a folder called support - in the support folder you will find another folder called support tools - install these on your DC, ADSI edit is part of these tools.
Alternatively jump onto google and search for "ADSI Edit Windows 2000 Download" - there you can pick up the tool no problem.
I am going offline now mate (honest - I am really tired), but am happy to pick this up tomorrow, I really think that we are almost there - maybe, if there is a problem we can try a different approach then.
I think A's gone for a wee while. He'll be back I guess :) ADSIEDIT is like regedit for active directory. You'll find it in the Windows Server support tools. You can grab them from here sir:-
I managed to get the forest prep to run. Now however, I have no idea how to validate the install and any level of sucess. I have run the 'best practices' scanner and got a bunch of erros.
I think the forestprep was a big step though. What can I do now to validate the install and start configuring the whole thing?
I just need to set up one test/example account and once I verify that it is working I can proceed to build my entire 'account map' into reality...:)
Actually, poking further into the best practices anayliser I think the errors are all related to exchange 2007 not being able to be used ever...so I might not have any problems...<shrug> I just need to figure out where to begin validating the actual install and go from there.
Yeah...apparently it was the BDC crapola...:) Once I removed those entries in the ADSI it was all good.
I am ready whenever to start verifiing and testing the software.
Bare in mind I use sendmail on linux at my house (I run a web/mail server there for personal and business use) so I might be a little stupid with all of the technical babble that is required with Exchange...Sendmail is pretty much point click and working..:)
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Cool, so on your member server you now have a spanky new Exchange installation?
What would you like to do? if you would like from here I can point you in the direction of technical articles that you can run through (so that it aids with learning) - rather than just spout jargon at you, don't worry I am not running away (I and the forum will be here) just thought that you would like to have a run at things yourself.
If you have some things that you would like to get covered post them.
In terms of verifying the setup - how does the application event log look on the server, and also are the Exchange services which start automatically all started (you can see them in the services manager and they are typically entitled "Microsoft Exchange yaaada"
Articles are perfect. So point away at any that you suggest.
My situation right now stands that I have a specified domain name to use for all of our e-mail. It is currently hosted offsite. I need as little disruption in e-mail flow as possible. I need to verify that the exchange server will send/receive e-mail without issue. I can either use that domain and just have them change the IP address to point here and pray it works as quick as possible...:) I am sure there will be some level of propegation delay...not an issue. However, if I can get it up and running and verify that it is working either by IP address (this has a static internal private IP of course) or is I use one of the extra unused domains that we own for testing purposes and then just edit in the required domain name and then have them make the switch.
As far as on the exchange software itself...I have never messed with it so I am going to be learning a lot of its conrtol from scratch. I have the big M$ book on managing it, but of course that book is huge and I have only really read the parts on preparing/planning and have not got far into anything as far as creating a user/account for e-mail usage.
I am also more of a hands on and do it person...reading and them trying is not my strong suit...once I do it I of course can duplicate the process infinately...:) The friend I have that helps with my home system walked me through all the steps of setting it up and creating accounts and that was all I needed.
I love it when they drop big projects in front of me and tell me to 'figure it out'...lol...I guess being the 'new guy' is the reason for that...:-D
So...where to start. I need to make sure that the exchange box is being seen through the outside IP address and is known on the network with its static internal IP address so things will route properly.
The application event logs are UGLY at best...here are just a few of the errors that I have found in them.
quote:
Unable to prepare message table for polling thread processing on virtual machine INTWEB. The error number is 0x80040115. Make sure Microsoft Exchange Store is running. Initialization of external interface NNTP failed; Error ecVersionMismatch-MAPI_E_VERSION. Initialization of external interface IMAP4 failed; Error ecVersionMismatch-MAPI_E_VERSION. Initialization of external interface POP3 failed; Error ecVersionMismatch-MAPI_E_VERSION. Initialization of the IMAP4 external interface failed with error 0x80040110. Initialization of the POP3 external interface failed with error 0x80040110. Unexpected error <<0xc1050000 - The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000>> occurred.
The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000
Unexpected error <<0xc1050000 - Network problems are preventing connection to the Microsoft Exchange Server computer. An unexpected, unknown error has occurred. Microsoft Exchange Server Information Store ID no: 80040115-0514-000006bf>> occurred. Initialization of external interface WIN32 failed; Error ecServerOOM. Initialization of external interface NNTP failed; Error ecVersionMismatch-MAPI_E_VERSION. Initialization of external interface OLEDB failed; Error ecVersionMismatch-MAPI_E_VERSION.
Microsoft Exchange OLEDB was unable to initialize because of differing versions of store and exoledb dll. Process INETINFO.EXE (PID=4292). Topology Discovery failed, error 0x80040a02.
Now one annoying thing is that each of those errors brings up the link and sends the information and is SUPPOSED to link to some level of help on the M$ site...they all lead to pages that no longer exist...
Of course I am sure we figure one or two out and other will start to disapear...:)
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Installation >> RE: Installation issue. 
RE: Installation issue. - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
