Microsoft recently released a number of security patches for Office for Mac, including updates for Office 2008, Office 2004, and the Entourage Web Services Edition.

According to a March 16th post on MacWindows.com, however, the Office 2008 update (12.2.4) may trigger the long-standing issue of being unable to save Word .doc & .docx files to a Windows server. If you have not been experiencing problems saving files to a Windows server, be very careful before applying this update!

MacWindows.com has posted several potential workarouuds for this issue, including disabling the autosave/recover feature & changing the owner of the sahre on the Windows server to NETWORK SERVICE.

As always, if you plan to upgrade, make sure you have a recent backup and complete plenty of testing before rolling out this upgrade.

iphone_homeApple’s recently released iPhone OS 3.1 has caused headaches & more than a little confusion for some users with Microsoft Exchange accounts. While the OS 3.1 update improves security policy adherence for iPhones when connecting to Exchange Servers, it also has the unfortunate side effect of breaking security compatibility with pre-3GS iPhones & all but the most recent iPod touches. The end result: many iPhone users who upgraded to OS 3.1 suddenly fond they could no longer sync with any Exchange Servers!

Fortunately, the synchronization issue is limited to Exchange 2007 Servers running SP1 & above, & there is a work-around to re-enable synchronization. Unfortunately, the work-around requires either convincing Exchange administrators to create a security policy exception or rolling back to OS3.0 on the iPhone.

In order to re-enable Exchange syncing with pre-3GS iPhones, Exchange administrators will need to create an EAS policy exception that will allow connections to mobile devices that do not support device encryption (either globally or on a per-user basis).

If the creation of policy exceptions is not an option (& that will likely be the case more often than not) there are 2 options: 1) upgrade to iPhone 3GS or one of the latest 32GB or 64GB iPod touch models, or 2) rollback to OS 3.0 (what will undoubtedly be the most popular solution).

The easiest way to rollback to OS 3.0 is obviously to restore the phone from a recent backup using iTunes (you did create a backup before you upgraded your phone, didn’t you???). Apple has a support article detailing how to backup, update, & restore iPhones & iPods. In case of emergency (ie: no recent backups!) you can go to this site to download firmware for iPhones & iPods. [NOTE: This site is NOT supported by Apple in ANY way!!!)

Finally, Apple has also updated it’s Enterprise Deployment Guide for iPhones. If you’re a sys-admin involved in the deployment & management of iPhones &/or iPods in an enterprise environment, this doc is a must-read.

entourage_mac_2008_iconWhile most of the blog coverage on the recent Office 2008 12.1.9 Update focused on the patching of Word vulnerabilities, considerably less attention was paid to what seems to me to be a much more important aspect of the update: Exchange Web Services support.

Entourage Web Services is Microsoft’s upcoming attempt to “achieve greater parity between Entourage and Outlook.”

According to Microsoft’s Description of the Microsoft Office 2008 for Mac 12.1.9 Update, this update is a “prerequisite for the installation of Microsoft Entourage 2008 for Mac Web Services Edition” and will have to be installed before the Entourage 2008 Web Services Edition can be installed.

Microsoft will be abandoning CalDAV for Exchange Web Services (EWS), which should offer better “performance, compatibility, and reliability” since EWS allows Entourage to shift the bulk of the ‘heavy lifting’ to the exchange server, rather than relying on the client to carry the load as it does now. It will also allow for the syncing of Tasks, Notes, and Categories with an Exchange server and will use EWS & HTTP to resolve names from the Global Address List, among other features.

Entourage for Exchange Web Services requires Exchange Server 2007 running Service Pack 1 with Update Rollup 4 or greater. Clients need to be running OS X 10.4.9 or later and the 12.1.9 update for Office 2008 for Mac, plus the Entourage for Exchange Web Services Edition (once released). More information on the Entourage for Exchange Web Services Edition can be found at The Office for Mac Team Blog.

Entourage Web Services is still in the beta stage, however, and not yet available to the general public. Its inclusion in the 12.1.9 update seems to imply that that may soon change.

Update to version 12.1.9 of Office update using the Auto-Update tool, or download the 12.1.9 update directly from Microsoft’s support site.

As with all software updates to mission critical software, please be careful.

entourage_mac_2008_iconAccessing shared folders & calendars is one of the handiest features of Exchange services. Unfortunately, Entourage doesn’t handle shared folders quite as gracefully as some would like. When trying to access folders or calendars shared through MS Exchange accounts, it’s not uncommon to receive the following error:

The user’s folder could not be found. Entourage could not find a mailbox for the user User_Name

This error occurs even though the mailbox does exits & the user followed Microsoft’s directions to the letter – as found here.

There are a couple of potential causes for this error, but the most consistent workaround is to point Entourage directly to the URL of the shared calendar or folder rather than leaving Entourage to try & find the path itself.

Note: You may need to contact you system or exchange administrator to get the full URL of the calendar or folder in order to complete the steps below…

Use the full URL to open the shared calendar

  1. Click File, and then click Open Other User’s Folder.
  2. Click Find user.
  3. Click Advanced.
  4. Enter the user name & email address for the calendar you would like to access.
  5. Type the full URL to the user’s account and Exchange server.
    1. (The URL should be in the following format: https://exchange.<ServerName>.com/exchange/<EmailAddress> )
  6. Click OK.
  7. On the Type menu, click Calendar, and then click OK.
  8. It typically takes some time for the calendar to fully synchronize with the events on the server. Be patient.

More detailed information on this issue can be found in the following Microsoft knowledge base article (The article refers to Office 2004 but is still valid for Office 2008).

word-iconWord’s infamous “Unable to Save: Disk Full or Too Many Files are Open” error apparently still hasn’t resolved , as of the latest version of Office 2008 (v12.1.5).

It popped up today at a clients office when one of the staff was attempting to save a .doc to her desktop. Saving to a new location produced the same result. So did trying to save it as a .docx file.

Fortunately, there’s a fairly painless work-around: save the file as a Rich Text Format (.rtf) document. Then close & re-launch Word & open the .rtf file & re-save it as a Word document. Unless you have some exotic formatting, everything should look identical.

It’s important to note that this is more of a bug then a genuine error & doesn’t necessarily have anything to do with having too many files open. And while it occurs most often when trying to save files to network shares, apparently local saves are not entirely exempt either.

Details on the causes of the error, as found on word.mvps.org, can be found below. It’s a bit old & focused on saving to servers but the general principles (& problems) seem to apply for local saves, too.

Here’s a  link to a short thread on the subject from Mactopia’s Office For Mac forums.

Can’t Save or Re-Save

Cause

The error message you see “Unable to Save: Disk Full or Too Many Files Are Open” is a generic “Sorry I am unable to save” message, and it can be caused by anything that prevents Word from obtaining an acknowledgement of completing its write to disk, including userID permissioning errors, failed network connections, more than about 9 documents open at once, inability to store or release its lock file on the server, or even the reason stated!

However, the cause we are most familiar with on the Mac is due to bugs in the transport between OS X and the file server. Apple and Microsoft introduced changes to overcome a security hole a few months ago, which caused the data stream between the client and server to be authenticated more strictly, and this has exposed errors which have been there forever.

The issue is with the way Word “streams” a file to or from storage. The problems are not exposed in other applications, because they do not attempt to open multiple connections with the file server.

Work-Around

One work-around that is partially successful is to set the Word>Preferences>Save to ensure that Fast Saves is OFF and Always Make Backup is ON. This doesn’t cure the problem, but on some kinds of servers, it raises the number of saves you get before you see the problem to around 60 saves, which is more than most users do on a single document.

When a user gets this error, they will find that if they attempt to save the document in RTF format to their local disk, they will usually succeed, thus preserving their work. (Italics are mine).

Until this bug is finally fixed, users can use Finder to copy their document from the server to their local disk, work on it there, then use Finder to copy it back again. Word must be quit, not just minimized, when you copy the document back to the server.  The bug won’t strike if both the file and its attached template are on a local drive.

Other than that, all you can do is keep your server and client patches up to the latest released levels and keep hoping: just like the rest of us.