在.ics日历文件中包含LOCATION字段将停止MacOS El Capitan上的Calendar与Exchange Server通信 [英] Including a LOCATION field in an .ics calendar file stops Calendar on MacOS El Capitan communicating with Exchange Server

查看:140
本文介绍了在.ics日历文件中包含LOCATION字段将停止MacOS El Capitan上的Calendar与Exchange Server通信的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这个问题与我之前问过的一个问题有关( http://severinghaus.org/projects/icv/进行验证.这些事件将导入到单独的日历中,而不是默认的Exchange日历中,并按预期方式显示在日历中.但是,导入事件后,日历无法将事件同步到Exchange Server.如果我尝试添加受邀者,这一点尤其明显.立即,我收到一条错误消息,提示:

This question relates to a question I asked previously (Importing .ics into Calendar on Mac (El Capitan) breaks connection to Exchange Server). I have written a Python script to generate an .ics file that can be used to transfer calendar events into an Exchange calendar in the Calendar app on MacOSX (El Capitan). The .ics file produced validates using http://severinghaus.org/projects/icv/. The events are imported into a separate calendar rather than into the default Exchange calendar and appear in Calendar as expected. However, after importing the events, Calendar is unable to sync the events to Exchange Server. This is particularly noticeable if I try to add an invitee; immediately, I get an error message saying that:

Calendar can’t save the event "event name" to the Exchange server.
There was an error attempting to send your changes to the exchange server.

经过大量的摸索之后,似乎在.ics文件中包含LOCATION字段会停止Calendar与Exchange Server的通信.

After lots of faffing around, it seems that including a LOCATION field in the .ics file stops Calendar communicating with Exchange Server.

因此,例如,以下.ics文件会将事件导入日历"应用中的Exchange日历(可能称为"tempcal")中,但该事件未与Exchange服务器同步,因此我无法添加受邀者:

So, for example, the following .ics file will import an event into an Exchange calendar (perhaps called 'tempcal') in the Calendar app but the event isn't synced with the Exchange server and I can't then add an invitee:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Python iCalendar timetable//
BEGIN:VEVENT
SUMMARY:COURSE XYZ 2016-17 LECTURE 1
DTSTART;TZID=Europe/London;VALUE=DATE-TIME:20161011T160000
DTEND;TZID=Europe/London;VALUE=DATE-TIME:20161011T170000
DTSTAMP;VALUE=DATE-TIME:20160923T021716Z
UID:20161011160000/Introduction to my course@example.com
LOCATION:TBA
END:VEVENT
END:VCALENDAR

...而以下.ics文件可以正常运行:

...whereas the following .ics file works fine:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Python iCalendar timetable//
BEGIN:VEVENT
SUMMARY:COURSE XYZ 2016-17 LECTURE 1
DTSTART;TZID=Europe/London;VALUE=DATE-TIME:20161011T160000
DTEND;TZID=Europe/London;VALUE=DATE-TIME:20161011T170000
DTSTAMP;VALUE=DATE-TIME:20160923T021716Z
UID:20161011160000/Introduction to my course@example.com
END:VEVENT
END:VCALENDAR

从我站着的地方看来,这简直是疯了.任何人都可以对发生的事情进行解释吗?也许更重要的是,我可以做些什么来解决此问题(例如在Mac上),还是需要获得IT支持来解决在Exchange Server的问题(如果可以,他们应该怎么做)? ?)

This seems like utter madness from where I'm standing. Can anyone offer an explanation of what's going on? Perhaps more importantly, is there anything I can do to sort this out at my end (i.e. on the Mac) or do I need to get IT Support to sort is out at the Exchange Server end (and, if so, what should they do?)

推荐答案

不确定是否有帮助,但是位于 http://icalendar.org/validator.html 抱怨TZID值无效.需要在VTIMEZONE部分中定义欧洲/伦敦"时区.

Not sure if this will help, but the validator at http://icalendar.org/validator.html complains about an invalid TZID value. The "Europe/London" timezone needs to be defined in a VTIMEZONE section.

要验证的另一件事是,每行的末尾都有一个CR LF,这是icalendar标准的要求.

The other thing to verify is at the end of every line has a CR LF, which is a requirement for the icalendar standard.

这篇关于在.ics日历文件中包含LOCATION字段将停止MacOS El Capitan上的Calendar与Exchange Server通信的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆