I just ran into the same issue with some MS Readiness webcast invitations,
but other vcs files worked fine. I noticed that in the webcast files there is
a space after the PropertyName:. I removed the all of the spaces to match a
file that worked, and I was able to import the webcast event.
For example, in the file referenced in this thread, the beginning of the
file reads:
BEGIN: VCALENDAR
VERSION: 1.0
BEGIN: VEVENT
DTSTART: 20060720T180000Z
DTEND: 20060720T190000Z
After some testing, I noticed that it was the spaces after the DTSTART and
DTEND properties that were causing the problem. Now the file wil import as an
Outlook appointment.
I know it doesn't really help with imports, but it may help in the bug filing.
John Roberts
JLR Technology Solutions
"Sue Mosher [MVP-Outlook]" wrote:
Thanks. I can duplicate the problem here and will file a formal bug report.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
"Active IT Design" wrote in message ...
Here's a link to the type of .vcs files that just cause Outlook to start a
blank email message instead of adding the item to my calendar.
http://www.msreadiness.com/EventSche...344&rid=298839
--
Is anyone else having issues with .vcs files not importing into Outlook 2007
beta 2? I'm a Microsoft Partner and I regularly watch Microsoft webcasts.
One of the webcast website features is to download a .vcs file containing the
webcast data and be able to import it into your Outlook calendar. When I
choose to "open" the file to do the import, Outlook fires up a new email
message instead of importing the .vcs as a calendar item. I've also tried to
save the .vcs file and import it manually using the import / export features
of Outlook. Nothing happens with the manual import, it doesn't fire up a new
email message but it also doesn't add the item to my calendar. This is
happening on several computers that I'm testing Office 2007 beta 2 on.