Synchronization....

[Cary W. Shultz]

Good afternoon!

I am an AD/Exchange guy so Office apps (outside of Outlook) are kinda
foreign to me.

Anyway, have a client who stores .mdb file (Access 2003 and Access 2007) on
a network share. Multiple people access all day long. Recently retired a
server that was - among other things - the File Server.

Now, when users open up MS Access and go to Tools | Replication |
Synchronize Now they are presented with the arrow down box that shows them
all of the .mdb files. Here is my question:

A bunch of the files that show are point to the server that was recently
retired. How do I make those go away? Meaning, not show up in that drop
down.

Second question: There are a bunch of other files - rightly pointing to the
new file server - that do not need to be there anymore (apparently have not
been used in years). How do I make those go away?

Thanks,

Cary

 

[David W. Fenton]

Anyway, have a client who stores .mdb file (Access 2003 and Access
2007) on a network share. Multiple people access all day long.
Recently retired a server that was - among other things - the File
Server.

Now, when users open up MS Access and go to Tools | Replication |
Synchronize Now they are presented with the arrow down box that
shows them all of the .mdb files. Here is my question:

A bunch of the files that show are point to the server that was
recently retired. How do I make those go away? Meaning, not show
up in that drop down.

Second question: There are a bunch of other files - rightly
pointing to the new file server - that do not need to be there
anymore (apparently have not been used in years). How do I make
those go away?

Someone didn't do their job when the new server was put in place.
The old replicas should have been transferred to the new server via
the Jet internal MoveReplica command (available only in Replication
Manager or via the TSI Synchronizer -- it is not exposed by DAO or
JRO).

Since that horse is out of the barn, you have to remove these dead
replicas from the list of replicas. There is only one way to do
this, and that is to attempt a synch with the original location but
without the replica being there. That means you need a PC with the
same name as the old server and a share and subfolder structure that
matches the old one. It would go like this:

1. set up the PC with the appropriate name, e.g., \\OldServer

2. set up a share that matches the old share,
e.g., \\OldServer\Databases

3. in that folder, create appropriate subfolders where the replicas
were located, e.g., \\OldServer\Databases\Projects\MyProject

4. from the new server, attempt to synch one of the replicas with
the replica located at \\OldServer\Databases\Projects\MyProject --
you'll get an error message that it wasn't found and has been
deleted from the replica set.

You may have to do #4 more than once, particularly if the
MSysReplicas table includes more than one replica at that location
(many different ReplicaIDs could have been assigned to the same
file/path name on a particular machine).

After cleaning up, you should probably put together some
documentation for them that explains why they need to be more
careful with their replicas. You might find my Replication Wiki
helpful:

http://dfenton.com/DFA/Replication/

 

[Cary Shultz]

David,

Okay, you busted me! I am that someone.

Now, in my defense, the server did crash and burn.......but that is simply a
convenient excuse. I would not have known to do what you so nicely put into
this answer. I will take a look at your wiki..

Thanks,

Cary