Paul Welsh
asked on
Exchange 2003 public folder replication problem
Hi, I am moving exchange 2003, services and mailboxes, from a physical box to a new virtual server on brand new hardware.
So, new virtual server 2003 with updates and relevant smtp, www, iis, nntp services installed - then fresh install of exchange 2003. All going fine - can see new server and existing exchange in ESM - until I try to get public folders to replicate. When I choose 'Folders' and try connect to the old server - no problem - I can see the list of public folders. Have gone into properties of each - added the new server as the additional store to replicate to -gone through each folder (there's not that many ) - but nothing is happening - I have left it for some hours. When I click on Folders -and try to connect to the new server - I get an error -could not locate root folder - ensure the default virtual server is running and configured correctly.
Errors in the event viewer like Error -2147221233 reading property 0x67480014 on object type tbtOwningFolders from database "First Storage Group\Public Folder Store (DELIVERANCE)".
domain\admin was unable to log on as domain\admin to the Public Folder Store "First Storage Group\Public Folder Store (servername)".
Any assistance welcome thanks
So, new virtual server 2003 with updates and relevant smtp, www, iis, nntp services installed - then fresh install of exchange 2003. All going fine - can see new server and existing exchange in ESM - until I try to get public folders to replicate. When I choose 'Folders' and try connect to the old server - no problem - I can see the list of public folders. Have gone into properties of each - added the new server as the additional store to replicate to -gone through each folder (there's not that many ) - but nothing is happening - I have left it for some hours. When I click on Folders -and try to connect to the new server - I get an error -could not locate root folder - ensure the default virtual server is running and configured correctly.
Errors in the event viewer like Error -2147221233 reading property 0x67480014 on object type tbtOwningFolders from database "First Storage Group\Public Folder Store (DELIVERANCE)".
domain\admin was unable to log on as domain\admin to the Public Folder Store "First Storage Group\Public Folder Store (servername)".
Any assistance welcome thanks
ASKER
HI and thanks for your response. I have taken your advice in the past and worked directly from your articles on the subject, so I know that you're the man when it comes to this stuff.
Will wait longer. Out of curiosity, why does it take that long? Is it data size/network speed dependent? In terms of data, I dont think there's that much .....e.g. if I was to do an xcopy of say, 10GB of standard pc/server data, mirroring the tree and data contents to another server or pc, this would take less than 20 mins on our network. I am sure that the public folders data size doesn't come close to that. Just for my learning - what is it that exchange is doing to take potentially days - if there's not that much data?
thanks,
Paul
Will wait longer. Out of curiosity, why does it take that long? Is it data size/network speed dependent? In terms of data, I dont think there's that much .....e.g. if I was to do an xcopy of say, 10GB of standard pc/server data, mirroring the tree and data contents to another server or pc, this would take less than 20 mins on our network. I am sure that the public folders data size doesn't come close to that. Just for my learning - what is it that exchange is doing to take potentially days - if there's not that much data?
thanks,
Paul
ASKER
Probably 30 hours into it now -no sign of the replicated folders on the new server. Possibly still premature -however I checked the event log after trying synchronize hierarchy - and get the following error:
Unexpected replication thread error 0x80040107 on database "First Storage Group\Public Folder Store (DELIVERANCE)".
EcGetSenderGUID
EcGetSenderDN
REPL::EcSeekRmq
EcSeekReplState
EcReplMessageUnpack
EcGetSenderGUID
EcGetSenderDN
EcGetSenderGUID
EcGetSenderDN
EcGetSenderGUID
EcGetSenderDN
FReplRcvAgent
thanks
Unexpected replication thread error 0x80040107 on database "First Storage Group\Public Folder Store (DELIVERANCE)".
EcGetSenderGUID
EcGetSenderDN
REPL::EcSeekRmq
EcSeekReplState
EcReplMessageUnpack
EcGetSenderGUID
EcGetSenderDN
EcGetSenderGUID
EcGetSenderDN
EcGetSenderGUID
EcGetSenderDN
FReplRcvAgent
thanks
ASKER
Hi -still no replication. At a loss as to what to do now. Out of my depth on this one. Can see on the originating servers event logs that its sending requests to the new server and new the server is accepting connections from the old server - I can see that the new server has received an instruction in its event logs to start replication -it seems to have a problem in actually processing the instruction to replicate... but whether this means a re-install - dont know.... - if you dont use public folders much - or at all -can you just move mailboxes or is public folder replication a prerequisite to successful mailbox move - and maybe create new public folders from scratch - rather than replicate the old ones? Just thinking of a possible workaround -as I say, my inexperience showing now...
The reason replication takes so long is that it is VERY conservative. Basically it is the same technology from Exchange 5.5 days, where a 10-base network meant you were rich.
If you were going to a more modern version of Exchange then you could do away with public folders. Unfortunately to remove the old server you have to replicate public folders off the server.
The primary reason for replication failing is a smart host configured on the SMTP virtual server. If you need to use a smart host then configure it on an SMTP Connector, removing it from the SMTP virtual server.
Simon.
If you were going to a more modern version of Exchange then you could do away with public folders. Unfortunately to remove the old server you have to replicate public folders off the server.
The primary reason for replication failing is a smart host configured on the SMTP virtual server. If you need to use a smart host then configure it on an SMTP Connector, removing it from the SMTP virtual server.
Simon.
ASKER
Hi - Just checked the smtp virtual server on both original and new machines - protocols -smtp -default virtual server -properties - delivery - advanced - smart host box is blank on both machines in ESM - - -in SMTP connector properties -general tab - there is a smarthost of smtp.btconnect.com and the new server was added there in the local bridgehead box... -does the name of the smtp connector matter? its just that its name in brackets refers to an old server that is no longer around - although its been like that for the past 5 years and mail has been flowing without problems....so I just have global, internal, owasrcratchpad, internet and store events as the 5 public folders - been there since saturday morning....
ASKER
Hi - Still no movement -so I am looking at permissions to see if they could be holding the process up as when I tried to open the public folders from Folder -Connect to -I saw an error in the event viewer Could not log on as user (domain admin) to the public folder store. So, I started comparing permissions in the old server which is working ok, to the new one where replication is not happening - -and the permissions are different - and the domain admin one which has full control on the old server - has 'send as' and receive as - denied on the new server.... would that have any bearing on things? - -= or should I look at the following:
Is it possible to change the location of the Public Folder dbase location -and remount the dbase - dont know if this would have any effect - -or
2. Look at re-installing. I need to make some movement one way or another... thanks
Is it possible to change the location of the Public Folder dbase location -and remount the dbase - dont know if this would have any effect - -or
2. Look at re-installing. I need to make some movement one way or another... thanks
The SMTP Connector doesn't matter, although if it has the name of an old server is it probably an updated Internet Mail Connector from Exchange 5.5 days. Recreating it shouldn't matter.
Domain Admins have Send As and other permissions denied by default, so that is to be expected. The main thing to worry about is that permission inheritance is enabled.
Moving the database is unlikely to have any effect, but you can do that if you like. Use ESM to move it.
If you look in message tracking, do you see any of the replication traffic? It is easy to spot - it will be something like SERVERNAME-IS as the sender.
Simon.
Domain Admins have Send As and other permissions denied by default, so that is to be expected. The main thing to worry about is that permission inheritance is enabled.
Moving the database is unlikely to have any effect, but you can do that if you like. Use ESM to move it.
If you look in message tracking, do you see any of the replication traffic? It is easy to spot - it will be something like SERVERNAME-IS as the sender.
Simon.
ASKER
Looking at an old question in EE -there is a commonality between this guys problem and the one I am having. In that when I go to "folders" and choose "connect to" and select New Server I get Could not locate root folder - and in Tools -Monitoring and status -my new server is unreachable. I can ping and name resolve the other servers on the network - new server is member only - not a DC. Very similar symptoms....it appears to have been resolved by a login convention change...Also I installed Exchange as a domain administrator - is that good enough?
https://www.experts-exchange.com/questions/21569110/Exchange-2003-Public-Folder-Could-not-locate-the-root-folder.html
https://www.experts-exchange.com/questions/21569110/Exchange-2003-Public-Folder-Could-not-locate-the-root-folder.html
ASKER
Hi -as I am not getting anywhere with this, I am considering options - i.e. removing the new exchange installation. Just for my clarification how do I go about doing this -is it Add/Remove programmes? I am also considering exmerging all mailboxes from exchange to PST files then uninstalling the old exchange -so that there are no exchange servers - then - re-installing a new one and importing pst files - -would that work? thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is not a solution to my problem. I am starting a new workaround.
You haven't waited long enough. It can take DAYS. I don't usually get worried for 48 hours.
The hierarchy has to go across first. You can force individual folders to replicate, but as you have to do that on each folder individually, that gets tiresome.
Simon.