Database ACL is completely cleared, left with default manager. Ever seen this?

I’m helping a customer move old Domino 6.5 servers on Win2003 to new servers on Win2008 (still with Domino 6.5 because of licensing). After creating new replicas, many application databases have their ACLs reset to -Default- = Manager and nothing else. Plus, many are missing their database icons. Anyone else see this recently and any solutions?

This was reported previously here http://www-10.lotus.com/ldd/nd6forum.nsf/DateAllThreadedWeb/d86b9c84da5f0f7585256f7f00597b9a?OpenDocument

Subject: Database ACL is completely cleared, left with default manager. Ever seen this?

I suspect this happens when you create a replica stub with default ACL on the new server, and either…a) You do a push replication from a server that does not think it has Manager rights to the database

b) You trigger the actual replication on a client replicator, and the client’s ID file does not have have Manager access to the database.

-rich

Subject: RE: Database ACL is completely cleared, left with default manager. Ever seen this?

@Rich - your “A” scenario is close to what I’m doing, but the source server is in the ACL (via the LocalDomainServers group) as Manager.

This problem occurs after using the Domino Administrator (R6.5), selecting multiple files, right clicking, and selecting New >> Replica. Adminp creates a replica stub on the destination server, and the databases get populated during the next replication between the two servers. Most databases are fine, but some are have a default ACl (with -Default- and the destination server name listed with Manager rights); and some are also missing the database icon; occasionally some are missing the database launch setting.

We’ve been moving several servers in Europe this way, and are doing it using remote access over a slow connection. It may be a bug related to network latency and the replicator not populating a replication stub correctly if the network is not responding fast enough. But since they are using an old, unsupported version of Domino, we can’t ask IBM. Plus, we haven’t found the factors to reproduce the problem consistently. So, I’m just speculating…