Orphaned smtp alias's on Public Folders


We have just installed a single Exchange Server 2000 (Windows 2000 Server SP2) on our network.  All the basic functionality including internal & external mail is work fine.  We created some public folders and gave the smtp alias such as help@ourcomapny.com.  These tested okay.  While testing we decided to delete these folders in System Manger and recreate them almost immediately.

However the smtp alias is now help2@ourcompany.com.  If we try and edit the smtp address back to help@ourcompany.com we get an error indicating the object already exists error c10312e7.

I have search technet for this error and found article Q280765 this explains how to find the rogue objects.  Using the instructions I can search and prove there are several variation of my address eg

help 2432323    help@ourcompany.com
help 5646473    help2@ourcompany.com
help            help3@ourcompany.com

You can't delete these from the search results, I have hunted high and low throughout Active Directory and System Manager, Search the registry but can't find any referance.

I then applied Exchange 2000 SP1 (forgot to do it earlier).  I have also ran ISINTEG with the -fix option.

None of the above has fixed my issue, If any one has come across this problem and fixed it I would appriciate the solution.

Thanks In Advance

Rob Langley
Who is Participating?
MoondancerConnect With a Mentor Commented:
200 points refunded, item moved to PAQ at zero points and closed.
Moondancer - EE Moderator
Would you like a refund for this, since no one has added information here?

Community Support Moderator @ Experts Exchange
Asta CuCommented:
This is a very old question, but helping you in Browsers so thought I'd add some help here as well.


To set up Microsoft Exchange with Internet Mail Service on a new Windows 2000–based server, follow the same rules as the upgrade. However, for a new server, you must consider the basic Windows 2000 configuration issues.

Verify that DNS is configured properly. For more information, see the Windows 2000 Online Documentation on the Microsoft Windows&2000 site.
When installing Exchange, be sure to use proper security credentials and account memberships.
If installing on a Windows 2000 domain controller, be sure that the SMTP service is removed or disabled.
Install Exchange SP3 or later.
Configure Exchange and Internet Mail Service.
Internet Mail Service (IMS)
Windows 2000 provides a native SMTP service. Installing the SMTP service on a computer running Windows 2000 Server and Exchange and using Internet Mail Connector causes the connector to fail to start, which disrupts Internet mail delivery.

Exchange cannot use the Windows 2000 SMTP service to send or receive Internet mail, so you must remove the Windows 2000 SMTP service in order to allow the Exchange IMS to start.

To remove the SMTP service:

In Control Panel, click Add/Remove Programs.
Click Add/Remove Windows Components.
Select the Internet Information Services (IIS) check box, and then click Details.
Clear the SMTP Service check box, and then click OK.
You can use the Windows 2000 SMTP service as a transport choice for inter-site replication among Windows 2000 domain controllers. You can also use it for general SMTP mail functionality. Disabling this service does not affect the ability of Windows 2000 to use SMTP protocols for inter-site replication or general SMTP mail functionality. The Exchange IMS makes the service available directly to any application including Windows 2000 Active Directory replications.
Much more on the link above....
Microsoft Exchange 2000 Server Service Pack 2
Release Notes

Good luck,

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

langlro1Author Commented:
Thanks for the reply.  Unfortantly I can't verfy any of the above as we did a manual fix for the customer and it is unlikely I will need to do this again

Thanks Again

After corruption in the Public and Private Information stores on an SBS2000 Exchange Server, the folders were renamed then recreated, with accounts where possible being exmerged. The public database had the folders copied in manually as should be done. However upon restarting the services etc., it was found that the e-mail addresses associated with the Public folders had been appended by a 2 or 3. With some accounts being given spurious numbering e.g. info became info2178654.

Trying to change the E-mail addresses associated with the Public folders back to the correct ones i.e. info2@domain.com back to info@domain.com resulted in the error message c10312e7 user already exists… etc.

A check of the ADUC in the Administration Console revealed nothing, however checking in Settings->Control Panel->Administrative Tools->ADUC revealed the blighters in all their glory.

The problem’s resolution was thus; by essentially doing a Public folder recreation once again plus removing references to folders in ADUC :

1. Export Public folders from Outlook to PST file
2. Stop SMTP Service
3. Stop IIS Service
4. Rename pub.edb and pub.stm
5. Open Settings->Control Panel->Adiministrative Tools->Active Directory Users and Computers
6. Select Microsoft Exchange System Objects
7. Delete problem items including copies (e.g. info; info2; info2134965; etc.)
8. Restart Information Store Service
9. Remount Public Folder in Administration Console->Exchange, etc.
10. Open Outlook and open PST created in step 1 as local folder
11. Copy folders back into Public folder from locally opened PST one at a time.
12. Make sure IIS running, if not start.
13. Restart SMTP Service.
14. Test.
15. Drink beer and make merry. J

If you have problems locating which Object is grabbing the address in ADUC (hopefully it should be obvious) check Microsoft Article q280765.
Asta CuCommented:
This is a very  old, closed question, I believe you intended to comment in another question vs. this.
":0) Asta
No I placed it here on purpose. It's the question that closest related to the problem I had. Upon searching through other various answers I couldn't find a satisfactory answer to the problem, so after developing a solution that worked for me I placed it here so should anybody else be struggling they'd have a good chance of coming across it. :-)
Asta CuCommented:
Thank you for expounding, thomasbback.  That is terrific!
":0)  Asta
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.