Yes, I did, but did not know the limitation for the naming of the agent. talked with adobe support today, and was told no space is allowed in the agent name. Thanks!
issue resolved. Looks like the replication agent name does not multiple words in the name. Once I changed the agent name from "translate publish" to "translate", it started working. Is that the real reason?
I have a replication agent configured, and connectivity tested fine. But when I tried to publish the pages, the page failed to be populated to the target publish instance.Below are the error messages:19.02.2016 15:16:48.018 *DEBUG* [147.118.248.9 [1455913007990] GET /etc/replication/agents.author/tr...
You are correct. but my question is actually for the flush agent which is defined under "agents.publish", but it showed "No such agent" info when clicked on "View Log". I tried to understand why it gives such message when in fact it is working fine when checking on the publish through the console. s...
Hi, all,I configured a flush agent earlier, all was working fine. When I checked today, the agent on the publish instance is still working fine. but on author instance, when I clicked on /etc/replication --> agents.publish --> flush agent --> view log, I got this error: no such agent: flush agent.Ch...
Hi, Opkar, you are right on money. I replaced the password, and it started working. Nobody should have changed that. I will track down.Thanks for your help, and appreciate all the replies from Amit, Bsloki, Kautuk,
Amit, thanks for the reply.These instances are running on the same VM. No firewall between them. Regarding the credentials, I'm logging as admin. it is the same for all instances. Just don't know where to start to look. Thanks.
Hi, all,Got report from users that the replication from author to publish failed. Did the test of connection with the following errors:~10.02.2016 16:29:54 - Create new HttpClient for Publish1 Agent10.02.2016 16:29:54 - * Auth User: admin10.02.2016 16:29:54 - * HTTP Version: 1.110.02.2016 16:29:54 -...