Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

The property value is invalid. The value can't contain leading or trailing whitespace error when installing Exchange 2010 in Exchange 2003 enviroment.

Posted on 2011-05-05
8
Medium Priority
?
3,639 Views
Last Modified: 2012-05-11
OK, I'm going crazy with this.   I receive the following error when installing Exchange 2010:
The property value is invalid. The value can't contain leading or trailing whitespace

I looked up the error and have found the offending DN name, but I am unable to change it with ADSIEDIT.   I have looked through Exchange Manager 2003 at the recipient policies and cannot find a place to change it there.

Any advise would be appreciated.
0
Comment
Question by:rikklea
  • 4
  • 3
8 Comments
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35704278
What DN has the problem? Is it a user object? Make sure the user has a valid UPN as that can cause this error too (blank right hand side of UPN)
0
 

Author Comment

by:rikklea
ID: 35708900
Sekarc4u:

I read that article, the problem is the resolution applies to EMC for 2007/2010  We have the EMC for 2003 and the recipient policy does not allow for changes to the DN which has a backslash "\" after the name (email domain).
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35730543
Why don't you just install the Exchange 2010 management tools and then try and change the offending object from there?
0
 

Author Comment

by:rikklea
ID: 35739672
MegaNuk3:

Unable to install the EMC, still get the same error.
0
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35740288
Can you post a screenshot of ADSIEdit on the distinguishd name of the object?

Why don't you just delete it from ESM? removing a recipient/email address policy won't remove email addresses in E2k3
0
 

Author Comment

by:rikklea
ID: 35740718
Thank you everyone for the help.    

The solution was to use ADSIEDIT on an older server and remove the character.   Although it gave me a permissions violation, it did make the change.
0
 
LVL 31

Accepted Solution

by:
MegaNuk3 earned 1000 total points
ID: 35741953
Well done. Thanks for the update. Feel free to close this question.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses
Course of the Month20 days, 16 hours left to enroll

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question