exchanga 2000 public folder error

Point value changed by question poster.

Did you recently upgrade to Exchange 2000 from 5.5 or did you move your Exchange server from machine to another. Either of them could have caused the problem. You could try resetting your Public Folders. Try using the information given in these MS KB articles. Hope this helps you out

1). "http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q275171"

2). "http://support.microsoft.com/default.aspx?scid=kb;en-us;Q284200"

Enter your Event ID here:
http://www.eventid.net/search.asp

We have installed the server several times beacuse
it had hardware problem .so i know that the problem is some left overs from previos installanion.
i need to know is there a way to debug the server
or scan active directory for errors ?
I also know that 0x8004010f means mapi_not found.
its looking for somthig that isnt there .

It does look like the 2 Technet articles posted by Jayanth were what you need.
They document using ADSIEDIT, which can update Active Directory information, as well as Exchange 2000 schema settings.
Just reading through your post and what the 2 articles list, they do sound like the fix for what you need.
Since you have reinstalled the Exchange server a few times, you obviously have some bad data in the schema. Running ADSIEDIT as per the 2 Technet articles should help you reset the Exchangesettings to point to the correct current Exchange server with the proper domain name, distinguished name, etc.

This issue can occur if the user's legacyExchangeDN attribute's delimiters in Active Directory are either stored in all uppercase letters or have partial uppercase letters. Examples of the delimiters in the legacyExchangeDN attribute appearing in uppercase are as follows:

All Uppercase Delimiters:

/O=ORG NAME/OU=SITE NAME/CN=RECIPIENTS/CN=AD USERS/CN=USERS/CN=USER NAME

Partial Uppercase Delimiters:

/O=ORG NAME/OU=SITE NAME/CN=RECIPIENTS/cn=AD USERS/cn=USERS/cn=USER NAME

To resolve this issue, use one of the following methods:

Contact Microsoft Product Support Services to obtain the Fbfix.zip file. This file contains the files that are necessary to resolve this issue programmatically. For additional information, see the Readme.txt file located in Fbfix.zip.

Use the Adsiedit tool that is included with the Microsoft Windows 2000 Support tools to change the legacyExchangeDN attribute.

WARNING: Using Adsiedit incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Adsiedit can be solved. Use Adsiedit at your own risk.

To use Adsiedit to change the legacyExchangeDN attribute:

ClickStart, point to Programs, point to Windows 2000 Support Tools, and then click ADSI Edit.

In ADSI Edit, locate the mailbox of the user who is experiencing this issue (the mailbox should be located under the domain tree), right-click the mailbox, and then click Properties.

Click the Attributes tab, and then click either Optional or Both to view the properties of the attribute.

In the Select a property to view list, click the legacyExchangeDN attribute.

Copy the entire entry in theValue box into the Edit Attribute box.

(continued..)

Do you run Exchange 2000 in a cluster environment?

If so, you may need this update:

http://support.microsoft.com/default.aspx?scid=kb;KO;q254360

(REMOVE SPACES from the pasted URL.)

Maxwell

could provide more information:
Like does this happen at a set interval or is when a users tries to make a change to a calander?
Also what service Pack are you running of the server?
And which clients, I had a similar problem with outlook 2000 clients, before the upgrade to Outlook XP.

If you already found the answer could you post it here for other.
David Ruschinek

The serevr runing win2k servuce pack 2 and exchange 2000 service pack 2.

Hi,
i am working over 6 month on migration from 5.5 to e2k, and struggeld with many bugs and errors. The reason for most Problems i found in the ADC, which i used to sync my 5.5 Dir and AD. My first question to is: Do you run a mixed environment ofExchange ? Have you any E5.5 in the Org you must keep up ? Is your W2k Domain in mixed mode too ?
I ask this for the following reason:
As you know E5.5 uses Distributionlist in two ways, first as a Distributionlist and second as a security Group. This behavior is in E2k complete diffrent, you have your Universal Distribution Groups and your Universial Security Groups. So whats up with the ADC ?
When you replicate a Publicfolder (like FreeBusy) the Distribution List from E5.5 is translated in an Universal Distribution List on the AD. At the first access on this Public Folder W2k trys to change the Universal Distribution List into an Universal Security Group. But this only works if your Domain is native! In mixed mode Domain you got somepretty errors on the Client side, and pretty Errors like yours in the Eventlogs of your E2k.

It might be that i am wrong, but i could bet thats your problem.

regards

Frobo

have you checked that there are correct permissions set against the folders and that they are in the 'replicas' bit to rreplicate to other sites?

This question was closed by the author