A scheduled collaboration configuration synchronization job has failed for collaboration with name 'null',

401
1
11-02-2018 02:28 PM
JYI
by
Occasional Contributor

Hi, 

I am trying to collaborate two 10.6.1 Portals, one on Azure and one on AWS.

The collaboration is initiated on the Azure Portal. AWS Portal can only Send Content to the Portal on Azure. 

On AWS Portal:

On Azure Portal:

The wild card certificates on the two Portal are the same.

The error message: "A scheduled collaboration configuration synchronization job has failed for collaboration with name 'null'" is in both Portal Log.

Can anybody explain what is wrong here?

0 Kudos
1 Reply
JYI
by
Occasional Contributor

Final Solution:

The reason why the collaboration failed is that inside a Portal VM, the other Portal url is not accessible. The two Portal urls have to be recognized inside Portal VMs. In our case, Portal and Web Adaptor are on the same VM.

0 Kudos