I unable to install exchange server 2007 on server 2008 enterprise with DC is 32 bit Server 2003 enterprise error orgainzation prepartion failed error code 8207 please help .

Hi,I not realy understand your environment. Your DC is a 32 bit machine, or you'd like to install Exchange 2007 on a 32 bit machine.If you'd like to start the organization preparation on a 32 bit machine, you need the 32 bit install package:http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=44c66ad6-f185-4a1d-a9ab-473c1188954cRegards,Zoltnhttp://www.clamagent.org - Free Antivirus for Exchange http://www.it-pro.hu http://emaildetektiv.hu

i have 2 server HP DL 360 g3 (32bit machine) OS server 2003 (32bit OS)with R2 Sp2 ---Role DCi install exchnage 2007 sp1 on HP DL 380 G5(64bit machine) OS server 2008(64bit os)with sp1--- and i got this errorError:An error occurred when executing 'ldifde.exe' to import schema file 'D:\Setup\ServerRoles\Common\Setup\Data\PostExchange2000_schema84.ldf'. Error code: 8207. More details can be found in the error file 'C:\Users\administrator\AppData\Local\Temp\2\ldif.err'.Please help

Are you using an account which has Schema and Enterprise admin permission as well local admin on 2008 machine? You can use Exchange 2007 SP1 32 bit edition to run /Prepare* commands directly on DC to prepare your AD. How to Prepare Active Directory and Domains http://technet.microsoft.com/en-us/library/bb125224.aspxAmit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Yes i am login with Enterprise Administrator but still same result .then i update schema on ad via 32 bit package the result is ok but i found another error Hub Transport RoleFailed Error:An error occurred. The error code was 2147950650. The message was The server is not operational..----------------------------------------------------------------------------------------------------------------------------------but is there any issue to update schema via 32 bit package does you have any refernce of microsoft about this

Do you mean that while running /Prepare* command on 32bit DC, you got Hub Transport Role? Then I don't understand why it is checking for Hub Transport role while just preparing Schema, AD and Domain... A Closer Look at Preparing Active Directory for Exchange 2007 (Part 1) http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/closer-look-preparing-active-directory-exchange-2007-part1.html If you say Schema is prepared on 32 bit and then while running setup on 64bit machine to install Exchange you got error on Hub transport server then I guess something is blocking the access between Exchange and DC... Do you have SNP disabled on Windows 2003 DC? Check below article to disable RSS too... You cannot host TCP connections when Receive Side Scaling is enabled in Windows Server 2003 with Service Pack 2 http://support.microsoft.com/kb/927695Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

When i check schema version it is 4197 is it correct ?I installed exchange with sp1.

Suggest you to check below article for schema version checking methods... How to find the current Schema Version http://support.microsoft.com/kb/556086/en-us?spid=3198 Also run ExBPA and see if you get any error and correct if something comes up in it...Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

i already check how can i fix this schema versionis 4197.

i already check how can i fix this schema versionis 4197. Rerunning setup /prepareschema of Exchange 2007 SP1 should fix it.Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

now every thing is fine but still got the same error Hub Transport RoleFailed Error:An error occurred. The error code was 2147950650. The message was The server is not operational.ialso patched as you told me http://support.microsoft.com/kb/927695

~ How about SNP disable? You can install patch for it on Windows 2003 SP2... http://support.microsoft.com/kb/948496 ~ Also verify the DNS settings of Windows 2008 server in all Local Area Connection and make sure that it is pointing to correct internal DNS server. After following above two things restart both servers and try to install Exchange 2007 SP1 on Windows 2008 server. ~ If you still face problem then run ExBPA and correct the errors as per guidance available in it and correct the issues.Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Thanks Amit I installed Exchnage on other machine its worked -------------------------------------------------------------------------------------------------------------------------- <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> The version of setup.exe that comes with the Exchange Server 2007 installation media will run only on computers with a 64-bit operating system. In many environments, existing domain controllers will be running the 32-bit version of Windows Server 2003. This means that you can not run the setup.exe commands necessary to prepare the domain off the Exchange Server 2007 installation media, as it has been compiled for an alternate processor architecture. One way to deal with this problem is to obtain the 32-bit evaluation version of Exchange Server 2007 from Microsofts Web site. You can use the 32-bit evaluation edition to prepare the forest and domains prior to installing the full 64-bit edition of Exchange Server 2007. You can obtain the 32-bit evaluation software by navigating to http://www.microsoft.com/technet/prodtechnol/eval/exchange/default.mspx and providing registration details. It is also possible to obtain the 64-bit Exchange Server 2007 evaluation from this location -------------------------------------------------------------------------------------------------------------------------- Refrence MIcrosoft training KIt 70-236

I ended up doing three things to get past this problem. The first was to turn off IP6 completely. Look for how to edit the registry to disable IP6. The second is to make sure that each AD server points to itself first for DNS resolution. My backup AD box pointed to the primary and that doesn't work for the Exchange Install. The third was to change the say that DNS suffixes were added for the network connection. I had to have the three part name, corp.example.com. I think because it found it for example.com, but the full name didn't match so Exchange would go no further. I know this won't help the problems that started this thread, but if anyone else is late to the game like me, it will help.