Oneupweb
asked on
I get an error when I try to check Replication Status I get an message " UnkAnnown Error Has Occurred" ID no: fffffc07
I get this error when I try to look at the Replication Status under the Public Folder Store in ESM.
UnkAnnown Error Has Occurred
ID no: fffffc07
Also, the Offline Address Book is not downloaded to clients in Outlook 2003. I have Exchange Server 2003 with SP2 on a Windows 2003 Server Standard Ed. I have tried the rebuild fix, removed and reinstalled OAB, Ran Reinstall of Exchange, Ran ESEUTIL /d on Public Folder all to no Avail.
I could really use some good advice here. I am lucky enough to be the only one on this Exchange server for the time being. I will be going live with it as soon as this is fixed. Any ideas what I could be missing?
UnkAnnown Error Has Occurred
ID no: fffffc07
Also, the Offline Address Book is not downloaded to clients in Outlook 2003. I have Exchange Server 2003 with SP2 on a Windows 2003 Server Standard Ed. I have tried the rebuild fix, removed and reinstalled OAB, Ran Reinstall of Exchange, Ran ESEUTIL /d on Public Folder all to no Avail.
I could really use some good advice here. I am lucky enough to be the only one on this Exchange server for the time being. I will be going live with it as soon as this is fixed. Any ideas what I could be missing?
ASKER
I cannot reload Windows on this because this is our Catalog Server as well. We are a small organization (30 Users). We are using a Linux based e-mail server for now and are moving it over. I would have to be able to fix this without a reload. It is my understanding that the server will cleanup any offline address books that have been deleted after 7 days. Is there a way to speed this up? Also, I have created a public contact list under the Public Folders. If I want to use this as the Offline Address Book, would I just point it to the Public Foldes when choosing my Offline Address Book? It does not give me an option to choose anything under that.
You cannot use a public folder contact list as an address book. If you want the public folder to be available to users offline, then you must add it to their favourites then enable the option to replicate public folders favourites offline.
As for my advice on reloading the server - you can always reload a server - it doesn't matter what it is doing. A workstation can be used to to hold any roles that the server might require while it is being rebuilt.
You might get away with removing Exchange, flushing out the left over folders then reinstalling Exchange fresh. When you do, make sure that you use THE administrator account rather than one that you think has the correct rights.
You do know that it is not recommended to install Exchange on a domain controller? At 30 users you are starting to get to the point where you would be better off with a separate machine. I will only go up to about 10 to 15 users before I start recommending a separate machine.
Simon.
As for my advice on reloading the server - you can always reload a server - it doesn't matter what it is doing. A workstation can be used to to hold any roles that the server might require while it is being rebuilt.
You might get away with removing Exchange, flushing out the left over folders then reinstalling Exchange fresh. When you do, make sure that you use THE administrator account rather than one that you think has the correct rights.
You do know that it is not recommended to install Exchange on a domain controller? At 30 users you are starting to get to the point where you would be better off with a separate machine. I will only go up to about 10 to 15 users before I start recommending a separate machine.
Simon.
ASKER
What Address Book should the clients be pointing to for an Offline Address Book? It doesn't really matter if they have access to one, but I do want to use cached mode for the clients. I just don't want this Sync error to come up everytime they hit send recieve.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
An Exchange server shouldn't be doing things like that - who knows what else is wrong with it.
I would move your mailbox back to the other Exchange server, remove Exchange and reinstall both it and Windows.
I personally feel the database is knackered - for a database to break with a single mailbox on it is a bad sign.
Simon.