Update: Microsoft's Mac business unit just set the land-speed record for turning around a fix. The story is available over at TUAW.

I've been wrestling with a problem for a few days after applying the latest Office 2008 for Mac update (v12.1.3). Everything works well except for sending and responding to meeting notices.

After the update, when Entourage tries to send a meeting notice or response, it throws the following: "[Error] Unexpected data was encountered. [Explanation] Mail could not be sent. Account name: 'Exchange - Greg' Error: -17997."

Needless to say, this is a frustrating problem. I managed to send some original meeting notices by opening them up after they failed to send (you can find them in the Outbox) and clicking the 'Send' button a second time. That worked for some reason. However, the same workaround doesn't seem to work for meeting responses, so I am having to send emails created by hand in order to confirm meeting requests with people who send them to me. Thankfully, when I accept a meeting request it does make it onto my calendar properly - it's just the outbound email that gets hung up.

I've had problems in the past with Entourage not parsing updates created by Outlook, but this is a much bigger and more painful problem. This is another case of "if it just worked the way it's supposed to, it would be the best option by far." A lot like my iPhone in that regard. Glitches kill the experience and create big frustration.

UPDATE: I just found a Microsoft newsgroup thread discussing the problem, and apparently it's a known issue bug in the latest release. Hopefully they'll be able to release a fix quickly. Workarounds include:

• Uninstall Office and reinstall, then update to the version prior to the latest release
  
• Move invitations you create from the Outbox to the Drafts folder and resend (won't work for acceptance notifications, though)
  
• Grin and bear it. :)

I may try removing my Entourage account profile from this computer completely and then setting it back up with the Exchange server fresh just to see what happens. I'd lose a few things that are store local-only in the process, but that won't really hurt me should I decide to go that route.

Anyone else having this issue? Any other great workaround ideas?

The fall conference season is upon us, and I'll be off to Barcelona on the first of November for a week at the Microsoft TechEd Europe/Middle East/Asia conference. I'll be joining my friend and colleague, Richard Campbell, there for the week. If by chance you'll also be there, be sure to let me know ahead of time!

Then, the following week Richard and I will both be traveling to Las Vegas for the Connections conference, where we'll be doing a live RunAs Radio recording session. Should be fun, and we have a great guest slated. More on that later.

If you'll be at either conference, please let me know via a comment or an email!

My friend Richard Campbell and I spent the morning recording a couple episodes of RunAs Radio for publication in the near future. One of our guests (whom we shall reveal when the show is published) provided some amazingly great information about using Performance Monitor, or "perfmon" for short. He's a perfmon Ninja, really. I'm excited about that show because I think when it comes up I think people will be able to learn something quite useful, as it includes some desktop video (perfmon is, after all, a very visual tool) and other resources. I think you'll like it.

Needless to say, both of us have been playing with perfmon for the past hour. Richard just IM'ed me with a funny situation, though:

Not really sure how that works. :)

So, be sure to check out RunAs Radio for the Performance Monitor show, which will be published sometime in the next couple weeks. We've also had a number of other great guests sit down with us over the past while, talking about some very useful topics suited for IT professionals. So check it out!

Want to watch tonight's final presidential debate live on the 'net? Everyone should watch, and please don't skip your opportunity to vote in the election. It's just too important.

Hulu.com is again streaming this debate, and you can watch it right here. Who needs a TV, anyhow?

Dumping the warm-fuzzy naming convention and avoiding the year-based names of the past, Microsoft announced today that the next version of Windows, which will replace Vista, will be called simply "Windows 7."

Good idea.

It's the seventh version of Windows. It makes sense. Returning to a solid, basic, fundamental naming convention helps, I think, in helping to focus purpose on ensuring the fundamental requirements are met, that a solid, simple (from a usability standpoint at least) product is released. Etherial names like "Vista" sound cool, but subconsciously they also evoke an image and set an expectation of something magical, something not quite real.

That's not what's needed, especially this next time around. So keeping the name simple is the first sign of staying focused on the core product. I like that.

As Mike Nash explains, this is the first time a code name for an early product in development has been retained for the final product. Well, given the substantial departure from the conventional Microsoft code names, I'd say it's okay this time. :)

More information is available on the Windows Vista team blog, where the announcement was made.

Space Aliens for McCain or Obama? Could be... Someone's trying to get the vote word out, that's for sure.

Updates: The corn field in the video is at Baggenstos Farms, and you can go walk through it. Also, I'm geeking out a bit on the fact that I filed the video as a CNN iReport that was featured all day today on the homepage of CNN.com and was viewed by 220,000 people in one day (wow). A portion of it was also aired on TV tonight on Anderson Cooper 360. That was fun.

I had a flying lesson Monday morning and on the way back to our home airport, my instructor and I saw an unusual crop formation in a corn field from about 1000 feet above the ground. You'd never see it otherwise. You think someone out there is trying to send us a message? I captured it for you to see with my new Kodak Zi6 pocket HD video camera. You can get the higher-quality version of the video here.

Oh, and by the way: Don't forget to vote!