Article ID: 841091 - Last Review: October 25, 2007 - Revision: 1.4 Characters that are not supported for object names in ExchangeOn This PageINTRODUCTIONThis article describes characters that you cannot use in object names in Microsoft Exchange Server 5.5, Exchange 2000 Server, and Exchange Server 2003. You may have to create names for components or objects in Exchange, import objects, or connect to objects. This article contains a list of characters that these object names might contain but that are not supported in Exchange. If you try to connect to objects or work with objects, and the names of those objects contain characters that are not supported, you may receive error messages or unexpected results. MORE INFORMATIONMicrosoft Exchange Server 5.5The following table lists characters that Exchange Server 5.5 does not support in component names or object names.Collapse this table
Microsoft Exchange 2000 ServerThe following table lists characters that Exchange 2000 Server does not support in component or object names.Collapse this table
Microsoft Exchange Server 2003Collapse this table
REFERENCES
For additional information about unsupported characters in Exchange Server 5.5, click the following article numbers to view the articles in the Microsoft Knowledge Base:
259282
(http://support.microsoft.com/kb/259282/
)
How to remove accounts with invalid characters
193842
(http://support.microsoft.com/kb/193842/
)
DXA does not handle MAC mail addresses in excess of 10 characters properly
244413
(http://support.microsoft.com/kb/244413/
)
Cannot reply to e-mail from MEMO because originator address is MEMOGWY(SNADS)
For additional information about unsupported characters in Exchange 2000 Server, click the following article numbers to view the articles in the Microsoft Knowledge Base:
329607
(http://support.microsoft.com/kb/329607/
)
You can join an Exchange 5.5 site that has an invalid character in its name to an Exchange 2000 organization
289671
(http://support.microsoft.com/kb/289671/
)
Invalid character error occurs when you upgrade or join an Exchange Server 5.5 site
316061
(http://support.microsoft.com/kb/316061/
)
The SMTP connector returns an error message when invalid characters are used
251951
(http://support.microsoft.com/kb/251951/
)
Exchange System Manager does not verify smart host DNS names
266311
(http://support.microsoft.com/kb/266311/
)
Workflow common script file must be saved as Unicode
311117
(http://support.microsoft.com/kb/311117/
)
"Recipient names cannot have quotes" error message occurs if you use Web Scheduler
884110
(http://support.microsoft.com/kb/884110/
)
Mail flow stops working after you create a new recipient policy or after you configure a connector in Exchange 2000 and in Exchange 2003
822588
(http://support.microsoft.com/kb/822588/
)
You receive a "The object is no longer available" message when you expand Public Folders in Exchange System Manager in Exchange 2000 or in Exchange 2003
836563
(http://support.microsoft.com/kb/836563/
)
You receive a non-delivery report after you send an e-mail message to an Exchange 5.5 recipient
291266
(http://support.microsoft.com/kb/291266/
)
Cannot create ADC Connection Agreement if there is a dot in the Exchange Server 5.5 computer name
For additional information about unsupported characters in Exchange Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
821757
(http://support.microsoft.com/kb/821757/
)
An event sink that is registered against a mailbox does not work in Exchange Server 2003
| Article Translations
|
Back to the top
