After you install Exchange 2007 service pack 3, and or rollup #1 or rollup #2 and you attempt to create a new receive connector, you receive the following error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
test
Failed
Error:
Active Directory operation failed on SBS01.ks.local. This error is not retriable. Additional information: The parameter is incorrect.
Active directory response: 00000057: LdapErr: DSID-0C090C26, comment: Error in attribute conversion operation, data 0, v1772
The requested attribute does not exist.
Exchange Management Shell command attempted:
new-ReceiveConnector -Name ‘test’ -Usage ‘Custom’ -Bindings ‘0.0.0.0:25’ -Fqdn ‘test.test.com’ -RemoteIPRanges ‘0.0.0.0-255.255.255.255’ -Server ‘SBS01’
Elapsed Time: 00:00:00
This is caused by service pack #3 not extending the schema properly, or not at all. To resolve this issue, download service pack 3 again at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en and then extract it.
Open a command prompt and go to the extracted folder. Now execute the following command:
Setup.com /PrepareSchema
Now attempt to create your receive connector, and it will work fine. Please note, you do NOT have to remove rollup #1 or rollup #2 to fix this issue. I found one post that mentioned waiting for rollup #2 to come out to fix the issue http://msmvps.com/blogs/bradley/archive/2010/10/12/can-t-do-a-new-receive-connector-after-exchange-2007-sp3-rollup-1.aspx , but the issue is not fixed in the rollup as it is a schema extension that was introduced in service pack #3. Upon further reading and investigation, on the Microsoft TechNet site, at http://technet.microsoft.com/en-us/library/ff607233(EXCHG.80).aspx it clearly states
“You must prepare Active Directory and each domain before you perform the first installation of Exchange 2007 SP3 in an organization. This process includes updating the Active Directory schema for Exchange 2007 SP3”
Guess no one read this part, including me!
Thanks for this, I have just got an orphaned SBS 2008 system I inherited updated with SP3 (and the zillion other things that needed to be done) and I could not create a new Client Connector as I have done on other systems – this fixed things.
Hey Lyle, thank you so much for this information. I obviously missed that part of technet. I would have thought that when the Windows Update installed this it would have done it for you. Keep up the great blog, you have lots of good articles.
Great post – This has been bugging me for weeks – i didnt link this issue with WSUS not automatically installing SP3 rollup (had to do it manually due to installation failures – and that didnt even extend the schema!!)..now i finally got a new send-connector created without a single error and my internal servers are happily being relayed 🙂
ChuckD, in Microsoft’s defense “If you run the Exchange Server 2007 Setup wizard with an account that has the permissions required to prepare Active Directory and the domain, the wizard will automatically prepare Active Directory and the domain. ”
when in doubt, use enterprise admins
“no warranty implied or given, in fact please ignore anything i say”
David- In our case the same account was used during the Windows Update and the manual install of SP3 to update schema. Problem is the Windows Update doesn’t add the command line option to update the schema so it never occurs unless you do it manually. Maybe it should be removed from WSUS. Not sure, but my article works if WSUS did the update and it is not working.
Windows update doesn’t push down Service pack 3. That’s a manual install. But SBS is using a secondary admin account.
Thank you so much for this information !!!!!!!!!!!!!!!!!
Thank you Lyle! This did the trick.
This blog showed in a search on the symptom higher than any MS item. I stopped searching, so I don’t even know if there is an MS item on it out there.
Hello,
I am also facing the same problem, but my server is not the first server in the Exchange organisation, and this error is not faced on the first server in the exchange organisation.
is this “setup.com /prepareschema” command needs to be run on every exchange 2007 server in the organisation or only on the first exchange server
Umesh
is there a way to check if the prepareschema is done while exchange 2007 SP3?
if the receive connectors are created before SP3 and then SP3 is installed, will those receive connectors work?
Yes, if the were created before they will still work. I’m not sure on how you would check to see if the schema was applied but you can reapply without issue.
It only needs to be run on one of the Exchange servers with an account that has permissions to write to the Schema. Once this is done, it is not needed to do the same thing on other servers as the schema is extended at that point.
Thanks for the reply, one more query, does this apply to only SBS or all other versions as well?
Umesh
It applies to any Exchange 2007 Server that didn’t get the Schema Update. From what I have been seeing people from both SBS and non SBS are experiencing it if they didn’t follow the Technet article 100%. At least it is easy to fix!