• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 780
  • Last Modified:

Exchange Server 2003 replication errors

Since installing an exchange server 2003 front-end server, I have been getting the following error every 5 minutes on my back-end server.

Source: MSExchangeIs Public Store
Category: Replication errors
Event: 3092
Description: Error 1129 occurred while processing a replication event.
                  Folder: (3-7) NON_IPM_SUBTREE\SCHEDULE+FREE BUSY\EX:/o=Glasgow Development
                  Agency/ou=GLAGOWDEVELO01

I have tried stopping public folder replication, but the errors continue.  I have also tried changing the front-end server back to a normal server, but this did not have any affect either.

What should I be looking for?
0
AlanCReid
Asked:
AlanCReid
  • 3
  • 3
1 Solution
 
aa230002Commented:
On your front end server, you shouldnt have any Public Folder store.
Dismount and delete the Public Folder store from your front-end server. Its not supported.
and then, restart your MSExchange Information Store service and things should be fine.

Thanks,
Amit Aggarwal.
0
 
AlanCReidAuthor Commented:
When you say restart the Information Store, do you mean on the front-end or back-end server?

Alan
0
 
aa230002Commented:
Restart the Information Store service on Front-end server only.

Thanks,
Amit Aggarwal.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
AlanCReidAuthor Commented:
I tried what you suggested and am still getting the errors, that is why I asked about which IS to restart.

When you look in System Manager at the Public folders, the SYSTEM CONFIGURATION one still seems to have a reference to the front-end server (although only in the server field, the name and storage group fields are blank).

Thanks
Alan
0
 
aa230002Commented:
You might have to restart the IS service on your back-end server. If you can not do it right now (production hours) do it after office hours and let me know the results.

Thanks,
Amit Aggarwal.
0
 
AlanCReidAuthor Commented:
I was going to restart the back-end server IS tonight, but after half an hour of continuing to generate messages, it has now stopped, so thanks for your great help
0

Featured Post

Industry Leaders: 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!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now