Return to Jive Software

Skip navigation
Up to Discussions in Support
2,994 Views 3 Replies Last post: Jul 8, 2009 11:23 AM by brad.heller RSS
orcusomega Novice
orcusomega
2 posts since
Jul 1, 2009
Currently Being Moderated

Jul 1, 2009 11:21 AM

Jotlet integration, sycn'ing with Outlook calendaring

My organization is using Jive extensively for various partner-facing sites, and we are faced with the issue of being able to maintain an on-line calendar within our spaces.  Clearly, with Jive owning Jotlet, and the integration of the Jotlet plugin, we have the ability to do this fairly easily, but have run into the inability to perform Funambol sync'ing as outlined in the Jotlet integration notes.

 

The specified URL for Jotlet synchronization is https://www.jotlet.net/sync, but this address is experiencing a 302 HTTP Redirect loop - right back to itself.  This was determined by tracing the requests and responses with wget, and here is a snippet of the Funambol log:

 

13:15:09 GMT -5:00 [DEBUG] - Connecting to www.jotlet.net:443
13:15:09 GMT -5:00 [DEBUG] - Requesting resource /sync/
13:15:09 GMT -5:00 [DEBUG] - Sending data of size 3671...
13:16:05 GMT -5:00 [DEBUG] - HttpSendRequest error 12156: The HTTP redirect request failed

 


13:16:05 GMT -5:00 [INFO] - Network error writing data from client: retry 1 time...
13:16:05 GMT -5:00 [DEBUG] - Sending data of size 3671...
13:17:00 GMT -5:00 [DEBUG] - HttpSendRequest error 12156: The HTTP redirect request failed

 


13:17:00 GMT -5:00 [INFO] - Network error writing data from client: retry 2 time...
13:17:00 GMT -5:00 [DEBUG] - Sending data of size 3671...
13:17:46 GMT -5:00 [DEBUG] - HttpSendRequest error 12156: The HTTP redirect request failed

 


13:17:46 GMT -5:00 [INFO] - Network error writing data from client: retry 3 time...
13:17:46 GMT -5:00 [ERROR] - HTTP request error: 3 attempts failed.
13:17:46 GMT -5:00 [DEBUG] - Error occurred in sync: code 3 = HTTP request error: 3 attempts failed.
13:17:46 GMT -5:00 [ERROR] - Error in preparing sync: HTTP request error: 3 attempts failed.

 

This is functionality that would be HUGELY beneficial in coordinating several departments and teams various calendars - if there is anyone who has been able to make this work, I would GREATLY appreciate your feedback!

 

Thanks,


Bob

Tags: bug, outlook, calendar, jotlet, sync
Expert
brad.heller
3,517 posts since
Jun 18, 2009
Currently Being Moderated
Jul 1, 2009 1:44 PM in response to: orcusomega
Re: Jotlet integration, sycn'ing with Outlook calendaring

Hello Bob,

 

Unfortunately we've officially ended support for Funambol integration in Jotlet. How old are these integration notes you're working off of and how old is your Jotlet account? New accounts are apparently blocked from accessing this feature.

 

Cheers,

Brad

orcusomega Novice
orcusomega
2 posts since
Jul 1, 2009
Currently Being Moderated
Jul 1, 2009 1:53 PM in response to: brad.heller
Re: Jotlet integration, sycn'ing with Outlook calendaring

My Jotlet account is maybe 2-3 months old, and the Sync feature is not obvious, but sync password settings are available. While I am not in any way married to Funambol, is there another way for us to sync an outlook calendar (not at the Exchange level - corporate will not allow us to run the application against the servers) with Jotlet or will I need to find another solution to this issue?

 

Additionally, is there a way to show rendered HTML in the calendar entries?  Most notable for hyperlinks to event registration services.

 

Thanks,


Bob

Expert
brad.heller
3,517 posts since
Jun 18, 2009
Currently Being Moderated
Jul 8, 2009 11:23 AM in response to: orcusomega
Re: Jotlet integration, sycn'ing with Outlook calendaring

Hey Bob,

 

Unfortunately not. The only way to "sync" the two is to export a .ics from Jotlet and import it to Outlook.

 

I talked to our product guys and it looks like they're hoping to scope out some good Jotlet features so feedback like this definately helps push that along!

 

Cheers,

Brad

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.