Click for MacWindows home


Access Your Computer From Anywhere
Control a PC from a Mac over the Internet

MS Outlook 8.x for Exchange and Macs

Information related to the Macintosh Outlook Client

Last updated July 2, 2001

On this Page:

For information on the newer Outlook 2001:Mac client, see our and our Outlook 2001 special report and our Outlook 2001 Beta special report.

Recent Version History (for Outlook 8.x)

Outlook 8.2.2 for Mac was replaced by Outlook 2001 in June of 2001.

Outlook 8.2.2 for Mac

Microsoft Outlook 8.2.2 for Macintosh was released at the begining of May, 2000. According to the online readme file, the update contains may bug fixes, including problems with corrupted calendar information, problems with such as NAT (Network Address Translation) gateways such as AirPort Base Station, and a Y2K fix.

Exchange 5.5, Service Pack 3

In September, 1999, Microsoft released Exchange 5.5, Service Pack 3 (download here). This service pack includes some bug fixes, a new administration feature called Mailbox Manager, as well as some other features. Outlook 8.2.1 for Macintosh (see below) is also part of SP3, though it actually preceded SP3's release. The SlipStick SP3 page has a good summary of what's new. You can also check Microsoft's SP3 page.

Outlook for Mac 8.2.1

On August 17, 1999, Microsoft posted Outlook Mac 8.2.1, both the entire client for PowerPC and 680x0, and an updater for Outlook 8.2 (PowerPC). Both are free. (There's also German, French, and Japanese versions.) Outlook 8.5.1 has nearly a dozen bug fixes, including:

The ReadMe file has a complete list of fixes.

Outlook for Mac 8.2

Microsoft released Outlook for Mac 8.2 in June, 1999. (See below for what's in it.) A reader reported that a Microsoft Knowledge Base article briefly appeared that said Outlook 8.2 was part of Service Pack 3, but was removed. So far, there is still no mention of Service Pack Three.

Exchange 5.5, Service Pack 2, and Outlook 8.1

Microsoft released the new Service Pack 2 for Exchange 5.5 just before Christmas of 1998. It includes better support of Outlook for Mac clients, according to Microsoft:

Web Resources

Reader Responses and Tips

Topics on this page:

Problems with Calendars with Outlook 8.1, Exchange SP2

Most readers are having problems accessing calendars created by Windows 95/98. However, a few readers report that the Mac client can view calendars created by Windows NT. Below, a reader offers an explanation of the calendar problem and how Exchange/Outlook works. Another reader offers two suggestions on how to get Mac Outlook to read Win 95/98 calendars, which he says he got from Microsoft.

David Dutt , January 14, 1999

I tested out the new Outlook 98 Client for the Power Mac that comes with Exchange 5.5 SP2 and I am not able view calendars created by using Outlook 97 for Windows. I read the release notes, but I did not see anything there. I only see my Schedule + Calendar (created from my Mac), not my Outlook 97 for Windows Calendar. In addition, I'm not able to display any Public Calendars. Anyone have any ideas about this?

John Wolf, January 15, 1999
Macintosh System Administrator
Temerlin McClain

"Just add another Me Too to the list. I installed the SP2 (8.1) version of outlook as well and I don't see any way to access public calendars either. I just assumed that it could only access Office 97 personal calendars and left it at that."

Dan Kessler, January 15, 1999
AR7 HooverDesmondArchitects
Denver, CO

"I, as well , have had the same problems with the new Mac Outlook 98 client. Previously I had been using the Mac Exchange Client with Schedule +, and thought I'd be better off with this new version. Frankly, the only difference I can see is a vertical menu on the left-hand side of the screen. I still can't see any calendars prepared by Outlook 97 for Windows. The only calendar I can see is what I create. I can't even see a calendar created by other Mac users!

"I don't know if it was supposed to be fixed with this new version or not, but I also can't see any contacts created by other users. The list of contacts shows up, but when they're clicked on, a useless "sent" e-mail message window opens with the contact's name in the subject. The Outlook Journal or Notes features don't work either. What a piece of junk.

"Forget it...Outlook Express 4.5 is way better anyway. I just leave the app running (it only uses 4.5 MB) and set the preferences to check my mail from the server every five minutes. I suppose that for now I'll have to stick with actual verbal communication and a day planner for scheduling."

Frank Pappajohn, January 18, 1999

"Ditto for me and the calendar-viewing problem with Outlook. I had been using the SP1 version and could "see" the individual messages listed in a list-type (like the mail) window pane, but Outlook obviously didn't know how to convert them into a calendar. Plus, these individual calendar events had no date attached to them (other than the modification date, like that's important!), so they're useless.

"I upgraded to the SP2 version, but still the same problem. Hope they fix it soon."

Phil Noguchi, January 22, 1999

"I use the SP2 Mac Outlook, and in general have had the same experience [as other readers], with one exception. Using the calendar, I can see other calendars to which I have been named as having access. It is very frustrating; I don't want to see my colleagues calendars, rather my own."

Works as Advertised.
Mark Ringo, January 18, 1999
Pier 1 Imports
Lead Network and Macintosh Technical Administrator

"I want to state for the record that the Exchange 5.5 SP2 Client (Version 8.1 Outlook) is a product that works as advertised. I am the Macintosh Administrator for Pier 1 Imports and an MCSE with Exchange Server certification. Our Exchange server (version 5.0) is configured properly and all members of our LAN (roughly 900) all use Exchange/Outlook. This product works well under Mac OS 8.51 and we are able to view calendars created by NT users every time. Possible the users that are attempting to view an NT user's calendar doesn't have appropriate permissions to do so. The only time that I am unable to view a calendar now is when I don't have permission."

More problems with Calendars. April 1, 1999

Byrne Lovell writes about accessing calendars and other topics:

I work in a Mac-hostile organization, where I nevertheless obtained the Mac Outlook from Exchange 5.5 SP 2. I can connect to our network from home, and to my Exchange server account which I access at work via Outlook 98 for Windows. Outlook looks OK. The e-mail portion works very much like Outlook 98/Windows. The Calendar part looks more like Schedule + 7.0 (or 7.1 or 7.5) - it has tasks and contacts built into it, not into Outlook itself.

Like many others who have commented, I cannot see my own schedule. I can, however, see other people's schedules just fine. If I click on the Outlook icon in the icon bar, I get a nice-looking calendar display with no data. If I click on the Calendar folder, I see an e-mail-like list of envelopes that probably contains my schedule data but isn't displayed properly and isn't the least bit useful. My problems are not caused by permissions - I can see everything I need from my laptop with Outlook for Windows client when I dial up from outside the office, and I log in with the Mac using the same ID.

I have checked at the office, and I think we are running Exchange 5.5 SP1 on the Exchange servers. This may be the problem. I am not sure how I could urge our server folks to try SP 2, since they are really very happy to tell me that Macs aren't supported. It would be interesting to hear from some of the others who have reported problems (and from those for whom Mac Outlook is working) which version of the Exchange server software they are using. Perhaps there is some way that the Exchange server has to be configured?

See also the two suggestions for solving this problem that Lovell sent us.

Can't view Outlook 98 Calendars. April 5, 1999

Rich Tench writes:

I too cannot view my own Outlook 97/98 calendar using Mac Outlook 8.1. I think that those people who aren't having this problem don't in fact have a calendar created with Outlook 98. If anyone has experience in creating their own calendar using Outlook 97/98 and then trying to view it using Mac Outlook 8.1, please let us know.

When I called Microsoft technical support they were very professional and helpful right up to the point where I was supposed to connect with an Exchange specialist. Then people stopped returning my calls.

How Outlook and Exchange work, the calendar sharing problem, and other issues. April 29, 1999

Mike Weber wirtes:

I just found your page and have some comments about Outlook 8.1.2449.4 This is the version of outlook that comes with Exchange Server service pack 2. Some people refer to it as "Outlook 98," but there is no internal or external reference to "98" in the product.

Regarding calendars: I've had the opportunity to play with Outlook 98 (Windows) and Outlook 8.1 (Mac) side by side, and this is what I've found. It seems that there are two types of calendars kept on the exchange server for each user; the "Outlook98" calendar, and the "schedule+" calendar. These calendars are complete independent of each other. The Mac 8.1 client uses the Schedule+ calendar, and the Outlook Windows client uses the Outlook98 calendar.

When you use a Windows Outlook 98 client to open another person's calendar, it shows you the Outlook 98 calendar, if it exists. If it doesn't exist, you're shown the schedule+ calendar if your copy of Outlook has schedule+ support installed with it. (Some of our installations are mysteriously missing this ability; others are fine.) If a user has ever created an appointment for their account from an Outlook 98 client, that Outlook 98 calendar will obscure the schedule+ calendar from viewing by Outlook 98 clients.

If your primary machine is a Mac, and you keep your schedule on your Mac calendar, it will appear as though Windows Outlook 98 clients can't see your calendar. They can, but the Outlook98 calendar is "getting in the way." The only way I've found to clear things up again so that Windows Outlook 98 users can see the calendars of Mac outlook 8.1 users is for those Mac users to delete the "calendar" folder that appears in their inbox and reset the permissions from the Tools:Set Access Permissions menu item in their Mac calendars.


I've always been able to open the Outlook98 calendars of my colleagues who have given me permissions to do so in their calendar properties and sharing setup. You can't see calendars you don't have explicit permission to open.

The Mac client also does not know how to interpret folders that contain calendar items; this is why you see nothing but a meaningless list of messages in the "calendar" folder used by the Windows Outlook98 client, or in any public folder that is defined to contain calendar items (we have tried to create "public calendars" but the Macs are unable to participate.

It may help one's understanding of the Mac client's limitation to realize that the Exchange server is nothing but a huge database server, and the clients are responsible for presenting the information in a coherent and sensible fashion. The Windows Outlook98 calendar really is a bunch of mail messages as far as the server is concerned. The Outlook98 client simply interprets and draws them as a calendar. The Mac client doesn't know how to do that. It also doesn't understand Contacts, which are another kind of special, interpreted mail message stored in the Exchange database, or Journal entries, or... the list goes on.

I've also observed the "pause" problem. I'm glad I'm not the only one! I see this problem most often when I have more than one MS application open, when one of them is Outlook, and when Outlook has at least one message open. From what another read posted about IE 4.5, I might hypothesize that one of the MS shared libraries that has to do with networking may have a bug in it.

Enabling Mac-Windows sharing of Outlook calendars. July 30, 1999 --

Byrne Lovell offers two suggestions for having Mac Outlook 8.2 access Windows 95/98 calendar data:

I've done some more research on Mac Outlook 8.2 and its inability to see the Win Outlook calendar data for its own account. I called up someone at MS (425-635-7031), and he was pretty helpful. The basic problem is that Mac Outlook uses the calendar (and I presume contacts) format used by Schedule +, while Outlook 97 and Outlook 98 for Windows use a different format. Your Mac Outlook can easily read your Outlook 97/98 e-mail folder, but can't read the calendar or contacts etc. However, you should be able to read the Calendars of other users!

There are two avenues that might work around this:

1. Set your Outlook 97/98 to use Schedule+ as your calendaring program. You have to have some additional files installed - the Schedule+ files from version 7.0 or later. The downside of this is that the compatibility between your Outlook 97-98 with Schedule+ and your peers with the normal Outlook 97/98 calendaring may suffer. But maybe not too much - who knows? MS doesn't reveal this anywhere I can find.

2. Since it is possible to use Mac Outlook and see OTHER PEOPLE'S Outlook 97/98 calendars, use this route. Have a second account set up for you for your Mac access. If this account is ever accessed by an Outlook 97/98 client, then you will have to ensure that it is configured to use Schedule+ as the primary calendaring software, because it will create calendar files in the Outlook 97/98 format; if it is never accessed by any Outlook 97/98 clients, you MAY not need that step.

Go back to your main (i.e., "real") account via Outlook 97/98, and give your secondary account all the permissions you can find - making it a delegate might be a good idea (who knows?). Some of this can be done in the tabbed Options-type dialog, some may need to be done by right-clicking on each relevant folder in the Outlook 97/98 window and bringing up the properties or permissions dialing (don't have that in front of me now, can't be sure of the label).

Now when you log on to your secondary account, your main account will be visible in the same way that any other Outlook 97/98 account is, according to the permissions granted to you (and you've already made sure you have all the permissions you could possibly need). So you can see your regular e-mail and calendar (and contacts and ...). If your Outlook 97/98 account has made your secondary account a delegate, you should even get copies of any meeting invitations sent to your regular (Outlook 97/98) account, and can respond to them.

I was also told that I could send my wish list to

Another suggestion for Outlook Mac/PC sharing of calendars and contacts. August 4, 1999 -- Colin Marrow offers another workaround for sharing Contacts and Calendars between Macs running Outlook 95 and PCs running Outlook 2000, with Exchange Server 5.5 SP2. However, Marrow admits that the this method may not be particle on a large network, as it requires a de-install and reinstall of Outlook on all PCs.

The problem that I encountered (and other contributors have referred to) is that the PCs and Macs could not see the shared folders in a useable form, or could not open. Most of the conflict arises, I believe, because the Mac client uses Schedule format, the PCs use Outlook format, the two are not compatible...The clue was that I noticed that when installing Outlook 2000 for the first time it gives you the option of selecting Outlook or Schedule as your default calendar.

On the Macs:

  1. Install the Outlook Client for Mac
  2. Assign full permissions to all the users that you wish to.
  3. Select one Mac to be the central store that others will connect to, doesn't matter which one.

    On the PCs:

  4. If Outlook 2000 has already been installed, uninstall it. It would be prudent to export the contents of the mailbox just in case the wheels fall off!
  5. Reinstall Outlook 2000
  6. Start Outlook
  7. Your original Contacts, Calendar and e-mail messages should be still there.
  8. Select File/Open/Other User's Folder
  9. Type in the Name (or Browse) the User Name that you have designated as the central store, select Folder Contacts.

    You may get a message that Outlook cannot open Schedule, do you want to install support for this now, say yes. The Folder should open, Captioned

    Username - Microsoft Schedule+

    Edit/create at will!


    If Outlook hasn't yet been installed on the PC run the install programme. You should get asked whether to use Outlook or Schedule as the calendar, select Schedule

    I can read/create/edit entries both ways in the Calendar and Contacts.

    I haven't yet found a way of creating a Public Folder on the server that Mac clients can interpret correctly...Macs see any public folder as containing mail items whereas the PCs will see mail, contacts or calendar as appropriate. It is easier for me to designate one Mac user as the "Public" Calendar and Contact source.

    I've also tried giving permissions on a PC user's Contact folder and have managed to get a Mac to read it, but not write to it, get User hasn't given permission error, even though all permissions have been granted and the Mac has been defined as a delegate.

    The Calendar does not update for other users until the originator has exited the window.

    ...the Macs can read and write to a Mac folder, as can the PCs, but a Mac can only read a PC folder. This must be a permissions issue, but I have set all the permissions I can find but all I get when attempting to write from Mac to PC is a message "Username has not given you permission to create items of this type".

    ...this may not be a solution for large networks [since] a de-install and re-install of Outlook would be needed on all PCs this may be a major overhead for system administrators...If there are ways of automating the client roll out (thinking about it, there must be) then what I propose may well be viable.

Problems with fonts, ATM Deluxe

Outlook 8.2 for Mac has a conflict with Adobe Type Manager Deluxe that causes crashes under certain circumstances (with a lot of active font sets). A number of readers have offered workarounds. (For more on Outlook crashing, see Crashing: Type 3 errors and Font conflicts, Suitcase 8.x below.)

Markus Norsted
Innovative AB,
Stockholm, Sweden
January 27, 1999

"Yes, I too downloaded the updated Outlook version from MS, installed it... and crashed. I couldn't even get the application to start. After several attempts (including a fresh installation of the Mac OS, version 8.5.1) I finally got Outlook to run. I then realized that it was ATM Deluxe (the control panel) that caused the crashes when starting MS Outlook. On some Macs, we had to totally disable ATM to get Outlook to run, but on some Macs it worked to disable all font sets and THEN start Outlook.

"I'm glad that we tracked down the problem, but as we need ATM for all font handling, this is a severe problem for us. I haven't yet tried to use other font management software (like Suitcase etc.), but this might work.

"The other trouble is, however, the MS Outlook application itself. As I work at a company that consists of 95% NT-machines and all communication, booking and scheduling is made through Outlook, me and my Mac-buddies have to get this to work. The promised update of the Calendar does not seem to work. We can't seem to share the calendars between us, Contacts can't be opened at all (are only shown as strange folder-icons) and the interface overall sucks.

"Can't someone at Microsoft please, please take a look at this problem.We need this to work!"


Johann Dijkstra of the Netherlands proposed this solution (Sept. 15, 1999):

Dieter Gohl proposed another solution (Sept. 20, 1999)

Dieter Gohl was having crashing problems with Outlook 8.2.1 on over 100 Mac's in his network. Disabling ATM Deluxe (4.0.3, 4.5.1) avoided the problems, but he eventually narrowed the source to active font-suitcases. With more than 128 active font-suitcases on a system, Outlook crashes with different messages. It doesn't matter whether the fonts are activated by ATM, Suitcase or directly by the system. With less than 128, all works fine.

J. Lucia (Sept. 22, 1999) offers a description of what's behind the Outlook /ATM Deluxe conflict and offers some more workarounds to the problem.

Outlook 8.2 uses the same bogus font manager that MS Word 6.1 did, therefore activating too many fonts causes it to die. Most of our issues with Outlook do stem when we have too many suitcases open, however, this is not always the case. Since we only use Adobe fonts, we purchased the Font Folio (8.0), and have organized our fonts with Font Agent 8.0, so there is absolutely no font corruption (ATM 4.5 confirms this as well). Our issues range from hanging when accessing the Calendar to intermittent lockups or the famous "Message has exceeded the maximum display area" dialog box.


Quitting Outlook, turning off ALL of the fonts managed by ATM and restarting Outlook has corrected all of these issues. In fact, a trick that can be used is to start the Mac with a very basic set of fonts (leaving all of the rest deactivated by ATM), launch Outlook 8.2 and log on. Then go back to ATM and activate the other fonts that are required to do your work. Outlook will NOT check the updated ATM database (like other applications) and will not load the newly activated fonts into memory--it has made Outlook actually usable in our case.

Also, we limit the fonts that are managed by the OS to essentially the ones that came with 8.6. We do put the Adobe Sans and Ser, Symbol, and Zapf Dingbats in there as well since they are required by ATM and Acrobat (this way we don't need to rely on ATM to be running to view PDFs).

More on ATM and fonts, and a new ATM problem

Ed Hagihara
September 29, 1999

I currently work as a network administrator for a magazine publishing company that has at least 350 Macs & PCs companywide (and growing), and I've seen at least two distinct issues concerning ATM w/Outlook & Exchange.

The first has already been mentioned - too many fonts active has given us some problems (too much text error messages, and unable to find the exchange server), so we've told people to deactivate some of their font sets before going into e-mail.

The other problem that we've been having seems to be with the Myriad multiple master font that comes with ATM. It's caused some other weird things to happen - for instance, when a user starts Exchange, it looks like its trying to launch, then it does nothing and takes you back to the desktop. We use OS 8.1, 8.51, and 8.6.

TIP: locked inbox related to fonts

September 13, 2000 -- Scott Bittick found an odd problem with Outlook/Exchange 8.2 for Mac that seemed to be related to fonts. A user's e-mail was "stuck" in her inbox. The mailbox showed 30 messages, but none of them appear on the right hand view window; clicking on the inbox did not display the messages. Bittick tried the repair tool, rebuilding the Desktop, and removing the Prefs file to no avail. He finally found this solution:

  1. Remove old Outlook including prefs
  2. Put the Fonts folder on the desktop and reboot
  3. Reinstall Outlook & config
  4. Reinstall fonts and reboot.

    It should be noted that I did not replace the fonts with the same fonts that I had removed from the System folder. Instead I used a clean set of fonts that we keep on our server, and later discovered that several of the problem fonts were corrupted. Thanks to FontAgent 8 for finding the corrupt fonts.

Outlook problems with hanging and other issues

Exchange 5.5 SP2 Minor problem.
Dave Green, January 18, 1999
Platte River Power Authority

"We are using the new Microsoft Outlook for Macintosh Exchange Server client (version 8.1.2449.4) and it works as advertised. We can see Windows calendars from the File-Open-Other's Appointment Book command.

"So far the only problem has been an intermittent failure when attempting to view an e-mail message. The screen sometimes fails to display the contents of the window. Quitting the application and reopening takes care of it."

Outlook temporarily hangs.

February 12, 1999. Rob Eberhardt described a problem with Outlook 8.01.x and 8.1.x that temporarily locks up the Mac.

"I've been having an odd problem with the Mac Outlook client, Exchange Server edition. The symptom is that the system will seem to lock up, but more accurately behaves as if it is on "pause". Glancing at the clock, you can see that the seconds have stopped ticking. A click of the mouse anywhere on the screen will allow the system to continue on for a few seconds and then stop again. Another mouse click and a few seconds more, and so on. It seems as though once you quit out of Outlook, the system runs fine again. I've tried Outlook versions 8.01.x and 8.1.x and both seem to have the problem."

April 2, 1999. Sam Swett agrees:

I would like to confirm an issue I read on your Exchange 5.5/Outlook for Exchange page (xch55sp2.html). Regarding "Outlook temporarily hangs. February 12, 1999" - when the writer says that you must click the mouse to have processing continue, I actually think that the problem is in a shared library common to more than just Outlook for Exchange. Why? Well, I have the problem at home also, where I don't have Outlook for Exchange. I *do* have Internet Explorer 4.5 though, and sure enough, I occasionally have this problem, but I don't know what triggers it. This is my biggest issue with tracking the problem - I can't get it to happen on demand, and therefore can't really test it.

May 12, 1999

Mikkel Pedersbæk reported that after installing OS 8.6, MS Outlook no longer "hangs" the system, as reported above. However, Rob Eberhardt reported (May 27, 1999) that MS Outlook still hangs even with OS 8.6.

October 15, 1999 Microsoft recognizes the problem
Rob Eberhardt

I wanted to report some good news for the many out there experiencing the dreaded "mouse click" problem with Microsoft Outlook 8.x, Exchange Server Edition. I have been working with someone from Apple and from Microsoft on this issue for several months, sending debug logs and configuration information. This has been a difficult issue since Microsoft was never able to duplicate the problem. Now, they have finally reported that they are able to reproduce this problem with Outlook Exchange, IE and IE Download Manager. They have logs with debug symbols turned on that show the problems. I plan to keep the heat on each representative to solve this problem now that it has been confirmed.

P.S. I had originally reported on this problem on the MacWindows site in February of this year, so a fix has been a long time coming!

Outlook and other Microsoft apps hang with Mac OS 8.6. June 4, 1999

John D. Peterson reports this problem:

We've been experiencing the slowdown/hang problem for several months. Unfortunately I haven't been able to pin-down what caused it to start. We see it on both systems here, a PowerBook 3400/200 e/w 144 Mb RAM w/Virtual Memory On, and a G3/300 Minitower e/w 384 w/Virtual Memory On. Both boxes are running OS 8.6 and the problem has occurred with Word 8.0 with all the current Office updates, Internet Explorer 4.5 (0408), and Outlook 8.1.2449.4 each individually.

The problem manifests itself in a slowdown that culminates in a hang that can be broken by clicking the mouse which restarts processing for a few moments until the system slows-down and hangs again. Whatever process is sucking-up CPU time appears to have a higher priority than all but a hardware interrupt. Causing the hardware interrupt via the mouse appears to open-up the time-sharing of the CPU for a short period of time.

I've started to work through the usual suspects, Control Panels and Extension conflicts, but without success. Sometimes the system will run for 48 or more hours before hanging, sometimes only an hour or two. There does not appear any identifiable trigger, however it is when printing that the problem is often first noticed. A print job will just not be run in a slowdown/hang without quitting the Microsoft apps that are running. Once they are quit, all is well. As part of troubleshooting the problem, I trashed all the installed Microsoft Control Panels and Extensions and let them be reinstalled upon first-run to no effect.

On June 7, 1999, Chris Erickson reports that the answer can be found at MacFixIt:

The best information that has been surmised is that one of the NEWEST Shared Libraries from Microsoft (most likely IE 4.5) causes some kind of low-level massive thread spawning to occur, only a hardware interrupt will resume processing. This condition is NOT observed with only the Office 98 libraries installed. The assumption is that either IE 4.5's or Outlook's related Shared Libraries are at fault.


This issue is NOT to be confused with the "DHCP Hang" that has been reported, especially with cable modems, during that pause while O.T. is trying to renew a lease on an I.P., no interrupts are successful, waiting up to 2 minutes for the time-out is always successful.

Michael Curtis (June 16) has a different solution, as lease for MS Word:

I had exactly the same problem at a client with Word 98 locking up everytime you went to any Word menu. If the server wasn't mounted it was fine.

In the end we found it the preference telling Word to remember the last x (9 by default) number of jobs opened in the file menu. We set it to zero and it was fine.

Outlook won't launch: Conflict with "ObjectSupportLib" extension file

J. Jordan (June 30) found another Outlook conflict with a library file:

One of my Mac Outlook ES 8.1 users reported a solution to the inability to logon under OS 8.6 as there being a conflict with the "ObjectSupportLib" extension leftover from a previous system. Removal of the extension made for many happy logons.

The "ObjectSupportLib" extension file that causes a conflict with Outlook 8.1 is an old Apple file used for managing Apple Events in Mac OS 7.5through 7.6.1. Unfortunately, by default, the installers for versions of Navigator and Communicator earlier than 4.05 install it by default. You can do a custom install to aviod installing it. (If you already have it on Mac OS 8.0 and later, through it away.) Indiana University Knowledge Base has more detailed info on ObjectSupportLib is in some detail.

Exchange Server SP2- Configuring the Mac hosts file for name resolution. June 8, 1999 --

Greg Newton sent us information on how to configure the Mac TCP/IP hosts file for name resolution with Outlook 8.1, and the Exhange Server 5.5 SP2. (His Macs have Mac OS 8.6.) The procedure is described in MS Knowledge Base article Q189906. Newton says:

[Our] server is not set up with DNS service. Installing Outlook 8.1 on the Mac clients we found that entering the server name along with the mailbox name and clicking the "Check Name" button yielded an error indicating that "There is a problem with the network, The name could not be resolved". After much trial and error we found that entering the IP address in the server name box (the same value entered when setting preferences in IE4.5 with Proxy Server) and clicking the "Check Name" button the error disappeared and the correct server name appeared in the server name box. No amount of trying to force the name resolution worked, only the IP address was successful.

Unfortunately Outlook will only recognize the server name and NOT the IP address when being set up for use on a client computer. This exercise proved that Outlook was indeed able to connect to the Exchange Server, but that name resolution was the problem. The first step we took to attempt to correct the problem was to write a simple "LMHosts" text file as per DAVE 2.1 instructions to force the name resolution for a local server, and checking the "LMHosts" check box in DAVE setup. No luck and this had no apparent effect. We uncovered another approach by checking the MacOS TCP/IP control panel and setting the User Mode to "advanced", which pops up a "Hosts" button. We were unable to get the required format of the HOSTS text file correct...

...We checked Microsoft support and found the information we needed. Look for an Knowlege Base article ID : Q189906 "XLCN: How To Ensure Proper Name Resolution". This article lists the required format for the MacOS TCP/IP Hosts file. Writing a simple two line text file, inserting it into each system folder on the client Mac's is the first step. Then open each client TCP/IP control panel, click on HOSTS and locate the new HOSTS file. Select it and click OK saving the TCP/IP changes to the control panel settings. Reboot the client Mac's and presto... Problem solved...

[See also Knowledge Base article Q149596 - 'XCLN: Configuring Mac Client for TCP/IP for this type of information.]

Getting Exchange Server to access a POP account at ISP. June 9, 1999 -- A reader asked:

We have not yet found a method to have Exchange Server 5.5 dial up our current ISP's POP Server and periodically check for mail incoming to our domain name and download it to Exchange Server. Does anyone have a solution to this problem??

John D. Peterson answered with this advice:

For a _very_ small organization you can use the Administrator's account to fetch each person's e-mail from the POP server using Tools:Services:Add:Internet Email in the Outlook menu. We set-up a series of rules with Inbox Assistant to then forward, and delete the mail from the Administrator's Inbox, leaving the original message intact which gives you a transparent connection. Mail appears in the User's Inbox immediately after being pulled from the POP server.

The downside is that most mail lists must have their own discrete rule for each User. The upside is that most spam stops there (the Administrator's Inbox) since it is not addressed to a specific person and is periodically trashed by me until I get the time to see if I can't create a general rule to automatically trash it.

December 27, 2000 --
Daniel Schwartz, who runs the Mac-NT list serv, adds this:

OK, what you want is for your ISP to support ETRN. In addition, there are a number of "Exchange Aware" ISP's (including my own, SNiP) that can directly support what this reader wants. Start with the very good Exchange FAQ's at Swinc's site; then move on to the list of Exchange aware ISP's. Finally, the SNiP site has a step-by-step tutorial for Exchange 5.0, 5.5, & SBS, complete with screen shots.

January 2, 2001 --
Scott Herrera

At my old job a few years ago we came across this issue. Yeah we tried to get our clients' ISPs to do ETRN and all of those other ways. Well then I came across the perfect simple solution: VPOP3 from Paul Smith Computer Services. All you have to do is run it on your Exchange server forward the mail to the Exchange Service.

There are a couple mods you have to do to your NT box, but its worth it. Since VPOP is basically a mail server that can also pick up mail via POP from other servers it will fight with Exchange for the POP and SMTP ports. You just need to go in and modify the ones Exchange is using. Though this will stop you from being able to use your Exchange box as a POP server. If you need to use your Exchange box as a POP server, a better idea is to run VPOP on another machine (doesn't need to be that fast) if you have the extra computer and need to use POP on your Exchange box. And to top it off, it costs under $200 and is only a 1.4 MB download. I could take it to clients on a floppy.

Outlook 8.2 for Mac

Greg Newton ran into a Microsoft Knowledge Base article on June 4 that described Exchange Server Service Pack 3 and Outlook 8.2 for Mac (posted June 14). The article was dated June 1, but by June 6, the article had been removed. The article ID was Q234039, keyword "exc55sp3", dated June 1, 1999, and was titled "XLCN: What's New In Outlook 8.2 for the Macintosh". The article described what is in Outlook 8.2:

The information in this article applies to: A Microsoft Outlook for the Macintosh, Exchange Server Edition, version 8.2.


Some of the new features in Microsoft Outlook 8.2 include:

June 16, 1999

The new Microsoft Outlook 8.2 for Mac looks good, according to John Wolf:

The drag and drop for enclosures is a very welcomed addition. Drag and Drop not only works with enclosures, but it works with text. If you have a Word document open, you can select a portion of your email message and drag it over to your Word document... and vice versa!

June 22, 1999

Gregory Newton also likes the version 8.2:

Absolutely flawless upgrade on all client Macs from 8.1 to 8.2. No crashes and appears very stable. Now all we need is compatibility with Windows versions of Outlook...

June 25, 1999

Damon Casey reports of some problems with Outlook 8.2 and the UK version of Mac OS 8.5.1:

I would just like to report that I have just installed Outlook 8.2 on a G3/300 Minitower running UK OS 8.5.1 and I am unable to send or reply to any emails. As soon as I click the send button in an open email message window Outlook quits and freezes the Finder. I have tried removing all third party control panels and extensions so that only Apple and Microsoft extensions remain active to no avail.

Robert Mroch reports:

The latest release of Outlook seems to have fixed whatever was preventing Outlook from running on our Macs. Also one of our guys mentioned that upper and lower case in the user name is an issue when logging on from the Mac's.

TIP: Moving email files from Outlook for Mac to PC (and visa versa)

Several readers have asked how to move received email messages from Mac to PC, so we asked our readers for their favorite technique. Here are some of the responses. The answer is simple: keep your messages in the Inbox. When in the Inbox, you can see the messages from either Mac or PC--even simultaneously. There is no need to move any files.

If you do have your messages in personal folders, you won't be able to access them from another computer. If you want to move messages that are in personal folders, you can read a tip from Bill Reynolds:

If the user has saved the messages to Personal Folders (.PST file), transferring those messages from PC to Mac (or Mac to PC) is simple: On the source computer, create a folder (e.g., "Moving Van" without the quote marks) INSIDE the Inbox (not at the root of the Mailbox), and move each Personal Folder (and its contents) one-at-a-time into that folder. On the destination computer, configure a Personal Folders file (.PST) if you don't have one already, launch Outlook, and move the individual folders inside "Moving Van" to the new Personal Folders location. (I wish Personal Address Books could be converted so easily.)

TIP: Moving Outlook personal address books PAB files from PC to Mac.

April 12, 2000 -- We asked readers how they move personal address books (.PAB files) from PC to Mac:

Jean-Paul Boucher

It is relatively easy to export and then import the Contacts/PAB from the Windows version of Outlook to the newer Macintosh Outlook Client (8.2.1). This latest version of the Macintosh client actually comes with an import feature for the Personal Address Book. Simply export the addresses from the Windows client in a Comma Separated Values file (CSV) copy the file to the Mac, and then choose File...Import in the Macintosh client. It will then ask for the file and attempt to match the appropriate fields.

The one catch is that the field names are very specific and if any data is incorrectly labeled, the import will fail. The user can define the fields during the export from Windows or by using Excel. the list of the proper field names is held in the Outlook Help. There are some weird ones (like Zip Code is called Postal Code, etc.).

Robert Taylor

In the Exchange/Outlook profile set the mail delivery point to the Exchange server, not to a personal folder. On the PC, start a new mail message and add all of the entries from your personal address book to the TO: or CC: area.

Close and save the message without sending it. The message should show up in the inbox. Close Exchange/Outlook on the PC and open it on the Mac. Open the saved message. When you control-click on each of the names you will have the option to save them to the personal address book on the PC.

Martin Forrester

The same method works in the reverse direction! In the Mac Outlook client you can control click on each of the addresses (in the message you create on the server, containing all your address book entries) and choose "Add to Personal Address Book" from the contextual menu.

Dan Thomson

I recently moved the address book for Outlook express from Mac to PC. I exported the contacts as a tab delimited text file, read the file into MS Word and used the "replace" feature to remove the tabs and insert the comma's that OE is looking for as comma delimited import file. Save the file as MS-DOS text. Print the file from Word and use it to define the import field headers when importing the text file into OE for the PC. The same process should work for PC to Mac.

TIP: Handling attachments

Bill Reynolds sent us this pair of tips about handling files attached to email messages.

Mac attachments on PCs

Keep messages with Mac attachments (especially Mac OS or application patches) in a folder INSIDE the Inbox...they will keep their resource fork (assuming your Exchange server supports Mac attachments to begin with)...waiting for you to download them from a Mac. (Don't wait too long: your Exchange admin may have a maximum-message-age policy, so you may lose your messages and attachments if you don't move them to Personal Folders and/or local or file server space.)

Save Mac attachments to Mac-supported server volumes (SFM on NT, for example)

If you try to open a Mac attachment and your PC sees it as a .BIN file, you need to patch your Registry so Outlook (not your PC, per se) recognizes the file as a Mac file (creator and type codes, etc.).

Recognizing attachments on your Mac

If Outlook doesn't recognize a particular file type, you need to use ResEdit to patch your Exchange Preferences file, so Outlook (not your Mac) can recognize the file (creator and type codes). If you save an attachment that Outlook doesn't recognize to your hard drive, you'll still need to use a utility to change that file's creator and type codes before you can open it. Even if your Mac normally can open that type of file, Outlook will have stripped out the creator and type codes, so your Mac will try to use the first application (alphabetically) it can find...usually Acrobat Reader.

September 27, 1999 -- Jon Burns says that some of his Macs hang when 8.2.x tries to forward an email attachment, or cut and paste from Word to Outlook. The strange thing is that connecing via AppleTalk clears up the problem:

I'm having the following problem: Only Mac client 8.1 will work "somewhat correctly". I have the usual lost profile and missing features.

When I install 8.2 or 8.2.1 on a Mac running 8.6, the following happens. When I try to forward an email with an attachment, the Mac hangs. When I cut and paste from Word to Outlook , the Mac hangs.

When I turn Outlook to connect via AppleTalk, it works fine.

The setup:

NT4 server, Exchange 5.5 Service Pack 2, NT4 server providing DHCP
About 50 Mac clients ranging from Umax S900's, Imac's, and Blue/white G3's.
All at system 8.1 - 8.6.
They are running Outlook Exchange version 8.1

Problem: When we upgrade the Mac's to Outlook 8.2.x the Mac's have the following problems. Although when AppleTalk is selected, the majority of these problems go away..

  1. Mac's hang/or may take an extrememly long time to send attachments.
  2. Mac's freeze when you double click on an attchment.
  3. Mac's freeze when you cut annd paste from Work98/Outlook.

    My Mac "7300/180" is running 8.6 and Outlook 8.2.1 and it works great.

Outlook 8.2 Type and Creator codes

Sue Mosher (Author of Teach Yourself Outlook 2000 Programming in 24 Hours Outlook and Exchange Solutions, and the Slapstick site) passed this tip along to us:

July 23, 1999
Nate Couch

Just downloaded the new Outlook 8.2 client for Macintosh and noted something which may help some.

The PAB file Creator /Type does change in this version from previous versions. In short, your old PAB file will not work until you change the Creator /Type information to the new info (use Resourcer or ResEdit to do this).

The new info is as follows:



July 23, 1999
John Wolf

You have a message from Nate Couch that the Type and Creator for Outlook 8.2 have changed... [He may have run into] the bug in Outlook (and Exchange) that occasionally trashes the file type on the file, and you have to manually change it back to _PAB to get it to be recognized.

It was particularly bad with Exchange 4.0. I have only seen it once since the switch to Outlook. I think it has to do with crashing on quit.

My personal address book, that I have had around since Exchange 4.0, is type "_PAB" and creator "MSES". So, he is correct, it has changed from "MSES" to "EXCH", but still, the old one is recognized.

If he had "????" in place of "_PAB" then he was suffering from the trashed file type bug.

Problems with Mac Outlook 8.2 extension files

August 5, 1999 -- Janluc Gagne reports problems with freezing and file corruptions with Outlook for Mac 8.2, but not when he reverts back to 8.1. He suspects some Microsoft extension files, including "MS Outlook OT Helper (PPC)" and the Microsoft OLE extensions that come with Outlook 8.2 -- the OLE extensions that come with Office 98 work fine for him. Gagne reports that Quark (which also uses OLE extensions) was freezing with the Outlook 8.2 extensions, but not with the Office 98 extensions:

The new features [of Outlook 8.2 for Mac] are great, but I had to revert back to version 8.1 because of constant freezes and corruption of the file system on my external HD. I have a B/W G3 running Mac OS 8.6... I keep non-Apple extensions to a minimum.

The extensions that (according to me) can be causing the problems are "MS Outlook OT Helper (PPC)" and the Microsoft OLE set of extensions. ...I had to uninstall 8.2, remove all OLE-related extensions, reinstall Office 98 (to get the good OLE extensions) and finally reinstall Outlook 8.1. I was getting hard freezes in Quark (which also needs Microsoft OLE extensions).

I use [Disk First Aid and Norton Disk Doctor] regularly, even when there are no problems (Disk First Aid for Mac OS Extended [HFS plus] format drives and NDD for Mac OS drives, since I do not have the latest version of NDD that supports Mac OS Extended). Also, whenever a new version of Apple Drive Setup comes out, I make sure to update the drivers on my HDs.

TIP: Getting the Macintosh Outlook (or Exchange) client to work. (Resolving the server IP address.)

August 12, 1999 -- Frequent contributor Richard Birchall sent us a tip on fixing a problem that prevents Outlook for Mac from working:

The client requires that the Mac be able to resolve the IP address of the Exchange server, by using the host name of the Exchange server.

A very common problem occurs when there is not a proper entry for the Exchange server in the company DNS server (or perhaps there is no DNS server at all).

The solution is to create a Hosts file on the Macintosh client computer.

You need to know the "IP address" of the Exchange server. If you do not know this, try running the PING command from a DOS window in Windows:

You should get a response like so (using my server, "mail02", as an example; substitute your server name):


C:\WINDOWS>ping mail02

Pinging [123.456.789.123] with 32 bytes of data:

  1. Make a Hosts file using SimpleText and save as "Hosts" into the System folder.
  2. Then go to TCP/IP Control Panel and select the file via the "Select Hosts File" button (may have to change the user level).

    The Hosts file is set up like this (one line):

    mail02 A 123.456.789.123

    This will resolve the name "mail02" to IP address 123.456.789.123

October 12, 2000 -- Stone Brooks expands on the above tip by adding some new details on configuring the Mac TCP/IP hosts file:

If you attempt to use the instructions given in the tip: TIP: Getting the Macintosh Outlook (or Exchange) client to work. (Resolving the server IP address.), and are getting an error message when the host file you created is selected. "Are you sure you want to use the host file? Line 1 has a bad domain name."

We discovered with TCP/IP version 2.0.1 the host name had to have a suffix ".com" or the domain name would not be valid. To work around this a conical name or alias is needed. Then point the alias to the IP address of the Exchange server.

The following lines were added to the host file:

More on hosts file configuring in Mac OS 9 for DNS to work with Exchange client

Mac OS 9 does let you select the hosts file, but not in Basic mode. You need to switch the TCP/IP control panel to Advanced or Administrator mode (command-k). You can then select a hosts file with the button in the upper right.

Simon Hingston adds:

Saving this file to the System folder will not solve the problem. With OS9 this must be saved as text called 'hosts' to the Preferences folder.

Outlook for Mac does not support Chinese, Swedish Characters

A reader with Exchange Server 5.5 w/SP2 has a problem with Chinese and Roman characters. When he sends a message from a PC with Chinese characters, PC's can receive them, but Macs show other characters. Changing the font to Taipei does not result in readable Chinese email.

One of our Microsoft contacts responded to our report Friday of a problem with Outlook for Macintosh receiving messages in Chinese from Windows users:

Outlook for Macintosh does not support Chinese. The current version, 8.2.1, supports four languages: English, Japanese, German, and French. If a user attempts to install Outlook on a Chinese OS, the install will fail. Even if a user attempts to run Chinese on a English OS (either through a language pack or by installing Chinese fonts on the system), Outlook will not be able to display the Chinese characters correctly, because Outlook does not support Chinese code pages.

Outlook 97, 98, and 2000, on the other hand, support Chinese on Windows, and therefore messages with Chinese characters will appear as intended.

Markus Norsted of Sweden noted that when he upgraded Outlook client for Macintosh to v8.2.1, he could no longer view Swedish characters in the messages he recieved:

I just want to add a question/comment regarding the character translation/display in Outlook 8.2.1. Before I upgraded to 8.2.1 I had no problems to view Swedish characters (i.e. ƒ÷) in the messages I received. But that's all changed in the new version....It's very annoying to have garbled characters in my messages, that's for sure.

Can't send messages when personal folders exist: font conflicts

Reader Joseph Re wrote to say that he gets periodically gets an error message with Outlook for Mac 8.2.1 when he tries to send a message. It only seems to happen when he creates Personal folders. The problem turned out to be font conflicts (see below).

The problem:

I recently installed Outlook 8.21 for Exchange Server 5.5 on my PPC 8600/200. OS 8.6, 256 RAM, No Virtual Memory, Asante 10/100 Ethernet (3.1), TCP/IP via DHCP...(all our Mac's here are still on 8.1 until results are in on 8.2.).

The problem is that, when I create a Personal Folder File and create multiple subfolders therein, after a few emails I get a message "The action could not be completed, you do not have enough memory or system resources..." (when I try to reply or send new email) which is completely untrue. It was actually working up until a day ago when my machine crashed in Quark (email was NOT open). I tried reinstalling (over the original) and this was no good. I then deleted all related files and did a "fresh" install of 8.2. It then seemed to work, at least until I set up Personal folders again, then I got the same error. I ran Inbox Repair Tool on the PF file and it came up with no errors. If I delete the Exchange prefs file, everything works again, but my Inbox Assistant and Out Of Office Assistant are no longer in the Tools menu.

I do have Outlook 98 on an NT machine as well, and I was trying to set up alternate Inbox Assist. rules there. Would that have caused a corruption of some kind on the server side?

I've bumped the memory to double what it was, removed/reinstalled Outlook, removed ALL OLE and Office related files, reinstalled Office, ran Norton Utilities/Speed Disk. What I haven't done is try to downgrade back to Outlook 8.1 and see if that fixes the fact that I can't send, reply or read emails (unless I toss the Exchange prefs out, then I can do all that but lose a bunch of menu commands including Inbox and Out of Office assistants).

I do have QXP 4.04, and I know that uses the same OLE files as Office and Photoshop 5. This all started when I crashed hard in Xpress.

The Solution:

I'm now back on Outlook 8.21 and it works very well. It turns out that there were font files that I had loaded into ATM Deluxe whose ID's were conflicting. Even though none of these fonts were being used by Outlook, Outlook still gave me the error "Can not display items, you do not have enough resources...etc." As soon as I open ATMD and resolved the ID conflicts, the problem went away.

Re's troubleshooting method:

Removed all OLE files (Extensions), Outlook 8.2 and prefs, and then downgraded to Outlook 8.1. I also turned off non-Apple extensions except for Asante 10/100 cdev and init and MacIPX inits. Then I (rebooted) tried Outlook 8.1 before launching Office (so no new OLE files were installed), and it worked. So I then launched Excel and it reinstalled all necessary files (rebooted), launched Outlook again and it still worked. So, I turned all inits back on (rebooted) and the problem reappeared. So, now realizing that this was not related to Outlook 8.2, I took a stab in the dark and disabled ATM Deluxe 4.03 and ATM Font Database in the System folder (rebooted) and Outlook worked again.

Calendar File Corruption with Outlook 8.2.x.

September 3, 1999 -- Frequent contributor John Wolf has rethought his opinion of the recent Outlook for Mac clients:

OK, so I thought Outlook 8.2 was wonderful. I take it all back. Outlook 8.2 (and 8.2.1) has been relegated to the trash can.

It eats shared calendars for lunch, it has more pauses than a first grade reader, and I suspect it of making network volumes disappear off the desktop. All in all, a ripe piece of software.

9.9.99 -- Jake Mowrer reported having the Outlook 8.2.1 schedule corruption problem. Additionally, Mowrer found that some Mac clients can no longer synchronize their schedules with the server even after he deleted the schedule file. Fortunately, he found a solution to the later problem:

I recently upgraded about 50+ Mac's to Outlook 8.2.1 and noticed that I am having schedule corruption as indicated by John Wolf on your site.

[Another] problem is, some clients who experience the corruption can no longer synchronize their schedules with the server, even if I delete the schedule file on their Mac. Almost as if the Exchange Information Store's copy of the schedule has become corrupt. I called Microsoft and that they said the only was to fix that is to delete their mailbox. I did that for the first 2 but I wanted to look for another solution...

G3 Tower Mac running 8.6/Outlook 8.2.1 communicating via IP to NT server running Exchange 5.5 SP2

The schedule would become corrupt, after recovering, got a message saying "This file has previously been synch'd with another schedule, do you wish to continue?". When you click "Yes", it says "Synch could not be completed. Unknown error occurred, try again later. A messaging service provided an error." At this point, I tried to create a new schedule file, still will not synch with the same errors.

[Microsoft KnowledgeBase] article Q168133 Deleting the Schedule+ Data from Exchange Server provided a solution:

  1. Start Outlook
  2. Place mouse pointer over the calendar icon, click and hold the mouse button.
  3. On the keyboard, press and hold the CTRL and SHIFT keys.
  4. Release the mouse button.
  5. Click Yes on the message asking if you are sure you want to clear the schedule data.

After this, I imported the old schedule file and it synch'd fine and corrected my problem.

September 27, 1999 --
Hal Taylor

I work at fairly large company (whose name I'd prefer to keep quiet) in a predominately Windows environment. We were initially pleased with Outlook 8.2 and it's small step toward a reasonable Mac Outlook client.

However, as soon as we started rolling it out to users, we began receiving reports of corrupted schedules. This seemed to be happening in cases were schedules had been assigned to delegate owners (it may be just that those schedules are the most heavily used). We immediately withdrew Outlook 8.2 from our environment, and moved all users back to 8.1. We have since been testing 8.2.1 on our own machines. We have seen corruption on 3 out of the 4 people testing, but have been unable to systematically reproduce it.

I'd be interested in seeing how many others out there have experienced similar problems. We had a ticket open with Microsoft, but our Microsoft support closed it because he could not recreate the problem. We've sent him some more information, hoping that he'll reopen the ticket, but it seems that they do not believe there is a schedule corruption issue with 8.2.

January 18, 2000
Lisa Toplansky

I'm writing regarding the Calendar file corruption for Outlook 8.2 and 8.2.1. This has happened to many Mac users at our site. Seems to be related to granting other users (particularly PC users) access to their calendar. The schedule+ calendar eventually becomes corrupt and produces and error:
ERROR: "Your local schedule was previously synchronized with a different shared schedule. Do you want to change the local schedule to synchronize with the current shared schedule"

The problem is hard to reproduce.

(Scroll above for more on this issue.)

Outlook 8.2 Type 3, Type 2, Type 1 errors

(For more on crashing, see Outlook for Mac and ATM Deluxe conflict: crashing above.)

September 12, 1999 -- J erome Skrdla reports getting Type 3 errors with Outlook 8.2 for Macintosh:

We are having a problem with Outlook 8.2 on new iMacs running os 8.6. After completing setup, and then closing out, the next time we try to open Outlook we get a type 3 error. This has not been consistant on every machine although 7 of 10 computers experienced the problem.

September 14, 1999 -- Mark Caldeira reported a problem that sounds similar to problem with Outlook for Mac, but with some differences:

We ran into a similar problem installing Outlook 8.2.1 on a few of our desktop G3 266 running MacOS 8.0. On 3 out of 5 machines, after authenticating the user with the exchange server using outlook settings, Outlook would crash on launch, giving either a type 1 or 2 error. We are still in the process of troubleshooting what exactly is going on.

Solution (September 15):

I just wanted you to give you an update: we seem to have solved our problem by reinstalling the Internet Config extension (we are using version 1.4 on our MacOS 8.0 machines), and deleting the Internet preferences file.

September 22, 1999 (updated Sept. 23) -- Jeff Lucia offers another solution to the problem:

Type 3 errors, I have only seen a couple of times. I have 20 G3s 450's running 8.6 and 5 PowerCenter Pro's w 8.51 running pretty well. However, I did have Outlook screw up an upgrade once and cause the Type 3's when trying to log on the next time. Outlook installs preference / required files in the System Folder in the "Exchange Files" folder (Not Exchange Temporary Items) in the Preferences folder in the System Folder. This folder and all additional preference folders (and extensions) must be thrown before reinstalling Outlook 8.2. Once I removed everything my install worked fine. The bad part is that you will need to reconfigure Outlook completely for that user.

The "Exchange Files" folder is required for Outlook to run, which is why if it gets corrupted sometimes crashes with Type 3's. Trashing this folder, AND the other Exchange items in the Preferences folder before reinstalling Outlook should help the Type 3 errors.

Also, don't forget to save the Personal Address book and Personal Storage Files (.pab, .pst).

September 28, 1999 -- Terry Knudtson also reported a Type 3 error with Outlook. He found that the problems disappeared when he switched to AppleTalk:

I'm a tech at the Edmonton Public School Board. I ran into that same [Type 3 error] problem a few months ago on a Blue and White G3 with Outlook 8.2 installed.This was on OS 8.5.1.

The only work around that I found was to switch Outlook to communicate viaAppleTalk instead of TCP/IP. Unfortunately, this won't work if you are on a routed network and the Exchange server isn't in the same domain as you are.

Outlook 8.2.1 crashing traced to font conflicts, Suitcase 8.x.

December 2, 1999 -- Jeff Churchwell has traced a crashing problem of the Outlook 8.2.1 client to conflicts with fonts.

Concerning Outlook client 8.2.1 crashing: I have experienced this problem, and can point to fonts, not networking configurations, as the problem. My users all have Suitcase 8.x from Extensis, and without fail, if they had certain fonts loaded in Suitcase prior to launching Outlook 8.2.1, the whole Macintosh would freeze.

Sadly, I can't say with certainty that anyone else would have problems with the SAME fonts that we use here. Further, it's not every typeface in a given font family, but only certain typefaces within a suitcase that give the problem (these typefaces will also cause the Mac to freeze up if reviewed individually within Suitcase... select a suitcase in the main Suitcase window and click the "View" button, then click on the individual typefaces, and wait for the freeze as you move from face to face). Type families with this error that I have have encountered so far include Avant Garde, Caslon and Goudy. Removing the suspect typefaces, or suitcases in which they are contained, eliminates the Outlook freeze.

My conclusion is that there are certain older Mac font resource types that are incompatible with Outlook, as well as Suitcase 8.x.

(For more on Outlook crashing on the Mac, see problems with ATM Deluxe and Type 3 errors, above. We've also had other reports of font conflicts, also above.)

Outlook text insertion bar disappears

First, a few reports of the problem, followed by several suggested workarounds.

October 26, 1999 --
Mary Halligan

I was wondering if anyone else reported the bizarre problem that I just started having with Microsoft Outlook, Exchange Server Edition Version 8.2.1. I noticed this very odd and annoying problem just a few days ago.

The flashing vertical line that tells me where my cursor is, has disappeared. I actually have the pointer and cursor, but as soon as I click on something, the flashing line that shows you where you are on the document, does not appear.

I thought that I had fixed the error, when I ran Disk First Aid. It reported "MountCheck found serious errors". I repaired that error, and everything seemed O.K.. The problem had disappeared (temporarily). Then my computer froze up, and the error came back upon restart.

I have tried running Disk First Aid, Techtool (rebuilt my desktop), and ran Techtool Pro. No detected errors. This problem does not occur with any other software, including Netscape mail. I am running OS 8.5.1 on a blue and white G3.

The problem came and went for several days. I finally got tired of it, and I reinstalled Outlook on Friday. Today, the problem returned. At this point, I am frustrated and stumped.

October 28, 1999
Jeremy West

Just wanted to let you know that our Macs are having the same problem with not being able to see the text blinking cursor when composing a new e-mail in Outlook for Exchange Server 8.2.1. It's very annoying and everyone has the problem. We were going to switch over to Outlook express 5 as soon as we can export our global address book for the company, since we can't use Outlook's calendaring functions with other PC users anyway. Express works fine and everyone likes the interface a lot better.


October 29, 1999
Mark Caldeira

Just wanted to let you know that I've had the disappearing cursor with Outlook 8.2.1 on a blue G3 running MacOS 8.6. So far it has occurred on only one machine out of 5 that are the same configuration. The strange workaround I have discovered is to go to Tools>Options...>Spelling tab and toggle "Always suggest replacements for misspelled words". I uncheck the option, recheck it, and close out of options, and I have the cursor back.

This problem has come up twice so far on that single user's machine, and that is the workaround I used to resolve it.

October 29, 1999
Paul Dormer

We found the problem to be ATI graphics. Disabling on some 9600's here cured it, but obviously the screen redraw is slower for everything else.

November 2, 1999
Jeremy West

Just an update for you- Last week I reported the disappearing text icon from Outlook and two different workarounds were posted involving toggling the spelling options and disabling ATI extensions. I tried the spelling option and it had no effect (I had no ATI extensions in the system) , but I disabled the 9600 graphics accelerator extension, and the icon returned.

October 4, 2000
Nelson Pereira sent in another fix. He tried the above solutions without success. His workaround:

Go to Outlook Setting in Control Panel. Remove Profile. Create a new one. Now Add Exchange server first then later come back to add personal address and personal folder. Just to do some testing before you add Personal Address and Personal folder. Then log on email.

The cursor appears. Then you you can go back add your addresses and folders.

I believe there could be a problem in Option setting that might cause cursor disappear or under menu view, though I haven't tried i. I thought it would be simpler to remove profile and create it again. It worked!

(Outlook 8.2.1, Mac OS 8.6, PowerMac Blue & White G3/400)

Network problem with Power Mac G4s

Just received two G4s, installed MacOS 8.6 on them, and Office 98, and then attempted to install Outlook for Exchange Server 8.2 on them. The HOSTS file has been created and Outlook was tested to have worked under OS 8.5 on the G3s before we replaced them with G4s. The problem now is that Outlook cannot find the server, it just sits there with the message that there may be network problems, when other G3s on the network can access the Exchange Server w/o problems. Then there's the Finder crash, followed by a slowing down of the system, an inability to shutdown so a cold reset is necessary. The latter symptoms I've found other people suffering though but I haven't found a solution yet.

Khang Than-Trong

Disappearing address information

November 4, 1999
David Pearson reports of a problem with Outlook 8.2.1 for Macintosh for Exchange:

I've just discovered that if I call up an entry in the address book that goes with my Microsoft Outlook and add any new information, that the program wipes out the e-mail address.

So, if I learn some new information I want to add to an address file, I have to reenter all the information under a new heading, and delete the old one.

There has to be a way to fix this glitch. It is going to take me hours of work to go back into all these address files, to which I've been blissfully adding information for several weeks now, and reenter all this data.

TIP: Moving personal address book entries from Mac to Windows

Thanks to Keith Billy for sharing this tip for moving the entries in the Exchange/Outlook personal address book on a Macintosh to the personal address book on a PC:

In the Exchange/Outlook profile set the mail delivery point to the Exchange server, not to a personal folder. On the Mac, start a new mail message and add all of the entries from your personal address book to the TO: or CC: area.

Close and save the message without sending it. The message should show up in the inbox. Close Exchange/Outlook on the Mac and open it on the PC. Open the saved message. When you right click on each of the names you will have the option to save them to the personal address book on the PC.

TIP: Using Palm Pilot to convert Outlook Win to Mac Schedule Plus

January 27, 2000 -- Matthew Smith found a way to convert contacts and schedule items in Outlook for Windows for Exchange Server to Schedule Plus for Mac. He uses DataViz's Desktop to Go software to move the data to a Palm Pilot.

I have an Exchange server with a number of users (including myself). I had been having some trouble converting Outlook 97/98/2000 contacts and schedule items into Schedule Plus (which is what the Mac uses) until I got a Palm Pilot. When I got the Palm Pilot and DataViz's Desktop to Go software, I synchronized all my items within the outlook schedule and items. Then I changed the settings on the DataViz product so that it would synchronize with Schedule Plus! I must say, this is a nice feature of the product, and it is a 15-day free trial...Now, all my data has been successfully copied to Schedule Plus and I have all the same info on my Mac as I do on my PC.

Now, if somebody would only come out with a software to synchronize the Mac version of Outlook with a Palm Pilot. I called 3 companies that offer products that hotsync with the PC version of Outlook, but none of them (including DataViz, a company with lots of Mac software) are even planning a Mac version. I do know that there is a way to sync with Macintosh Outlook Express 5 on a Palm Pilot, and I know that Outlook Express 5 can get info from an Exchange server, so I will be working on this.

Macs can't log on, Outlook quits

March 14, 2000 -- Reader Jeremy West is having a problem with Outlook Mac clients and Exchange Server. The Macs can't log on and Outlooks quits:

We have about a dozen Macs on a large NT network and we have been able to access the NT Exchange Server via TCP/IP through Outlook fine until today. When we launch Outlook and supply our domain information and password, we get an error stating "The set of folders could not be opened. The MS Exchange server computer is not available. Either there are network problems or the MS Exchange Server is down for maintenance."

The only option we have is OK and then the program quits. When we set up a new profile in the Outlook settings, we are able to verify the NT server and the mailbox name when we click on Check Name, but the program still gives the connection error when we start Outlook. I can access the NT server through Dave, so I know that the connections are good. I can also access all of the NT servers that are running Mac shares through Apple share in the Chooser. We can go into Netscape communicator and set up the e-mail portion to log into our SMTP and POP server and we can get our mail that way, but we really need to do this through Outlook.

By the way, ALL of the Macs had this problem happen today. The PCs can all connect fine. Nothing new changed on our network recently and no new software was installed on the server. We are at a loss as to how to correct the problem.

We are using Outlook 8.2.1 for Mac and Exchange Server 5.5 on an NT running the latest service pack.

March 15, 2000 -- Several readers offered suggested solutions to this problem. Marcus Reese thought the Mac TCP/IP isn't resolving the Host File DNS entry. Matthew Smith also suspected an improper IP address for the name of the server, and had some different suggestions. Jeff Lucia reports having had a similar problem that was caused by multiple profiles.

Marcus Reese:

I have a few suggestions for Jeremy West to try. It sounds like his TCP/IP is not resolving the DNS entry in his Hosts File. I would trash one of his Macs TCP/IP prefs file (writing down it's info first) and Hosts file. I would then reset up the TCP/IP Control Panel and reselect the new Hosts Files.

Matthew Smith:

In response to the problem being experienced by Jeremy West, I would recommend the following.

1. If the server with Exchange server running on it has NT SFM running on it, have them connect via AppleTalk instead of TCP/IP.

2. If this is not an option, have them go into the hosts file that sits inside their system folder's preferences folder and add an entry with the proper IP address for the name of the server. If unfamiliar with the process of doing this, open up the file called "Sample Hosts" (in the preferences folder I believe) and look at the document. It will give instructions, and when changes are made, save the modified document as "Hosts" in the preferences folder. Don't confuse this with the LMHOSTS file that DAVE uses. They are different.

3. If nothing is working, consider Outlook Web Access as a temporary solution to the problem. It offers many of the same features the full client offers. The NT administrator should be able to set it up, if it is not already set up. One thing to note is that you must grant any users of Outlook Web Access access rights to log on at the server terminal for it to work correctly. This could be viewed as a security problem for those whose server terminals are not in a secure location. You can find documentation on this feature and setting it up on Microsoft's website. Another note: you need to have MS IIS 4.0 (available with NT 4.0 option pack) in order to install Outlook Web Access.

Those are my recommendations based on my experience. Feel free to edit this liberally if you post it. In addition, feel free to give Jeremy my email address. I'll offer as much help as I can.

Jeff Lucia:

I just had an issue identical to what Mr. West is encountering. However,I'm not sure this is going to help him to much though because he didn't mention multiple profiles. Essentially, my setup had problems because I had two user profiles on the same machine (2 users share the machine). When I did a clean install of the OS, and reinstalled Outlook I received the same error message Mr. West did whenever I tried to log the second user on. This is because Outlook refers to the original profile that was created as it's "default". It was actually trying to log the second user on with the first users profile.

The solution is to log in as the original user, go the the user properties, and force Outlook to prompt the user to choose the desired profile on startup. Once that was set, both users could log on correctly.

March 16, 2000
Jean-Paul Boucher

I have several hundred Macintosh clients connecting to Exchange 5.5 SP3 servers. The problem that Jeremy West is having sounds like a DNS issue. The Outlook Client for Macintosh resolves the name of the Exchange server through its CNAME (when using the TCP/IP connection, not the AppleTalk connection). Someone may have altered the DNS records for his Exchange servers.

March 21, 2000
Mike Menne

Here's what I've found to be the case whenever I use TCP/IP on the Mac with Outlook or Exchange.

In the TCP/IP control panel, the Domain Name MUST be entered in the search order. Without it, Outlook will resolve an IP address or full domain name (eg into just the server's name (eg exchserver). If the search order is set, them Mac TCP/IP stack will automatically add the domain name to the server name when looking for the Exchange server (eg. adding to exchserver resulting in

March 21, 2000
S.Celeste Blackwell

I had the same problem, similar Network Setup - Turned out the Exchange Server was not listed on our network's name server, once it was added to the list, everything worked properly.

April 5, 2000. Jeremy West's solution.

West seems to have solved his problem more simply: by restarting all of the Microsoft Exchange services. We thank everyone for their suggestions, which should prove helpful for other readers.

Locked out of Outlook client

March 22, 2000 -- Murray J. Miskelly was doing fine with Mac Outlook 8.2.1 for Exhange Server until another problem forced him to reboot from a frozen screen:

I am running Outlook 8.2.1 on a G4 with Exchange server 5.5 on NT. I have been using TCP/IP without a hosts file, but with full Domain Name in the search order. This has been working fine for a number of months.

The problem originated when another program froze on the Mac and I had to perform a forced reboot. Now when I try to log in to Outlook it gets past requesting my password and then presents me a dialogue box stating "The set of folders could not be opened. The information store could not be opened", with an 'OK' button as the only option. This quits the program.

If I cancel the password dialogue box and try to work offline I get the same message. I have reinstalled Outlook, and run a repair check on the PST file (all clear), but the problem persists.


March 22, 2000 -- Murray Miskelly found the solution:

Using the Outlook setup application I eventually set up a new profile duplicating my original settings. This has worked implying that my old profile was corrupted. I therefore assume that profile information is kept 'protected' when reinstalling components of Outlook and system software.

Sent Items messages disappear

March 23, 2000 -- Dan Foshee noticed that just recently that his Sent Items were no longer visible from any Mac Outlook client on Exchange Server. Yet, he can see the Sent Items messages on an account set up on a Windows PC. Foshee suspects an undocumented "feature," but hasn't been able to find it:

It all started when our e-mail group moved my account to another server. Since then, we've moved the account back to the original server, but the problem remains.

The solution:

April 11, 2000
Dan Foshee

I found out why my Sent Items disappeared, but not the why behind the why.

Turns out that a Synchronize filter on my Views properties for that folder view was turned on and left on; what it was synchronizing to, I have no idea. The e-mail administrators denied changing any settings, though I'm thinking it would have to have been changed at the server level; if it were on the client side, wouldn't a clean install of the client software have reset the view?

Anyway, when we created a new folder view (control click on the Sent Items folder, then Properties, then Views tab) we were able to turn the Synchronize filter off, then modify the 'current view' to turn the filter off as well (not really necessary, but it eased my mind).

Windows 2000 and Exchange Server/Outlook: Macs don't get notification of new e-mail

March 28, 2000 -- Khang Than-Trong of a problem with using Windows 2000 NAT as an Internet gateway. His problem is with Outlook for Exchange Server for Macs, which aren't receiving notification of new mail. He says:

We recently went to a Windows 2000 Server to share the DSL connection for the office, and act as the gateway. As a result, all of the workstations internally have arbitrary 'internal' IP addresses (non-live on the Internet, i.e.. 192.168.0.x).

The Exchange, Web, SQL servers have 'real' live-to-the-Internet IP addresses. Windows Outlook 2000 users can receive new mail notification (i.e., the new mail appears in their inbox) automatically while the Macintosh clients cannot--they have to switch folders (which causes the client to go out to the server) or manually press command-M to 'deliver' the new email (it doesn't work if you've pressed it in the last 2 minutes).

Digging through Usenet archives and Microsoft knowledge base has led me to something about UDP packets (that are used for the notification) not being passed properly through the aforementioned Windows 2000 NAT (network address translation) box. But how come it is business as usual for the PCs?

Suggested solution

March 28, 2000 -- Luis Antezana has solved the problem by allocated more memory to the Outlook client:

I see the problem described by Khang Than-Trong from time to time. In my experience it always has to do with a low memory situation. I have seen this on OS 8.6 and Exchange Server 5.5, with Outlook 8.2.1 s the Mac client. The solution is to either Quit and relaunch Outlook, restart your whole computer, or allocate more RAM to Outlook. The problem may happen when the whole computer has very little RAM left for any application. Either way it seems to be a RAM issue. With VM off I have found the problem to exist with an allocation of 18000k, and to mostly disappear with an allocation of 21000k-23000k. How lame is it when just your e-mail program takes 23000k?!

Problem moving contacts from Outlook 2000 to Outlook 8.22

May 8, 2000 -- Matthew Smith reports that of a problem moving contacts from Outlook 2000 into Outlook 8.22 for Mac:

I exported contacts from Outlook 2000 (for PC) into Comma Separated Values (text). When importing them into Outlook 8.22, I am able to select the fields I want, but when it goes to import, Outlook unexpectedly quits (error of type 2). Has anybody else experienced this? It seems to happen with 8.21 as well.

May 10, 2000
Luis Antezana

I have seen this problem in Outlook 8.2.1 - I don't remember if it actually caused a crash, but I do know it won't import directly. When I migrate someone from PC Outlook, I have to do a considerable amount of editing of the exported text file in Excel and Word before I can bring it into Outlook for Mac. There are some kinks in the way that the two Outlooks present their data: there are more data fields in PC Outlook, the same data fields may not be represented by the same field names, proper placement of quotation marks around data is important, and spaces before or after field data also matters. Importing the text file into Excel can modify the data as well, altering some of the aforementioned formatting. You have to be careful and methodical with your fixes. With a lot of trial and error you can make it work. Then make sure you write down what actually worked so you can repeat the procedure!

May 17, 2000 --
Rolf Lohr sent in another method of moving contacts from Outlook 2000 to Outlook for Mac for Exchange server.

I got the same problem and I solved it somehow. The contact import function was not correctly working.

This is how I got it to work. The MS format .csv is different from almost every application (Excel is different then Outlook)

I did one example record and exported the record first as contact.csv. The import function is requiring a header line. Then I put all my contact record in the same format like the previously exported format. Now I imported it again and this worked.

IE 5 removes newer Outlook 8.2.2 library files

May 9, 2000 -- Several readers reported that after installing the new Outlook/Exchange 8.2.2 for Macintosh, launching Internet Explorer 5 will run the Internet First Run utility. This reinstalls the older Microsoft extension files--removing the files Outlook just installed. Readers have reported this occurring with Internet Explorer 5 and Word 98. Both readers also said that this process removes bug fixes in Outlook 8.2.2.

However, Microsoft responed to say that IE and Word don't remove any bug fixes.

One of the readers was Bruce Bowden:

After installing Outlook 8.2.2, the next time I ran Internet Explorer 5, it launched Internet First Run and installed a number of system files, presumably replacing the ones that Outlook had just installed. Running Word triggered another sequence of messages that it was configuring various components.

As a result of all this activity the major fix I had hoped for - the system lockup when a new message arrives - doesn't work. Presumably I could gain the benefits of the new version provided I didn't run any other Microsoft products.

May 11, 2000
Bruce Bowden

One more bit of info. I checked the contents of the 'MS library folder'. After installing Outlook 8.2.2 these files were present:

File name



mod date

Explorer Library (PPC) v1.2



Wednesday, 20 January 1999 12:00:00

Microsoft VM Library (PPC)



Thursday, 26 March 1998 00:00:00

MS C Library (PPC)



Monday, 23 June 1997 12:00:00

MS C++ Library (PPC)



Wednesday, 20 January 1999 12:00:00

MS Configuration Lib PPC



Thursday, 25 December 1997 00:00:00

MS Container Lib (PPC)



Thursday, 25 December 1997 00:00:00

MS Favorites Library (PPC)



Thursday, 25 December 1997 00:00:00

MS Import Lib PPC



Wednesday, 20 January 1999 12:00:00

MS Internet Library (PPC)



Thursday, 25 December 1997 00:00:00

MS JScript (PPC)



Thursday, 25 December 1997 00:00:00

MS Parser Library (PPC)



Wednesday, 20 January 1999 12:00:00

MS Preferences Library PPC



Thursday, 30 April 1998 09:31:44

MS Variant Lib (PPC)



Thursday, 25 December 1997 00:00:00

After running IE5 the folder had changed to:

File name



mod date

Explorer Library (PPC) v1.2



Wednesday, 20 January 1999 12:00:00

Microsoft VM Library (PPC)



Thursday, 26 March 1998 00:00:00

MS C Library (PPC)



Monday, 23 June 1997 12:00:00

MS C++ Library (PPC)



Wednesday, 20 January 1999 12:00:00

MS Import Lib PPC



Wednesday, 20 January 1999 12:00:00

MS Parser Library (PPC)



Wednesday, 20 January 1999 12:00:00

and the remaining files were in the Trash.

I copied the files back into the 'MS library folder' and ran IE5 again.

This time it asked permission to install files and gave me the chance to cancel the launch. (Maybe because Outlook was also running at the time)

Last trial - I changed the mod dates on all the rejected libraries to today's date and copied them into the MS library folder. IE5 once again rejected them and spat them into the trash.

Microsoft response:

A Microsoft source has responded to our report of Internet Explorer 5 replacing files installed by Outlook 8.2.2. Our source, who wishes to remain anonymous, explains the issue this way:

Regarding the issues with Outlook 8.2.2 and Internet Explorer 5:

After installing Outlook 8.2.2, IE 5 runs first run setup again. This is expected and correct. Outlook 8.2 actually installs older IE components, which IE then updates when it runs next time.

Contrary to information published on your site, IE 5 does not overwrite any components which have been patched by Outlook 8.2.2. All bug fixes in version 8.2.2 are in the file "Microsoft Outlook", which IE does not touch.

So, in summary:

We have since spoken with other Microsoft officials who have confirmed this.

TIP: too little RAM blocks Global Address List access

June 16, 2000
Kurt Dikkers

Our [Outlook for] Macintosh users have recently found that they lost access to Global Address List. The cause was that the Global Address List was added to due to a reorganization and greatly increased in size. Unless the memory allocated to Outlook had been increased from the default value, Outlook could not store the Global Address List locally in RAM and therefore could not show it. Raising the memory allocation by several megabytes, brought back the displaying of the Global Address List. Of course Outlook gave no indication of a memory problem like a well-behaved application should. Now if there was a way to rapidly scroll through our exceptionally large Global Address List, life would be great.

TIP: Moving Contacts from Outlook 2000 to Outlook 8.2.2

Shane Palmer told us about a useful help file with guidelines on importing addresses into Outlook 8.2.2 (Mac) for Exchange Server:

If you select Import from the File menu then click the Help button on the following screen you will get a very helpful set of guidelines to follow when creating a CSV file to import. I tried a small test of 5 contacts and I exported just the Email Display Name and the Email address from Outlook 2000. I copied the resulting file to my Mac and opened it in Word 98, changed the field names according to the Help file, and saved it as a text only document.

Listed below are the exact steps that I followed to move my contacts from PC Outlook 2000 to Mac Outlook 8.2.2.

  1. In Outlook 2000 on your PC select File-->Import and Export.
  2. Select Export to a file and click Next.
  3. Select Comma Separated Values (Windows) and click Next.
  4. Select the Contacts folder and click Next.
  5. Select a location to save your CSV file and click Next.
  6. Click the Map Custom Fields button, click the Clear Map button and drag any fields that you want to Export from the left-hand column to the right-hand column. You may want to check the Outlook 8.2.2 Help File to make sure Outlook 8.2.2 has equivalent fields for what you are selecting. When completed click OK, then click Finish.
  7. Copy the CSV file you created to your Mac.
  8. Open the CSV file in Word 98 on your Mac and rename any fields as necessary according to the Outlook 8.2.2 Help File. Even if you don't need to change the field names you will still want to open and resave the file in Word 98 to get rid of any Windows carriage returns/line breaks. If you open the file in something other than Word 98 you may see these Windows carriage returns/line breaks as unusable garbage characters. Just delete these and you should be fine.
  9. Select File-->Save As, and make sure Text Only is the file type selected to Save as. Name the file if necessary and click Save.
  10. Open Outlook 8.2.2 and select File-->Import and click OK.
  11. Select the file you just saved in Word and click Open. You will see progress indicator showing the import status. Once this is done open your Personal Address Book to verify the addresses that you imported.

For more information, see the Help file mentioned above.

Outlook won't launch, can't find Exchange Server

July 6, 2000 -- Jeremy West has a reoccurring problem with Macs running Outlook Client 8.2.1 and 8.2.2, Exchange Server 5.5 SP3 and Windows NT SP5. When Macs try to open Outlook, they get an error message:

The set of folders could not be opened. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.

West says the Mac clients can access POP from the Netscape browser e-mail function:

It affects all the Macs on the LAN, and the problem will not resolve until the NT server gets restarted. Our first problem occurred several months ago, and it would reappear every couple of weeks. In this last week, it has happened almost every day. The Mac clients can POP in with Netscape's e-mail features, so we know the account is OK, but when we try to open Outlook, we get the error message.

July 7
William Hoyt

I have received that exact error message, and every time it is due to server trouble and isn't limited to the Mac clients.

Running MacOS 9.04 in a Win2000/NT4.0/Exchange 5.5 environment without DAVE or any other special software.

July 11 Jeremy West provides more details of the problem:

Just an update to those trying to help with my Outlook/Exchange problem. We are running TCP/IP on a DHCP network with DNS. Another wrinkle is that the Mac users can access their Outlook accounts by connecting to the Web Access version. This gets us in to Outlook over the web, but we cannot use the Global address book or Public Folders. We can do e-mail resolution by typing in the recipient name and having the Web Access version of Outlook resolve it, but it is far from fully usable. Just want you to know that we are able to get in other ways besides POP. Also, the users can get into their mailboxes fine with a PC.

Possible workarounds:

July 7
Aimee H. Shaw

We saw a similar problem here on our Macs a few months ago - it affected only the Mac clients. We could log on to the Mac email accounts on a PC, but not the Mac stations. It was a permissions issue that somehow got corrupted when account info was moved around on the Exchange Server. Our solution was that an IT person with administrative rights logged into their personal Outlook account on each Mac; quit the application--re-entered the MAC client info in the Outlook Settings CP; and relaunched using the client info. We're not sure why it was necessary to do this, but it worked and we haven't had any problems since.

July 7
David Pearson

Try using a host file with the IP address and the name of the Exchange server on the PCs having problems. If you can ping the server from the PC this should help.

July 10
Ed Hagihara

It wasn't stated if Jeremy was using AppleTalk or TCP/IP to access the Exchange Server. Here are a couple of things off the top of my head to look at:

1) Too many fonts active. Since the problem goes away when he restarts the server, and since it seems to affect all Macs, this is probably NOT the case. I have seen Exchange/Outlook do some really funky things because of fonts, however. Seemingly unrelated things like: not being able to access the Exchange Server, the client shuts down quietly after entering the password, and unable to open messages because it has "there is too much text in the message". Really weird.

2) If you're accessing the server through AppleTalk, try TCP/IP, unless you're not running a DNS server capable of doing name resolution, or, you can create a hosts file that points to the exchange server. Since he can resolve the server through POP3, they're probably running DNS.

A fix that sounds promising

July 11
Greg Shaw

Outlook problems are a semi-regular part of life around here. Losing track of the Exchange Server or the personal address book are the most common problems. Both can be solved by opening the Outlook Settings app, deleting either the Exchange Server or address book, then creating a new entry with the same settings. After recreating the Exchange Server be sure and do a check name, using a different username/password than the one just setup,before closing the settings app.

Evidence pointing to the server

July 17
Jeremy West

Here's an update on the Macs that can't access Exchange. In the past, if we restarted the Exchange server, it resolved our problem. Last week, we restarted the server several times, but it did not fix the problem. We then noticed that our engineers were running some performance monitors on the server, and when we stopped the monitors and restarted again, the Macs could now get on to Exchange. Our engineers seem to think it is an RPC problem with the server and are working directly with Microsoft to figure this out. I will keep you updated as always, and thanks to all those who have sent in advice. I have tried them all, but it looks like this one is definitely a server issue.

Similar problem, somewhat different workaround

January 26, 2001
John Parnaby

We're running Exchange 5.5 SP2 on NT 4 SP 6a and have generally had a stable setup - then all of a sudden over the past two days users have had random trouble logging in to get e-mail [MS Outlook 8.2.2.] Nothing has changed on our network. The strangeness is the same and not all users are affected.

Login can take up to 5 minutes - users usually abandon before then (force-quitting Outlook). The fix is to change the user's profile in Outlook Settings (e.g., by logging in as myself) and then change it back to the user. Everything is fine then. Re-creating a brand new profile (after trashing the Exchange Profiles folder) has the same effect.

It is as if the profile has become corrupted - but why? We did nothing on the server and all user's machines have a "Standard" desktop.

It sounds similar to Aimee H. Shaw's problem (July 7) but I don't see how it has to do with admin rights. Also the fact that after 5 minutes login does work suggests there might be a delay in finding the Exchange server - but again, no IP changes have been made.

We've mopped up all the problems now - we hope - probably about 10 percent of our 500 (Mac) users. 800 PC users were not affected.

Watson for Exchange, Entourage still to leave problems.

July 24, 2000 -- Dan Schwartz spoke to Microsoft product reps at Macworld Expo about its upcoming Mac e-mail products, Watson for Exchange Server and Entourage (in Office 2001). He says that business users will still have to use BOTH e-mail clients, as Watson for Exchange Server for Mac will not support Internet POP3/SMTP servers:

Well, MacWorld Expo had a few interesting tidbits if you have to support Macs on the Internet and/or connected to an Exchange Server. I had a long chat with the product honchos for the Outlook for Exchange client as well as for the Office 2001 "Entourage" client.

Basically, those of us using Exchange Server have the Outlook 8.2.2 client, while Watson is slated for 1Q2001 release. Unlike the Fat Binary Outlook 8.2.2, Watson will be PowerPC only. Watson, like Outlook 8.2.2, however, *still* will not support standard POP3/SMTP servers - Only Exchange. These two products are written and supported by the Exchange product group, and *not* by the Mac group.

On the other hand, Office 2001 will introduce the Entourage 2001 PIM and POP3/SMTP application. Microsoft is positioning Office 2001 for Mac as a home (consumer) application, with Entourage being part of the package. In addition, the next Outlook Express will be a stripped down Entourage.

What does this mean for us poor slobs? If we have to connect a Power Mac up to an Exchange Server, we can look forward to Watson. But if these same Macs also need to connect to the Internet for POP3/SMTP service, then you'll *still* need to load either Outlook Express, Entourage 2001, or the stripped down OutlookExpress version of Entourage (when available).



Outlook 8.2.2 -> Watson

MICROSOFT MAC OS GROUP (Consumer focus) - POP3/SMTP Outlook Express 5.0.2

Entourage 2001 -> Outlook Express (Entourage "Lite")

Looks like a bureaucratic pissing contest between the Microsoft Mac OS and Exchange product groups, which means we get hit with the spray. No matter what, we'll *still* have to support multiple email clients.

Watson won't support POP/SMTP, but Entourage may support Exchange.

July 25, 2000
David Toub

I can confirm Dan Schwartz's comments. I had received an e-mail from Irving Kwong, head of the MBU, who informed me that Watson would not include Internet mail support, only Exchange. He also informed me that he is currently using Entourage connected to an Exchange server (!). However, having used OE to connect to our Exchange server under TCP/IP, it only will detect mail from the outside world. All intra-office e-mail is routed through Exchange, not SMTP and is apparently invisible to non-Exchange e-mail clients. So I'm not sure how Mr. Kwong gets his internal e-mail using Entourage with Exchange, but his e-mails were very helpful and pleasant.

Just to clarify, Watson is the next Mac version of Outlook for Exchange Server, and Entourage is the POP/SMTP mail client and PIM that will ship with Office 2001.

Outlook/Exchange printing problem and suggestions (Mostly HP printers)

November 10, 2000. Jeff Lucia is having a problem with printing from Outlook/Exchange 8.22 for Mac. (Several suggested fixes are below.)

The user can read mail without any problems (looks perfect on the screen), but when they print it, it gets cut off. It is almost like there is an invisible margin and any text after the margin is just left off.

This has occurred with OS 9.04, and 8.6, G3 (Beige or B&W) and G4's. I have removed EVERYTHING Outlook and Microsoft and reinstalled all Microsoft applications (thinking it was a library problem) to no avail. The only solution I have been able to find, is a clean install of the OS. There's got to be a better solution than that (I pray :) ). Also, I have turned off ATM and tested this with a base set of fonts in the fonts folder with the same results thereby ruling out our font library. The problem also occurs on all printers.

November 16, 2000. Tekel Gayle thinks the problem is a corrupt font:

I think I have seen this problem before. I believe the problem is beingcaused by a corrupt font on the senders side. To troubleshoot, have the users load the basic Macintosh fonts. Send a test message and print. This should work and you should the identify the troubling font.

However, Michael Llaneza offers this workaround to the problem:

This sounds like a printing issue we had here. In our case, we have an NT4 print server and HP printers. The only way the Macs can print properly is by using the Generic PPD and *not* the latest drivers from HP.

I'm assuming that Mr. Lucia is also going through an NT print server since he's using Exchange. I don't have the root cause of the problem nailed down yet, but the workaround will get stuff on paper.

Matthew Smith responds to this advice:

When one uses the NT print server, you should always use either Generic or preferably LaserWriter Plus v38.0 as the PPD.

November 21, 2000 -- Perbix Michael suggests looking at drivers:

We use Outlook 8.2.2 and print to HP 4000 and 4050 with no problem, however when using the new HP universal installed (version 3.2 and newer) you can only print 1 page, then get errors until you quit Outlook and restart the application. Reverting back to the USB/AT version of the HP 800 specific driver solved the problem.

Also the new 3.2 and above driver has a problem with AppleTalk zones. It sees printers in the computers zone but you can not switch to any other zones. At least we can't. We use all Cisco hardware.

Jason Wohlgemuth found a new printing snag:

I've found a bug in Outlook 8.2.2 that shows up in OS 8.5, 8.6, 9.0 and 9.0.4. (These are the only OSes that I have access to)

When you make an appointment in the calendar that has the & symbol in it and you print it shows up as an underline character. For example. I had 2 users in our R&D Dept that have Macs with 8.6 on them. They had received an appointment in their calendars for "R&D Meeting" When printed, it came up as "RD Meeting"

I have tried a clean install of all the above mentioned OSes and it showsup. It even shows when doing a print preview either with LaserWriter drivers or Adobe Drivers. Even if I go to desktop printer and select Generic it still shows. I have searched the net and found nothing on this issue.

November 27, 2000 --
Luis Antezana

I've been reading the posts about the Outlook 8.2.2 printing problems. None of my users have any problems printing Outlook 8.2.2 through our NT server to any of our HP 5000's or HP 4MV's using the printer-specific PPD's. We have multiple different Macintoshes from 604e's through G4 and both OS 8.6 and 9.0.4 installed. We have used both AdobePS 8.7 and Apple LaserWriter 8.6.5 and 8.7 drivers.

So to sum up, use the Apple or Adobe driver and the printer-specific PPD and you should be fine!

November 28, 2000 --

Michael Alatorre send a report about his users problems printing from Outlook/Exchange 8.2.2 for Mac to USB HP DeskJet 970Cxi inkjet printers. He tried a suggestion another reader had sent (using HP DJ 800 USB/AT drivers), but it didn't work. He has been able to print to a networked HP 4000N.

My users and I have seen this same problem with our USB HP 900 inkjets and Outlook/Exchange 8.2.2. Some months back I even contacted HP support and had a long call with the Mac support based out of Portland, OR. He was very patient and we tried several re-installations over the phone. Ultimately, he thought it was a problem with the driver out at that time. When 4.02 driver came out, we tried it. But, we had the same "print 1 page then get errors..." results.

Unfortunately, we could not get HP DJ 800 USB/AT driver to recognize our attached DJ 970Cxi's. Perhaps, that 800 series driver can't work with the 900 series DJs. Either way, it's frustrating for our workgroup. There's a thought of going to the USB Epson or Canon inkjets, but the desktop printing that the HPs offered was a convenient feature for anything but printing with Outlook.

Addendum: while our users cannot use their DJ 970Cxi's for general printing from Outlook 8.2.2, they successfully use a networked HP 4000N to print from this client app without a problem. They just prefer printing locally for its convenience and not having to get up and go to another room to get their output. Also, 8.2.2 is the only app that's giving them this trouble--all other apps (Office, Acrobat, MacFlow, Netscape, etc.) work just fine.

November 28, 2000 --

Byron Songer uses Exchange Server in Louisville, Kentucky public schools. He has problems printing form Outlook 8.22 (Mac OS 9.0.4) to HP DeskJet 800 series printers.

Recently I came across the problem of getting Outlook to print to an HP 8XX inkjet connected to the Mac's USB port. The problem is similar to that reported by another user. In Outlook you can print one e-mail and not print any others until you quit and restart the application. With an earlier HP driver you don't get an error message but the e-mail document fails to print. With the latest driver a message is presented stating that an error has occurred. Printing multiple copies from other applications is not a problem so I definitely feel this is a Microsoft problem. Printing to a PostScript printer works fine, of course.

Changing drivers fixes problem

January 4, 2001 -- Chris Bakowski offered another fix. Bakowski has a USB DeskJet 935c, but used the HP driver for the DeskJet 640 series. He said that the driver "appears to have solved the problem when printing more than once from Outlook."

January 24, 2001 --
Michael Alatorre

I'd like to confirm Chris Bakowski's fix of the _print one message from Outlook 8.22 to an HP USB DeskJet printer then get errors_ problem. Since installing the HP DeskJet 640c driver, this is no longer a issue in our workgroup with this client and our 970Cxi DeskJets.

HP driver update fixes Outlook for Mac printing problem

January 9, 2001 -- A reader reports that version 4.1 of the HP driver (for DeskJet 640c, 8xx, or 9xx printers supported by 4.02) fixes the problem of Outlook printing to HP printers.

Outlook 8.22 and Exchange meeting requests

November 28, 2000 --
Jeff Churchwell

[With Outlook/Exchange 8.22 for Mac], I have started to receive meeting acceptance or decline messages from users on my network, which I cannot open. All I get is an error message saying "The command you specified could not be carried out. An unknown error occurred." The odd thing is, I'm not the original sender of the meeting requests, nor am I a delegate to anyone, nor can I tell who is the original sender.

The persons acknowledging or declining meetings are both Mac and Windows Outlook 2000 users. Our Exchange server version is 5.5, SP3.

November 29, 2000 --
Ryan Taylor reports

A client of mine is receiving the exact same message. She is receiving meeting acceptance and declinations from users on her network. She did not initiate the invitations and some are from people she doesn't even know. She gets the same error message when trying to open them: "The command you specified could not be carried out. An unknown error occurred." I can move the files to the deleted items folder but I cannot open them.

She is using Outlook 8.22 on her Mac G4. The other people are using either Outlook 2000 or Outlook 8.22. Our Exchange server is 5.5 SP3.

An exhaustive search of Microsoft's Knowledge Base turned up absolutely nothing.

Reader offers solution:

December 11, 2000 --
Ryan Taylor

John, I've fixed this problem. I was able to open these meeting requests on my PC but not the Mac and determined that one person was on all of these meeting requests. Found out that she was accidentally setup as a delegate set to receive all of her VP's meeting requests. The VP is on a PC using Outlook 2000. Since she is on Outlook 8.2.2 she can't open these Outlook 2000 meeting requests. I removed her as a delegate and the problem disappeared.

Microsoft Knowledge Base had a similar article with the same error message pertaining to Outlook 98 and Schedule+ for Win95.

TIP: Moving e-mails from Outlook (PC) to OE and Entourage (Mac)

June 4, 2001 -- Jeff Spetalnick sent this procedure for moving e-mail from PC to Mac:

I have been trying for months to move my PC files to my Mac and finally just stop using PC altogether after too many crashes and its extremely impractical file organization. I finally figured out how to do it:

1. Open Netscape Communicator 4.7 on the PC.
2. Import Outlook 97/98 files
3. Copy the Netscape/Users/{USERNAME FOLDER}/Mail folder to the Mac
4. Create a folder on the desktop called Old Netscape User Folder
5. In the System: Preferences:Netscape Users:{Username Folder}:Mail folder copy all of the items from MAIL to the desktop folder just created
6. Copy all of the items from the PC Netscape MAIL folder to the Mac Netscape MAIL folder
7. Open Netscape and all of the mail files will appear
8. Highlighted each imported folder one by one to allow Netscape to display the files
9. Quit Netscape and Open OUTLOOK EXPRESS
10. Select Import from Netscape

I am using Entourage, but Outlook Express has an Import from Netscape as well.

Outlook 8 and large Personal Folders

July 2, 2001 -- Our anonymous reader also reports a problem with Outlook 8.x:

I'd like to warn your readers of a potential problem with Outlook Mac (v8 and possibly v9) and LARGE Personal Folders. With more and more messages stored in Personal Folders (archiving almost every message is important here), a user I support has corrupted his Personal Folder. I think this has happened because the file has exceeded 2 Gig in size. If this is the case, MS should apologize for not properly stress testing their software! Outlook should have graciously suggested that the Personal Folder was getting kind of big and that moving more files into it would be disastrous. Oh well. 

The Inbox Repair Tool fails to recover the file and reports a list of errors 10 sheets long. Uhg.

So, I have re-installed the backup from yesterday (whew! - thank you Dantz). Of course, the content he was moving has an unknown whereabouts. We will have to wait for the opinion of the Exchange Server managers.

Now that I have a 1.9 Gig file, I'm going to stress test version 9 to see if they handle it any better.

| Top of This Page |

Other MacWindows Departments

| Solutions | Tutorials | Tips | News Archives |
MacWindows Home |

This site created and maintained by John Rizzo
Copyright 1999-2001 John Rizzo. All rights reserved.