Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 225
  • Last Modified:

User Replicating a Database

I have a a user who uses a local copy of a database on his laptop. It was replicating fine without a problem for quite a while. Now it seems that the database will not send any of the information he enters into the database up to the server copy. I had him verify the option of Send documents in the replication settings and it was checked. Does anyone know:

1) How I could verify the settings he does have on his replication tab for that database?

2) What I should have him look at to try and fix this problem?

3) I had him email me the database in question and it says it is protected by local security so I cant open it even with Full Admin rights.

ANy help would be appreciated.... Putting a 500 point value because need some solutions fast...


Thanks
0
TheBull369
Asked:
TheBull369
  • 2
1 Solution
 
marilyngCommented:
All replication history and errors will be noted in the client's log.nsf, and in the database>> Replication >>History.


While you're in the history, clear it - sometimes that's all it needs.  Also, check the replication times against the server to see if there is a error entry at the same replication time.

To open the database, put it on the server :)  

The server always has permission, what happens with databases created locally is that Notes encrypts them so that some other user just cannot open them.  However, notes usually adds a default administration group to all ACL's, but not necessarily on the client templates, unless you set them to replicate from the server.  IF you make sure all your templates have a default administration group (i.e [Adminstration]), then any new databases created will include the default group.
0
 
TheBull369Author Commented:
It was the Replication history due to a time related problem. The users clock at one point was set for July 7th only on the send side... So cleared history and seemed to work....

Thanks
0
 
marilyngCommented:
Glad it worked.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now