8513 MSExchangeFBPublish error with multiple servers 0x80044501

I just added in new larger exchange server recently.  This is being done to add additional space for the message stores.  All users will be migrated to this server once I'm completed.  

I didn't install this server but after it was brought online I started to see 8513 errors in the event log with the 0x80044501.  I found this MS article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;296151

I also found several other people with similar issues on here, but with a small difference.

I followed the MS article 296151 and found that the key did not exist in the registry.  So I went to the other server and exported the key then changed the individual parameters so that it was pointing to the new server then imported the reg file/key into the new server.  I tried to restart the services and still received the 8513 error.  I continued down the file to step 12 where I got stuck.  Someone else on here was asking the same thing on where this is located.  They were pointed to change the password on the account that controls the service.  I went in and looked at the services and it was set to a local service not an account so there is no way to reset the password unless I specify an account.  

First question:
Do I need a free/busy on each server or does this run on only one server?  

Second question:
Is there another way around this?  If not then I will need to create an account but the big question is what rights should that account be given?  I know by default domain admins are restricted in exchange for a few things on the service side...
sej69Asked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
To remove the first Exchange server you need to follow this article: http://support.microsoft.com/default.aspx?kbid=307917

For traffic detection, I suggested in an earlier post to enable message tracking. With that enabled every message that passes through the system is logged. You can then track the message to see what is happening with it. You do need to have message tracking enabled on both servers to be able to track it fully. Replication traffic is very easy to spot when you see it.

Simon.
0
 
SembeeCommented:
You should have free/busy information on every Exchange server where there are mailboxes, and this information should replicate to the other servers. There are a few other system folders that I always replicate, the OAB folders for example.

The article that you have posted is for Exchange 2000, whereas you haven't posted the version of Exchange. It may not even apply to you.

Is the server fully patched? Service packs etc?
Is replication happening correctly?

Simon.
0
 
sej69Author Commented:
Oops.  I'm running exchange 2000.  Yes, the server is fully patched including the most recent Exchange service pack. (just freshly downloaded from MS)

Replication?  I'm not sure what you mean...?   How do I verify this?
0
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.

 
SembeeCommented:
With Exchange 2000 there is not only the service pack, but the hotfix roll up as well. You need to ensure that has been applied as well.

If you have introduced a second server you need to replicate some public and system folders from the original server to the other servers.

This is the article that we point people to when they are removing the first Exchange server. Even if you aren't removing the server it explains how to setup replication of certain folders. I would replicate the system folders that are outlined in this article. http://support.microsoft.com/default.aspx?kbid=307917

Simon.
0
 
sej69Author Commented:
Oh, I thought there was a way to see if replication is working.  I do have these replicas set on both servers.  Actually they were created when the server was installed but I verified that just to be sure.

I just talked to the person that installed the server and he thinks that he didn't install the hotfix rollup.  I'll go looking for that now and try it out.

One thing I've noticed after working on this issue for a bit is that after applying the registry fix the error is no longer scrolling every 40 minutes or so.  The error only shows now when exchange is restarted.

Anyway, I'll go looking for the hotfix rollup and get that on.  Do you have any other suggestions?
0
 
SembeeCommented:
If the replicas are set, then that is good. What you need to look at is whether the content is replicating? Are the items counts shown for the folders in ESM the same on both servers?

Simon.
0
 
sej69Author Commented:
Woa. Surprised.  No, none of the folders have actually replicated.  In fact, the folders that were created didn't even show on the new server.  This would make some sense in some of the reading I've done.  Something is hanging up the replication process.  Password/Account rights...?  The issue is that the account that Exchange is started under on the 2nd(new) mail server is the local system account and not a domain account.  Should I set this to a domain account that has rights to the message stores?

I also applied the rollup patch and that doesn't seem to have fixed the issue.
0
 
SembeeCommented:
You should NOT change the account the services run under. That is a hang over from Exchange 5.5 and isn't required. Leave the account settings alone.

If both servers are Exchange 2000, then you will have to wait for replication. It is very slow. Measured in weeks.

If you haven't already, get message tracking enabled on both servers. That will let you track whether the replication traffic is being delivered correctly. I have had antivirus software quarantine replication traffic in the past, so it is important that you keep an eye on the message tracking logs using the Message Tracking Center to ensure that they are delivered.

Simon.
0
 
sej69Author Commented:
Ok, I'm going on 4 weeks with this issue and it still hasn't sync'd up yet...  Any more ideas?
0
 
SembeeCommented:
Do you see any traffic going backwards and forwards?

The other method is to basically sod the replication, remove the old server totally and then email the users asking them to create a new entry in their calendar, leave it half an hour or so and then remove it. That repopulates the Free/Busy information. You do have to remove the other server for this process to work - as you must stop the Outlook clients from being able to connect to it. As they were refer to the live Exchange server, the other one has to go, not just be shutdown (as it will still be in the system if you do that).

Simon.
0
 
sej69Author Commented:
If you are referring to the public folders for the "Traffic" then no, I don't see anything coming over from the other server.  No public folders were created.

When you say remove the old server, I'm not 100% sure on what you mean?
0
 
sej69Author Commented:
Sorry.  I got busy and totally forgot about this.

I'm almost embarrassed to say that all it was that the exchange replication service wasn't started.  I could have sworn that this is something that is turned on by default but I guess not.  Anyway, I turned that on and within a few days everything was syncing just fine.  Thanks for the help but it was much easier than we all had thought.
0
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.