Announcement

Collapse
No announcement yet.

Replacing an Exchange 2003 Server with updated hardware

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Replacing an Exchange 2003 Server with updated hardware

    Hi all,

    I'm new here. I have a question, and it seems so simple yet the solution is eluding me...

    I have recently purchased an updated server to replace our old Exchange box. They are both running Exchange Server 2003. The old box runs W2K server, the new on W2K3 server.

    I have Exchange 2003 installed on the new box. Both servers apper in the ESM. I can move users mailboxes between the servers at will. Where I'm having issues at is with Public Folders. I have run pfmigrate and received what I believe to be the desired results, however, the migration does not seem to be taking place. When I check the Public Folder store on the new server, the Folders are not there.

    If I try to 'Send Contents' the operation completes, but it appears nothing has been done. When I check the Replication and Status, for the server 'Folders' is connected to, it reports the item as 'In Sync', but the other server reports 'Local Modified'. If I try to sync the other servers file, I get an c1041722 error. It dos this regardlessof the server the 'Public Folders' is connected to.

    Any ideas of where to look?

    Thanks, Brian

  • #2
    Re: Replacing an Exchange 2003 Server with updated hardware

    I imagine you are familiar with with this info..
    http://support.microsoft.com/kb/822895
    and
    http://www.msexchange.org/tutorials/PFMIGRATE.html

    What is the text that goes along with your error code?
    Regards,
    Jeremy

    Network Consultant/Engineer
    Baltimore - Washington area and beyond
    www.gma-cpa.com

    Comment


    • #3
      Re: Replacing an Exchange 2003 Server with updated hardware

      Yeah... used pfmigrate.

      Here's log files from pfmigrate:

      Microsoft Exchange Public Folder Migration Tool

      Mon Oct 16 22:14:37 EDT 2006

      Source Server: FCWBMAIL Version 6.5 (Build 7226.6: Service Pack 1)
      Target Server: MAILBOX Version 6.5 (Build 6944.4)
      WMI Server: FCWBMAIL

      Report Mode in progress.

      Analysis of 11 folders with replica on 'FCWBMAIL' completed.

      0 folders without replica on 'MAILBOX'.
      11 folders with replicas on both servers.


      Mon Oct 16 22:14:43 EDT 2006


      The error text is as follows:

      The Microsoft Exchange Information Store service could not fid the specified object.
      ID no: c1041722
      Exchange System Manager
      And, yes, I did actually run pfmigrate in normal mode also.

      I've searched for the code and the text and it seems to refer to issues with Exchange Server 2000 and permission settings.


      Thanks,

      Brian
      Last edited by random_rodder; 17th October 2006, 03:25.

      Comment


      • #4
        Re: Replacing an Exchange 2003 Server with updated hardware

        Here's a google search using the error code

        http://www.google.co.uk/search?sourc...:en&q=c1041722

        And a search on Petri

        http://forums.petri.com/showthread.p...light=c1041722

        Comment


        • #5
          Re: Replacing an Exchange 2003 Server with updated hardware

          The problem with this is these links (and many others just like them) discuss the Store not mounting in ESM. My Stores mount fine on both servers. This error only occurs when I try to force serverA to sync with serverB, within ESM from serverA.

          None of the public folders replicated from server A to B appear in the public folders on server B, and vice versa. Expanding Publics Folders and selecting a replicated folder in ESM, the replication shows up in the status and replication tabs, but, the replication status on the replication tab shows 'Local Modified' for the sever that is not connected. On the status tab, if I right click the folder on the other server and select Syncronize Content, I get that message I quoted above.

          Comment


          • #6
            Re: Replacing an Exchange 2003 Server with updated hardware

            Read
            http://www.microsoft.com/technet/pro....mspx?mfr=true
            Then
            http://www.microsoft.com/technet/pro....mspx?mfr=true
            Regards,
            Jeremy

            Network Consultant/Engineer
            Baltimore - Washington area and beyond
            www.gma-cpa.com

            Comment


            • #7
              Re: Replacing an Exchange 2003 Server with updated hardware

              Have done both already.

              Guess maybe I ought to ask an obvious question, that I think I know the answer to. Once replication is set up and completed, should the public folders that are supposed to be replicas show in the Public Folders on both server? To me, since they are replica's, that should be yes. And the people whose accounts get moved to the new server should have access to the info on that store. At that point, then the public folders could be re-homed to the new server.

              Another quesion, would it be easier to just restore the public store from a good backup to the new server instead of fighting with this?
              Last edited by random_rodder; 18th October 2006, 00:27.

              Comment


              • #8
                Re: Replacing an Exchange 2003 Server with updated hardware

                Originally posted by random_rodder
                Have done both already.
                So you reset the permissions to the default? Well why didn't you say so? (btw - what is both? The first one was meant to be just info.)

                Guess maybe I ought to ask an obvious question, that I think I know the answer to. Once replication is set up and completed, should the public folders that are supposed to be replicas show in the Public Folders on both server? To me, since they are replica's, that should be yes. And the people whose accounts get moved to the new server should have access to the info on that store.
                Makes sense to me.

                Another quesion, would it be easier to just restore the public store from a good backup to the new server instead of fighting with this?
                Maybe someone more knowledgeable than me should answer this but it seems that you still might have issues even if you do a restore.
                Regards,
                Jeremy

                Network Consultant/Engineer
                Baltimore - Washington area and beyond
                www.gma-cpa.com

                Comment


                • #9
                  Re: Replacing an Exchange 2003 Server with updated hardware

                  Originally posted by JeremyW
                  So you reset the permissions to the default? Well why didn't you say so? (btw - what is both? The first one was meant to be just info.)
                  Both = checked/reset permissions and checked the propagation settings

                  Originally posted by JeremyW
                  Makes sense to me.
                  Just because it makes sense to us doesn't mean it makes sense in M$ world...

                  Originally posted by JeremyW
                  Maybe someone more knowledgeable than me should answer this but it seems that you still might have issues even if you do a restore.
                  If I were going to keep both servers active, I could see that being an issue. I just want to retire a 6 year old server (thing has more grey hair than I do)...

                  Comment


                  • #10
                    Re: Replacing an Exchange 2003 Server with updated hardware

                    Is this still an issue?
                    The public folder replication status cannot be relied upon. I always use the item count.
                    Furthermore, message tracking is invaluable in diagnosing if things are working as it shows if the messages are reaching the server and what Exchange is doing with them.

                    pfmigrate isn't the magic tool everyone thinks it is. It is just a script to populate the replication tab rather than having to set it manually.

                    Finally - I have seen AV software get in the way of replication, so you may want to check that isn't causing a problem like quarantining the replication traffic.

                    Simon.
                    --
                    Simon Butler
                    Exchange MVP

                    Blog: http://blog.sembee.co.uk/
                    More Exchange Content: http://exchange.sembee.info/
                    Exchange Resources List: http://exbpa.com/
                    In the UK? Hire me: http://www.sembee.co.uk/

                    Sembee is a registered trademark, used here with permission.

                    Comment

                    Working...
                    X