.VCS files don't import into Outlook 2007 beta

A

Active IT Design

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.

Any ideas or is this just a beta bug?


- Jon

Jonathan OBrien
MCSE, Microsoft Small Business Specialist

Active IT Design, LLC
www.activeITdesign.com
 
S

Sue Mosher [MVP-Outlook]

Have you checked your file association for .vcs files? Can you post the file contents or link?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
S

Sue Mosher [MVP-Outlook]

Thanks. I can duplicate the problem here and will file a formal bug report.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
J

John Roberts

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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top