tag:blogger.com,1999:blog-13722520.post112542782903815194..comments2024-01-23T17:05:43.163-08:00Comments on Calendar Swamp: Outlook 2003: For iCal import, use Gregorian instead of Lunar?!Scott Macehttp://www.blogger.com/profile/01831862884367555570noreply@blogger.comBlogger42125tag:blogger.com,1999:blog-13722520.post-66046202676893962802013-10-06T22:11:05.258-07:002013-10-06T22:11:05.258-07:00Don't know if this will work for everyone but ...Don't know if this will work for everyone but I'm trying to import the 2013-14 NFL schedule for my fave team and had this same cryptic error message. After opening the .ics in Notepad and deleting the Version2.0 didn't work I tried copying and pasting to a new Notepad file but that didn't work either, so I reopened the file in Notepad to look for those pesky hidden spaces and discovered that the first line started with "BEGIN:VCALENDAR<br />VERSION:2. 0BEGIN:VEVENT<br />DTSTART:2013" instead of "BEGIN:VCALENDAR<br />VERSION:2.0..." so I deleted the space between the . and the 0, closed and saved, and then imported flawlessly with no further modifications. Hope this helps someone!Sagamore Honeyhttps://www.blogger.com/profile/02980127665889087040noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-28083438369600024542012-01-24T15:43:10.777-08:002012-01-24T15:43:10.777-08:00I am having a similar problem with .ics files goin...I am having a similar problem with .ics files going the other way: importing from one generated in Outlook 2003 into iCal. All the files from on correspondent show up on the iCal 7 hours late on the correct date. But only from certain senders.Piperhttps://www.blogger.com/profile/02656406267841429193noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-45763852609382519122011-08-13T08:52:35.482-07:002011-08-13T08:52:35.482-07:00Thank you granadaCoder, your code worked for me.Thank you granadaCoder, your code worked for me.razvantimhttps://www.blogger.com/profile/12281011052798238533noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-71787347576215214312011-06-22T11:10:28.384-07:002011-06-22T11:10:28.384-07:00June 2011 and this is still an issue with Outlook ...June 2011 and this is still an issue with Outlook 2003. My work around was add it to Google Calendar first and then 1 way sync Google with Outlook. Not pretty but functional. <br /><br />rather crazy that both the ical and Outlook icons in evite create the same .ics file.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-17946742248413259722011-02-13T06:34:51.825-08:002011-02-13T06:34:51.825-08:00How can I get Outlook 2003 to archive my mails on ...How can I get Outlook 2003 to archive my mails on a 30 rolling days basis?Brad Fallonhttp://www.freelinereport.com/noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-23070864369896372902010-11-22T13:43:12.353-08:002010-11-22T13:43:12.353-08:00I posted some additional information here:
http://...I posted some additional information here:<br />http://microformats.org/wiki/icalendar-implementations<br /><br />But basically, I created an .ics file that worked while I was logged in as an XP Admin account.<br />But the exact same file was failing when trying to import to Outlook as an XP-StandardUser.<br /><br />The "lunar" exception seems to be "Anything that could go wrong under the Moon" type of catch-all exception.<br /><br />In case the other url dies some time in the future, here is the icl contents.<br /><br /><b><br />BEGIN:VCALENDAR<br />VERSION:2.0<br />PRODID:www.testMeiCalendar.net<br />METHOD:REQUEST<br />BEGIN:VEVENT<br />DTSTART:20101231T230000<br />DTEND:20110101T010000<br />SUMMARY:New Years Eve Reminder<br />LOCATION:Downtown<br />DESCRIPTION:Let's get together for New Years Eve<br />UID:ABCD1234<br />SEQUENCE:0<br />DTSTAMP:20101125T112600<br />END:VEVENT<br />END:VCALENDAR<br /></b><br /><br />As I said, the above file worked (as is) under an Admin account, but the exact same file would fail under a Standard account with that lunar exception. :<<br /><br />I was wasting alot of time tweaking the contents of the file, and it kept giving the Lunar exception. Then I figured I needed to try something different, which was namely, try a different Windows-Account.<br /><br />The lesson learned is that whether you are Microsoft or you are a "normal" developer, writing good exceptions is a part of the job. <br />Keep them un-ambigious, and provide information back to the caller with some meaningful information, not just a "something blew up" exception.granadaCoderhttps://www.blogger.com/profile/02752822942527478679noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-32343045686411949842010-10-06T13:16:54.335-07:002010-10-06T13:16:54.335-07:00SOLVED - at least for me anyway.
Looking at iCal ...<b>SOLVED</b> - at least for me anyway.<br /><br />Looking at iCal spec it appears a CRLF is required at end of every line so changing my .jsp <br /><br /><b>Before:</b><br /> out.print("BEGIN:VCALENDAR ");<br /><b>After:</b><br /> out.print<b>ln</b>("BEGIN:VCALENDAR ");<br /><br />Notice the <b>"ln"</b>, it appends a CRLF to the output.<br /><br />Viola, no more pesky error message, REJOICE!!!<br /><br /><i>Tested on Outlook 2003 client.</i>Anthony @abrrownoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-87662525735181749762010-09-13T01:21:39.408-07:002010-09-13T01:21:39.408-07:00This worked for me:
Create an event in Outlook, g...This worked for me:<br /><br />Create an event in Outlook, go to 'Actions' -> 'Forward as iCalendar', save the generated .ics file to your hard-drive, and copy that format in your own .ics file.Steven Ellishttps://www.blogger.com/profile/04344770837551828902noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-61126530367346473772010-05-26T06:28:44.651-07:002010-05-26T06:28:44.651-07:00Please see the following post on codeproject artic...Please see the following post on codeproject article - the code given in that project produces an invalid vCalendar/iCalendar file, but the comment lists many good resources for creating a valid working iCalendar file.<br /><br />broken code - do not use as-is - please read the RFC and validate<br />http://www.codeproject.com/KB/cs/sendtaskspgmticly.aspx?msg=3429265<br /><br />Read the RFC at http://tools.ietf.org/html/rfc5545 and use the iCalendar validator tool available at http://icalvalid.cloudapp.net/ to help create proper iCalendar files (read the full codeproject post for more details).<br /><br />In particular notice that the PRODID property has a break (\n) in it where it shouldn't, which produces MIMEDIR starting on a line by itself. This is incorrect, as there is no property named "MIMEDIR," and it should really be a part of the line above it.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-20556675865023246002010-05-18T13:33:30.265-07:002010-05-18T13:33:30.265-07:00HERE'S THE SOLUTION AND WHY...
VTIMEZONE, DTE...HERE'S THE SOLUTION AND WHY...<br /><br />VTIMEZONE, DTEND, etc. Those are not the problem. There's a great deal of Red Herring -chasing going on here and so I felt compelled to share: <br /><br />Open your .ics file with Notepad on Windows (any version of Windows). Be certain your Word Wrap is turned-off under the Format menu. <br /><br />Now, do a File | Save As...<br /><br />Notice the file is in UTF-8 (or perhaps Unicode)? Outlook chokes on this. Save the file with "Encoding: ANSI". <br /><br />Double-click it to open in Outlook and you should see it open without any trouble. <br /><br />Note, however, that any special characters that require UTF-8 encoding will not show correctly (or at all). That requires you to modify those characters to something that fits in the 7-bit ANSI ASCII realm. <br /><br />Reasons: <br />The Word Wrap will cause there to be forced end-of-line characters in the file where you do not want them. This isn't why you get the error, it's just something that can "break" the file. <br /><br />Outlook's handling trouble does not appear to be a simple issue with the Unicode Signature (BOM) that forms the invisible first character of some UTF-8 files; the character that should tell an application to read the file as UTF-8 instead of ASCII. Even with that BOM removed, Outlook doesn't seem to like the UTF-8 at all.<br /><br />Now, in the IETF's RFC 5545 (which describes the iCalendar format) it states... <br /><br />"6. Internationalization Considerations<br /><br />"Applications MUST generate iCalendar streams in the UTF-8 charset and MUST accept an iCalendar stream in the UTF-8 or US-ASCII charset."<br /><br />I hope that helps to know why it doesn't work and how to make it work.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-65485070625223802572010-03-25T09:50:49.688-07:002010-03-25T09:50:49.688-07:00For me, the issue was resolved by replacing the li...For me, the issue was resolved by replacing the line breaks (CR-LF) in DESCRIPTION by "\n"Ajaynoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-3260375470956543662010-02-17T11:12:51.046-08:002010-02-17T11:12:51.046-08:00I've been having trouble getting this to work ...I've been having trouble getting this to work as well and in the end I decided to let Outtlook do the hard work for me.<br /><br />Set up an appointment in outlook similar to those that you are trying to import.<br /><br />Save the file using Save as... and select file type .ics<br /><br />Open the file using your favourite text editor and gradually work through the file deleting lines, saving the file and then double clicking on it until you get the minimum content that will work.<br /><br />I found it necessary to save it in DOS format, not Unix.<br /><br />As a mimiumum I've found the following lines necessary:<br /><br />BEGIN:VCALENDAR<br />PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN<br />(these previous 3 lines are all one line)<br />VERSION:2.0<br />METHOD:PUBLISH<br />DTSTART:20100219T130000<br />DTEND:20100219T150000<br />RRULE:FREQ=WEEKLY;UNTIL=20100531T000000Z;INTERVAL=1;BYDAY=FR;WKST=MO<br />TRANSP:OPAQUE<br />SEQUENCE:0<br />UID: some random hex string<br />DTSTAMP:20100217T080637Z<br />Summary: Whatever\n<br />PRIORITY:5<br />X-MICROSOFT-CDO-IMPORTANCE:1<br />CLAS:PUBLIC<br />END:VEVENT<br />END:VCALENDAR<br /><br />You may be able to delete some more of the lines and it shouldn't take too much effort to work out what the lines do and the formatAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-38127856281035475852009-11-26T00:54:23.370-08:002009-11-26T00:54:23.370-08:00Someone said that they debugged and found a line t...Someone said that they debugged and found a line to add "METHOD:PUBLISH"... Well that is already in the ics file... as my file begins:<br /><br />BEGIN:VCALENDAR<br />PRODID:-//Google Inc//Google Calendar 70.9054//EN<br />CALSCALE:GREGORIAN<br />VERSION:2.0<br />METHOD:PUBLISHRyan Fordhttps://www.blogger.com/profile/11727971770118504729noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-44145928987184393792009-11-26T00:50:45.117-08:002009-11-26T00:50:45.117-08:00exported my ics file from Google and even with rem...exported my ics file from Google and even with removing the "Version 2.0" line, saving and trying to import into Outlook 2003 I continue to receive:<br /><br />This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.<br /><br />To avoid this error, set the appointment option to Gregorian instead of Lunar.<br /><br />More information about this error message online. (link)<br /><br />...and the "link" is as follows:<br /><br />Details <br />Product: Office <br />ID: 10070 <br />Source: OfficeErrorMessages <br />Version: 11.0 <br />Message: Links to additional information about the error message you saw are available below. <br />-----------------------------------<br />Currently there are no Office Assistance articles available for this error message. <br /><br />...well, isn't that just swell! This is rediculous!Ryan Fordhttps://www.blogger.com/profile/11727971770118504729noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-62433781798062508842009-10-19T16:54:27.860-07:002009-10-19T16:54:27.860-07:00Thanks for a solution finally! Removing Version:2...Thanks for a solution finally! Removing Version:2.0 worked for me as well.Marc Vermuthttp://www.twitter.com/mvermutnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-91486896136498300012009-10-01T21:06:44.800-07:002009-10-01T21:06:44.800-07:00hi frnds
the time that the appointments adds in ...hi frnds <br /><br />the time that the appointments adds in outlook is 5 hrs behind....what is the reason..Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-43990642079646451372009-09-11T11:58:19.388-07:002009-09-11T11:58:19.388-07:00I just debugged this and found that adding a singl...I just debugged this and found that adding a single line:<br /><br />METHOD:PUBLISH<br /><br />resolved it in Outlook 2003. After adding that line directly after VERSION:2.0 Outlook allowed me to import the iCalendar file.<br /><br />Looks like another cryptic bug for Microsoft....wish I had a dime for everybody looking for "Gregorian" option.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-5726497601327800532009-08-24T15:52:03.277-07:002009-08-24T15:52:03.277-07:00I think Joe in the previous comment was on the rig...I think Joe in the previous comment was on the right track, at least for me. Here's how I fixed the problem.<br /><br />First, I'm generating these ics files in Perl using the Data::ICal perl module, and emailing them using MIME::Lite, similar to the guy at http://www.mavetju.org/programming/outlook-ics.php. I'm doing this to add a feature to the web-based software I'm working on. (The software sends an email with an iCal attachment.) I tried everything in the comments above, but kept getting the Lunar/Gregorian error message from Outlook when I double-clicked the calendar attachments in the emails that were sent to me from Perl. <br /><br />Looking at the raw data in the .ics files, it looks like Outlook is changing the line terminators from CR-LF to CR-CR-LF. (CR = carriage return, LF = line feed; these are two different ASCII characters.) The iCal spec calls for CR-LF, and the Perl module appears to be doing that correctly; but Outlook is adding an extra CR. Actually, I can't be sure Outlook is doing that in the received email -- it might be an artifact of me saving the attachment to a file, uploading it to my webserver, downloading to my Mac, and running the "od" utility to examine the file. But I suspect it's Outlook doing it when the email is received. <br /><br />Anyway, when I changed the text encoding in MIME::Lite from quoted-printable to base64, Outlook liked the attachments -- no more error. I.e. the encoding technique in the email attachment made the difference.<br /><br />So, my point is, like Joe said, look at the end-of-line characters, and make sure that your file isn't having those changed by whatever process you're using -- in my case, the encoding method for the email attachment.Matt McAdamshttp://www.trackvia.comnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-81842315870415594832009-06-24T12:16:39.164-07:002009-06-24T12:16:39.164-07:00I just found this post and I think I found the pro...I just found this post and I think I found the problem with the outlook. It turns out that if you use any other code for the linefeed in the 'DESCRIPTION' field except ASCII 13. (if you have multiple lines in the description field).<br /><br />Hope this help.<br /><br />JoeAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-10483945119845196832009-06-11T02:05:55.868-07:002009-06-11T02:05:55.868-07:00I had a problem opening files that are not encoded...I had a problem opening files that are not encoded as "UTF-8 without BOM".nowahttps://www.blogger.com/profile/13989040861548788208noreply@blogger.comtag:blogger.com,1999:blog-13722520.post-41921156496741651882009-06-05T11:40:52.277-07:002009-06-05T11:40:52.277-07:00I had a similar problem, but removing the REQUIRED...I had a similar problem, but removing the REQUIRED "VERSION" property is not the solution.<br /><br />This does not solve the issue. This will break certain properties of the iCalendar formatted file. <br /><br />*Recurrence will not work*<br /><br />Please refer to RFC 2445 for the proper formatting of an iCalendar file.<br /><br />Also, your issue with Outlook 2003 may stem from the fact you are not using the following properties: DTSTAMP in the VEVENT, METHOD:PUBLISH in VCALENDAR, and a UID for the VEVENT.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-18090414678968850262009-05-20T20:46:40.547-07:002009-05-20T20:46:40.547-07:00Awesome, I removed the VERSION:2.0 line and this f...Awesome, I removed the VERSION:2.0 line and this fixed my problem - outlook 2003 can now open my ics files. Thanks!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-80834884038423178272009-05-08T03:53:00.000-07:002009-05-08T03:53:00.000-07:00I opened the file in notepad, copied all the conte...I opened the file in notepad, copied all the content to a new empty file and saved it as “test.ics”. Somehow this worked for me. I have seen this before with generated php, unix and other flat files that had content from a third party platform which windows does not see/recognize. By copy pasting the content to new file you get rid of the “unseen” data. <br /> <br />Hope this works for you guys.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-18301640813510831032009-04-18T01:17:00.000-07:002009-04-18T01:17:00.000-07:00Can anyone please give the solution of this instea...Can anyone please give the solution of this instead of posting problems.<br /><br />:( I am creating meeting calendar in c# and it is working fine with outlook 2007 but not for 2003.<br /><br />Please let me know asap if any solution.........<br /><br />Thanks a ton in advance .........Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-42509007014384948922009-01-08T23:30:00.000-08:002009-01-08T23:30:00.000-08:00Hi,i used RemoteCalendarsSetup-6.3(http://sourcefo...Hi,<BR/><BR/>i used RemoteCalendarsSetup-6.3<BR/>(http://sourceforge.net/forum/forum.php?forum_id=697660) and it's working for me.<BR/><BR/>cheersAnonymousnoreply@blogger.com