2
Domain Shared Calendar - Add to Outlook?
Question asked by Gary P - 1/8/2016 at 5:08 AM
Answered
Just wonder if anyone could clear the following up.

I have created a domain shared resource (a calendar named Holidays) and granted full rights to users and selected automatically map, which attaches it to each user.

I have then tried to attach this shared calendar to outlook it shows as an option, it attaches but I get an error in outlook 2013.


Task 'SharePoint' reported error (0x80004005) : 'An error occurred in this SharePoint List (SmarterMail - Holidays). Try updating the folder again. If the problem continues, contact the SharePoint site administrator.  HTTP 500.
The server returned the following error message: Server was unable to process request. ---> User does not exist.'
 
 I have read that domain resources cannot be added to outlook , but the interface allows users to do this. So not sure if this is possible and a bug or a bug in the user interface ?
 
Any thoughts or advice would be appreciated.

4 Replies

Reply to Thread
0
Gary P Replied
Anyone got any thoughts or comments ?
0
Employee Replied
Employee Post Marked As Answer
Hello Gary,
 
I apologize for the delay in a response on this thread; I only came across it today. The ability to share a domain calendar via Add to Outlook is not currently available, so I'm unsure why you're able to connect to it in the Add to Outlook modal. This may be a bug in that version of SmarterMail... What version are you running?
 
Though this is not currently available, it has been requested in the past, and I do agree that it would be a valuable addition. There is another thread available in the Community with greater traction as a Proposed Idea. In an effort to facilitate tracking on this request, please share your agreement and any additional feedback on this thread: http://portal.smartertools.com/community/a803/feature-request-domain-shared-calendars-published-to-outlook.aspx
 
Thank you,
1
Gary P Replied
Hi Andrea
 
I cannot repeat this in the current version we are using 15.2.15.2.6039, so given the age of the post this would appear to have been a bug in the version we would have been using at that time.
 
Gary
0
Employee Replied
Employee Post
Thank you for the follow up on that, Gary. I appreciate it.

Reply to Thread