Thursday, March 26, 2009
The solution: open the 'web.config' file, find the line
<add path="ChartImg.axd" verb="GET,HEAD" ...
and add a "POST" verb:
<add path="ChartImg.axd" verb="GET,HEAD,POST" .....
Tuesday, March 24, 2009
Here are some of the calendar-related fixes in the update:
- OWA and Exchange Web Services (EWS) do not correctly display a monthly/yearly recurring meeting or appointment (KB# 960291)
- Customized properties of a recipient's calendar are removed (KB# 949464)
- Can't read calendar items when some IMAP4/POP3 clients (esp. mobile devices) connect to exchange (KB# 951341)
- Messages Queued for Submission performance counter increases when Domino meeting requests are delivered (KB# 953094)
- You do not receive an NDR after a meeting request was sent after a change to the recipient's LegacyDN (KB# 957124)
And for Entourage:
- The Info store may crash when Entourage client synchs (KB# 957947)
- Unexpected modified instances of recurring meeting (KB# 949113)
- Duplicate Calendar entries (KB# 949114)
Again, this is just a few of the fixes in the update. Read the full KB 960384
Thursday, March 12, 2009
The appointment at 17h00 should read "Jürg":
Quick, immediate, and cost-effective means of correcting: UNIFIER, available from here.
After which his character set conversion issues were no more.
Just to cure your insomnia if it is not already: Meeting Maker server data is stored internally in a Macintosh character set (regardless of what platform you are running on). When we convert Meeting Maker into the intermediate database we convert it into Windows Code Page 1252, Microsoft's default Western European character set (We mainly go to Exchange, after all).
The lower 8 bits with French and German characters should be OK -- but our friends in Switzerland were running with Macintosh clients.
We'll add a UTF-8 option if we get more European demand.
Saturday, March 07, 2009
Since we'd done the rough sketch on running Meeting Maker data INTO Mirapoint (though the people who asked for that are now lost at sea), pulling it out and putting it into Exchange did not seem so difficult.
Actually, when we brought it up at our Friday development meeting the Decryption team at Sumatra already had the full spec, and the Insertion team began modifying the existing Oracle Calendar conversion code and... (don't try this at home, kids, we have years of experience that keep us safe from the occasional software fire hazard)... it was basically running by the end of the day.
So we're reading VCS files and converting them into our common intermediate format, and prepping to do all the sorts of things you've come to expect from a Sumatra migration:
- Preserve the recurrence patterns,
- Guest lists
- Guest responses
- Keep meetings "live"
- Avoid conference room anarchy
- Avoid conference room land grabs
- Whatever else you need
Thursday, March 05, 2009
We were days away from a beta-launch, when our QA team decided to print out the entire collection charts. We were stunned when only the first page printed. Looks like Microsoft decided not to include printing in the first two releases of Silverlight. The work-arounds aren't pretty.
Yah, it was nice to see our President's inaugration speech via Silverlight. But does this mean that the only line-of-business apps available to Silverlight are going to be consumer gaming and video-watching apps? Maybe this is the way to make corporate America greener -- prevent enterprise users from printing Silverlight-generated page via the browser?