× Welcome to the Centrify Community! We are rolling out product name changes — click here to learn more.

Centrify Cloud Connector error

Showing results for 
Search instead for 
Do you mean 
Reply
Highlighted
Participant III
Posts: 33
Registered: ‎11-07-2013
#1 of 8 2,633
Accepted Solution

Centrify Cloud Connector error

Hello,

 

When I check for status in Centrify Cloud Connector, it says "Failed connecting to cloud..." with the following error:
---------------------------
Centrify
---------------------------
Failed connecting to cloud.
Reason: The security timestamp is invalid because its creation time ('2016-10-31T09:29:44.992Z') is in the future. Current time is '2016-10-31T09:22:06.473Z' and allowed clock skew is '00:05:00'.
---------------------------
OK  
---------------------------

 

When it get resolved on its own randomly after sometime, I get the following error.
---------------------------
Centrify
---------------------------
Failed connecting to cloud.
Reason: The ChannelDispatcher at 'sb://centrifyapac-southeast-asia-11.servicebus.windows.net/Proxies/12269c33-4324-46f4-bc5f-2f1f91968528/f7f99f30-744a-4009-bbfe-2c1be5f5be53/' with contract(s) '"IServiceBusRpc"' is unable to open its IChannelListener.
---------------------------
OK  
---------------------------

 

Can anyone give clues separately on why these errors occur?

 

Regards,
Ganesan

Centrify Advisor I
Posts: 57
Registered: ‎12-12-2012
#2 of 8 2,628

Re: Centrify Cloud Connector error

Hi Ganesan,

 

The time difference between your cloud connector host and our cloud cannot be greater than 5 minutes. Please check the clock of the cloud connector host when the first error occurs. 

 

Do you still see the 2nd error after a cloud connector service restart?

Thanks,
Henry

Participant III
Posts: 33
Registered: ‎11-07-2013
#3 of 8 2,625

Re: Centrify Cloud Connector error

Hi Henry,

 

Yes, the second error comes even after restart of cloud connector. Here is similar error but pointing to different server:

 

---------------------------
Centrify
---------------------------
Failed connecting to cloud.
Reason: The ChannelDispatcher at 'sb://centrifyapac-southeast-asia-07.servicebus.windows.net/Proxies/12269c33-4324-46f4-bc5f-2f1f91968528/f7f99f30-744a-4009-bbfe-2c1be5f5be53/' with contract(s) '"IServiceBusRpc"' is unable to open its IChannelListener.
---------------------------
OK  
---------------------------

 

Regards,

Ganesan

Participant III
Posts: 33
Registered: ‎11-07-2013
#4 of 8 2,601

Re: Centrify Cloud Connector error

Any update on this behavior?

Centrify Advisor I
Posts: 57
Registered: ‎12-12-2012
#5 of 8 2,596

Re: Centrify Cloud Connector error

Hi Ganesan,

 

1. Could you please review this KB article and make sure your firewall is set up accordingly.

 

2. Could you please run the connectionTestGui.exe in this folder on the cloud connector host and see if there is any failure?

C:\Program Files\Centrify\Cloud Management Suite

 

3. Could you please let us know your tenant? 

 

Thank you.


Best Regards,

Henry

Participant III
Posts: 33
Registered: ‎11-07-2013
#6 of 8 2,574

Re: Centrify Cloud Connector error

Hi Henry,

 

1. No link to that KB article.
2. All but "Certificate Check" are success. "Certificate Check" resulted in Warning. If I disable the firewall, it resulted in Success.

 

If I disable the firewall, Cloud Connector also works fine. Please let us know the KB article to ensure it is setup correctly.

 

Regards,
Ganesan

Centrify Advisor I
Posts: 57
Registered: ‎12-12-2012
#7 of 8 2,572

Re: Centrify Cloud Connector error

Hi Ganesan,

 

This is the KB article I have mentioned:

 

https://centrify.force.com/support/Article/KB-4849-Centrify-Cloud-Connector-outbound-connection-summ...

 

Thanks,
Henry

Participant III
Posts: 33
Registered: ‎11-07-2013
#8 of 8 2,538

Re: Centrify Cloud Connector error

Thanks for the reply.

 

Its little cumbersome process in adding "Microsoft Windows Azure Service Bus service" settings in ISA 2006. I will try again. I have disabled and verified that this firewall change solved the problem.