Exchange BPA: Unknown Schema Extention version e.a.
Hi, I have downloaded the Exchange Server 2007 with Service Pack 1 Enterprise and Standard Editions (x64) - EXE (English) from MSDN and used this to rund "prepareSchema" and "prepareAD" this all went fine and the Exchange BPA was reporting that my schema was suitabel for exchange 2007. After that I used the same setup to install the CA role on the first server. This all went ok, no error what so ever. Now when i run the Exchang BPA i get the following errors that concern me: Unknown Schema Extention Version: The Exchange schema extensions are from an unknown version. Schema version detected is 11116. Unrecognized Exchange Signature: Active Directory domain 'ASP' has an unrecognized Exchange signature. Current DomainPrep version: 11221 Acording to MS this would be cause by the fact that i used a different setup to do the /prepare and to install the CA. This is not the case however. I also found the following extention versions: CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=<DN-of-forest-root-domain> A rangeUpper value of 4397 indicates that Exchange2000 Server is installed. A rangeUpper value of 6870 indicates that Exchange Server2003 is installed. A rangeUpper value of 10637 indicates that Exchange Server2007 is installed. On http://technet.microsoft.com/en-us/library/bb738144(EXCHG.80).aspxit says that the rangeUpper value for SP1 Should be 11116. Can't find anything on the Exchange signature value for SP1. So this might indicate that its ok since i'm installing SP1 and not the 2007 RTM. Still i don't like errors about my schema etc. Can anyone tell me what this might mean? Is it just exchange BPA that does not cope with SP1 well or did i make a big mistake. Thanks for any replies.
August 22nd, 2008 2:20pm

sorry but: BUMP. Does anyone have any idea?
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2008 2:23am

Hi, I have checked objectversion for Org use ADSIedit.exe, its value is 11221.My lab is Exchange 2007 sp1. Note: The ADSIEdit.exe tool is an MMC snap-in that you can use to edit objects in the Active Directory database. For more information about ADSIEdit.exe, in Help and Support Center for Windows Server2003, click Tools, and then click Install Windows Support Tools Install Windows Support Tools After you finish the installation, all the component have upgraded to sp1,then the alert should disappear. Besides you can use ExBPA to have a Exchange 2007 readiness check to check whether any error will be report there. Exchange 2007 Readiness Check now available in ExBPA http://msexchangeteam.com/archive/2006/07/28/428506.aspx It could not the problem, you may check exchangesetup.log to view detail installation information there. It should locate at c:\ExchangeSetuplogs Hope it helps. Xiu
August 25th, 2008 12:09pm

Hi, Thx for your reply. It gives me some hope that you have the same object version. I should have mentioned that the readiness check does not pose met with any errors. It says that all is well and ready for exchange 2007. Its after in install the first server and perform the health check of the BPA that i get this error. So not with the readiness check but with the healt check (iin which i select the new administrative group and the first server in installed). If you run that in your lab environment does it report anything in this aerea then? Thanks again.
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2008 2:20pm

Hi, In my lab,I did not find any related issue. Nevertheless, I found a thread similar as yours,( http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2596975&SiteID=17 )there you may check your accept domain, whether it has been set properly. Besides, Id like to know whether you have any child domain in your forest, whether you have run setup /preparead there.Please check objectversion in child domain to see whether it is the same as root domain. If it is not the case, then please check c:\ExchangeSetuplogs to see whether any error logged there. Hope it helps. Xiu
August 26th, 2008 9:10am

Thought i'd let you know. Turns out i made a mistake with the PBA. After installing version 2.8 I now installed an update ( http://www.microsoft.com/downloads/details.aspx?familyid=4f2f1339-cbcd-4d26-9174-f30c10d7ec4c&displaylang=en ) and the error is gone. My bad, thx for the response!
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2008 1:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics