First of all, I know what the error means. That's not the question. I'm trying to figure out a replication bug-a-boo and stumbled on an anomaly. Here's the snippet of code:
[snip]
Set s=New NotesSession
Set db=s.Currentdatabase
Set view=db.getview("Configuration")
Set ConfigDoc= view.Getfirstdocument
Set CAREDb=s.Getdatabase("Server1/Acme", configdoc.careLocation(0), False)
Call caredb.Replicate("Server2/Acme")
[snip]
This agent is run on schedule on Server1 (in a database other than the care database.)
There's a replica of the care database on both servers, both in the care subfolder under the Domino data directory on their respective servers. Configdoc.careLocation(0) = "care\caredatabase.nsf" but when I look at the log on Server1, when the agent runs, I see:
01/03/2017 02:24:55 PM Pulling D:\IBM\Domino\data\care\caredatabase.nsf from Server2/Acme care\caredatabase.nsf
I don't know if that's the cause of my replication error or not, but I figure any odd behavior is a good behavior to eliminate. So, the question: Where is my agent getting the full path to the database on the remote server and how can I convince it not to use it?
EDIT: The added code:
rc = caredb.Replicate("Server2/Acme")
If rc Then
Print "Replication to " + caredb.Filepath + " successful."
Else
Print "Replication to " + caredb.Filepath + " failed."
End If
The log:
01/06/2017 08:10:56 AM Replicator updated 1 document(s) in Server2/Acme Consumer\ComplaintWorksheet.nsf from D:\IBM\Domino\data\care\caredatabase.nsf 01/06/2017 08:10:56 AM Finished replication with server Server2/Acme
01/06/2017 08:10:56 AM AMgr: Agent ('Update Locked Documents' in 'care\MCDefer.nsf') printing: Replication to care\Careworksheet.nsf successful.