Click for MacWindows home


 
 

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

Outlook 2001:Mac for Exchange Server

Information related to the released Outlook client for Macintosh

Last updated August 16, 2006


On this Page:

More cross-platform Outlook info at MacWindows

For information on earlier versions of Outlook for Exchange Server, see the following:

 

If you have any information to share, please contact us.


MacWindows Report

Outlook 2001 Mac is a client for Microsoft Exchange Server. It is not a POP/SMPT Internet mail client like Outlook Express or Entourage. In addition to e-mail, Outlook 2001 contains a contact database and group calander and scheduler. Outlook 2001 is the first version of the Mac Exchange client that featuries group scheduling, calendar, and task management that are format-compatible with the Windows Version of Outlook. Both Mac and Windows versions will use the same data.

Version History

Outlook 2001 vs. Outlook 8.2.2

Features in Outlook 2001 that are not in Outlook 8.2.2 include:

Microsoft recommends using Outlook 2001 with Exchange Server 5.5 or Exchange 2000 Server. Outlook 2001 supports connection to Exchange Server using AppleTalk and TCP/IP. Outlook 2001 is a available in English, French, German, and Japanese.

Outlook 2001 vs. Entourage

Outlook 2001 and Entourage are too different programs. Outlook 2001 is a Mac client for Microsoft Exchange Server, and is a collaboration tool. Entourage is the mail client/contact database/schduler in Microsoft Office 2001 and Office X, and is meant to be a personal tool.

(At one time, Microsoft had a web page comparing Entourage 2001 vs. Outlook for Exchange Server, identifying the types of users the company thinks would use Entourage and Outlook 2001 for Exchange Server. This page has been removed.)

Entourage is an Internet standards mail client with some built-in, single-user calendaring capability. It connects to any POP/IMAP server --including the one in Microsoft's Exchange Server--for sending and receiving e-mail. However, it won't access Exchange Server's collaborative calendar/scheduling features.

Outlook 2001 provides messaging and calendaring compatibility with Windows Outlook for Exchange Server. If you configure Exchange Server to send and receive e-mail through the Internet, Outlook 2001 can exchange mail over the Internet as well as through a corporate e-mail system. However, Outlook 2001 users can not be able to access there own non-corporate, personal e-mail accounts (POP/SMTP).

Outlook 2001 lacks many of the features of Entourage, including synching to Palm OS, rendering and sending of HTML e-mail, and integration with Word.

IMPORTANT: Installation procedures for upgrading to Outlook 2001

Upgrading from Outlook 2001 Beta to Outlook 2001

Much of the data created with Outlook 2001 Beta is either incompatible with Outlook 2001 or unstable, according to Microsoft. Users of Outlook 2001 Beta will need to create new profiles, appointments, and meetings to prevent "instability." (You'll be prompted to create a profile if you have only the Beta installed. If you have both the Beta and Outlook 8.2, the shipping Outlook 2001 will use the 8.2 profile.) Microsoft also recommends removing contact names that were installed with the Beta after you install the new Outlook 2001:

After upgrading to the released version of, remove all names from the Share my data with these people list in the Sharing panel in Preferences. If you do not remove people added using the Beta version, you may experience system hangs or crashes. After you have removed all names from the list, you can add them back using the released version of Outlook 2001.

Upgrading from Outlook 8.x to Outlook 2001

Outlook 2001 is more compatible with Outlook 8.x than with Outlook 2001 Beta. For instance, profiles from Outlook 8.2 are compatible, and will be automatically upgraded when you install and run Outlook 2001. Microsoft's Outlook 2001 release notes give this advice for upgrading:

If a profile created using Microsoft Outlook 8.2 or earlier is detected, you will be prompted to upgrade this profile so that it can be used with Outlook 2001. (Outlook 2001 Beta profiles will not be upgraded. See the "Information for Outlook 2001 Beta Users" section below.)

If Outlook Calendar data is associated with the profile, you will be given the option to import the Calendar, Tasks, and Contacts data into Outlook 2001. If you do not import your old data, it will not be visible in Outlook 2001. In either case, a local copy of your Calendar data will be saved to a Schedule+ Interchange file (.sc2) and placed in the Microsoft Outlook 2001 folder.

If you have a Personal Address Book (.pab) file associated with your profile, you will be given the option to import those contacts into an Outlook 2001 Contacts folder and to remove the Personal Address Book file. If you choose to do so, contacts will be created for each of the entries in the Personal Address Book, and placed in the Contacts folder. Then, the Personal Address Book service will be removed from the profile. The Personal Address Book file will not be moved or deleted.

Reader Reports on Outlook 2001

Note: some of the issues with Outlook 2001 Beta may also exist with the release version.

TIP: on using the Auto-signatures from the Beta version

July 2, 2001
Luis D Antezana also sent us a

Although Outlook doesn't migrate Beta users' profiles, the data is in System Folder>Preferences>Outlook 2001 Beta Profiles. I manually moved my Auto-signature file over to the new (old if converted from 8.2.x) System Folder>Preferences>Exchange Profiles folder and it recognized immediately. It's possible the beta profile data could also be moved, but it's easy enough to create new ones that I don't care to risk any weirdness from the Beta profile data.

First impressions

July 2, 2001
Dr. David Toub

Here are my impressions, having eagerly awaited this release for one year now...

All in all, worth the wait, but not as feature-rich as it should be. Outlook remains the ugly stepchild of the Microsoft Business Unit, but at least it got updated (which is more than could be said for Project!)

July 2, 2001
Luis D Antezana

Can I just gripe about a few things in the final Outlook 2001?

1. No Palm support, despite it being "the most requested feature." However, I think that it should be easy to get third party support for this (DataViz?) since the Outlook format is now the same for Mac and Windows and there are many third party solutions for Windows/Outlook/Palm.

2. Import/Export is generally limited to Contact information (except for importing stuff from Outlook 8.2.x)

3. No HTML support

4. No forms support within the client

5. No real difference from the Beta release except for a few minor changes and the import/export - I was hoping for some surprises.

6. (The biggest one of all) You noted this in yesterday's MacWindows report, but I want to underscore its significance: from the Release Notes -

"Appointments and meetings created using the Outlook 2001 Beta should be re-created using the released version of Outlook 2001. Items created using the Beta may cause instability in the released version of Outlook 2001."

For those of us who implemented the Outlook 2001 Beta release office-wide, this is a heck of a thank you present from Microsoft. I acknowledge that Beta releases generally shouldn't enter a production environment, but after 4 months of testing I couldn't find any reason not to install it on our users' systems (plus it let us all be compatible with Outlook Web Access's calendars). Now everyone's Beta-created appointments and meetings need to be manually deleted and re-added?!?! This was definitely not expected, and not discussed anywhere from newsgroups to beta release notes until yesterday. You can imagine the hellish situation this puts me in!

P.S. Outlook 2001 final has a bigger recommended RAM size by about 3,000k, but appears to occupy about the same RAM space as the Beta.

July 9, 2001
S. Younker

An open letter to Microsoft...

The new version of Outlook 2001 for the Mac is a major disappointment. I'm not dismissing the importance of the full Calendar, Contact, Tasks and Notes integration with the Windows version of Outlook, or the new look and feel, but there are so many things that are missing that I wonder what took Microsoft so long to get this product out the door. Maybe the problems are because the Windows Outlook team was responsible for this product and not the Macintosh Business Unit in the Bay Area. I just don't know.

The issues as I have come across them:

1. Outlook 2001 does not have the ability to display HTML e-mails. I met an engineer at Macworld SF in January and he told me that this feature may not make the final release because MS would have to write an engine to handle the html. Hello - doesn't Entourage do this? How about IE? Can't MS share some code among it's divisions in order to incorporate this much needed and much requested feature?

2. No Palm support - enough said!

3. Does not display graphic backgrounds - Maybe this is a small issue, but then again it should be an easy one to solve. In my corporate environment I'm constantly receiving e-mails from Win Outlook users with cute little background image attachments. Unfortunately on the Mac they show up as .gif and .jpg attachments.

4. No new attachment formats in the Send Options dialog. Entourage supports 'AppleDouble' encoding, but not Outlook 2001. Again, can't MS share some code between divisions.

I've been waiting several years for MS to address the issues above and telling my users that MS would be releasing an upgrade that would make our Outlook much more compatible with the Windows world. The calendar integration is a much needed first step, but in my opinion MS has fallen way short of releasing a great upgrade; especially with the wonderful releases of IE and Office 98 and 2001.

Now that it is finally out I have no great enthusiasm for installing this product. This upgrade took so long to get out the door that I'd be foolish to expect MS to release an update correcting these problems within the next few years.

My users will notice the pretty new looks and better calendar integration, but they will still be asking me the same questions: Can I hot sync my Palm with my Outlook calendar?, Why don't some of my e-mail attachments get received correctly? and What are these funny GIF and JPEG icons doing in my e-mail?

Problem with fonts; new feature not found in Windows version

July 2, 2001

Another reader (who wishes to remain annonymous) points out a feature of Outlook 2001 that isn't in the Windows version:

Just a note to remind new Outlook users of the problem between Outlook Beta and an "excessive" number of fonts. For those having problems with crashes and unexpected quits, I suggest that this "feature" may not have been fixed. Try to eliminate all but a base set.

On a positive note, this software exceeds Outlook 2000 for Windows with one interesting administration feature. We Mac users can create "Discussion" folders in "Public Folders". Windows users can use the discussion folders, but they cannot create this special type of folder. At least, we could not find the feature among the "just fit it in somewhere" menus and Options. We came up with a trick though: create a Discussion folder on the Mac and have Windows users "copy" it. 

Of course, our Exchange Admin people are scratching their heads and a little hesitant. This fancy feature hasn't been test on the REAL computer platform and may cause problems!

I pointed to the Outlook Web Access site and they are fully supported in a browser environment too.

Updating from Schedule + to Outlook 2001

July 3, 2001
Michael Alatorre

While I enjoy the new interface and features, there is one problem that will prevent the Mac users here from converting: no support for Schedule+ for group scheduling. If we import the sc2 file as recommended, the calendar becomes a local calendar and is no longer stored on our Exchange servers.

I believe PC Outlook client allows for using either the Outlook or Schedule+ formats. Unfortunately, this client does not support this option. Our IS department has sent a message to Microsoft stating this. Perhaps, an update in the future will give us Schedule+ support.

One can use both clients (2001 & 8.2.2) at the same time, with the latter for group scheduling, without a problem. However, it's not the most elegant for workarounds.

July 6, 2001
John Parnaby

Regarding Michael Allatorre's comments on Outlook 2001: "no support for Schedule+ for group scheduling. If we import the sc2 file as recommended, the calendar becomes a local calendar and is no longer stored on our Exchange servers."

This isn't true. Outlook 2001 (in most cases) will auto-import the Schedule+ information the first time it is run on the client. [If this fails, you can import a .sc2 file manually]. This turns the Schedule+ into Outlook calendar information which is available across the network (not local). Schedule+ users (and old 8.22 clients) will not be able to see this - only other Outlook clients can see this calendaring info.

This is where the problem arises. A good number of PC installations of Oultook 2000 will include "Schedule+ support" (depending on the PC configuration). Mac Outlook 2001 users don't get Schedule+ support. If this is the case, there is a danger that PC Outlook users and Outlook 8.22 Mac users keep the old Schedule+ info "alive" on the server.

If you are definitely opening Outlook calendar information, it should all work for cross-platform group scheduling. Practically, for us, this has meant we have to roll-out the product department by department so that no-one's calendar information becomes unavailable when we switch to the 2001 product.

July 6, 2001
Ryan Taylor

John, per Michael Alatorre's comments about the lack of Schedule+ support in Outlook 2001, I believe Microsoft is moving away from Schedule+ support on both platforms. Outlook 2002 in Office XP no longer supports Schedule+ although you can import Schedule+ data. I don't think Microsoft will incorporate Schedule+ support in any future versions of Outlook from now on.

Problem with IP connection via NT

July 3, 2001
Johannes Kislinger

Of course we are all pleased with the developments. However on our NT network we still can't figure out why Outlook is not able to communicate via TCP/IP, it still changes to AppleTalk.

Problem with address books and folders

July 3, 2001
Robin Jackson

I installed 2001 release version. I have deleted everything to do with the beta version. I am having 2 main problems:

First is that I cannot seem to download my company's offline address book although I had no such problem with the beta version.

Second is that a number of folders that I have marked to be offline keep losing this designation and do not synchronize, I have no idea why this is happening.

Jackson added on July 6:

The error happens half way through the normal download just after the following message 'copying offline address book template file.'

July 18, 2001
Rowan Pym

I am having the same problem with downloading the offline address book. I get the error message: An error occurred while opening the Microsoft Exchange offline address book files on the Microsoft Exchange Server. See your administrator. (OK)

Then: Unable to download the offline Address Book. The Microsoft Exchange Address Book could not be accessed. (OK)

As I am the administrator, this is not much help to me. The problem does not affect all installations (some work fine).

July 31, 2001
Mike Donaldson

I have also been unable to download the offload address book - exactly as described by Rowan Pym on July 18th. Another person in my office with the same machine configuration is not having any problems. Hope someone figures this one out soon!

If you've seen any of these problems, please let us know.

Additional address book problems

(Note: there are some other address book problems described above.

August 30, 2001 -- Thomas McPhee has an Outlook 2001 problem we haven't heard of before:

I am having a problem with downloading the offline address book. I get the error message: \
"An error occurred while opening the Microsoft Exchange offline address book files on the Microsoft Exchange Server. See your administrator."

This never happened with Outlook 8.2. Our office just switched to Exchange 2000 from Exchange 5.5. The problem occurred on both versions of the exchange server.

If you've seen this problem, please let us know.

September 12, 2001
Shane Palmer

I am having the same problem with Outlook 2001, and after browsing through the miscrosft.public.outlook.mac newsgroup I see that several other people are having this problem. I tried to troubleshoot by reinstalling the older Outlook 8.2.2 client on a "clean" Mac, which is a Mac that I erased the hard drive, installed OS 9.1 and Outlook 8.2.2 and absolutely nothing else. I found that I can no longer download the offline address book in Outlook 8.2.2 as well as Outlook 2001. I made sure I used a new account on the Exchange server that has never been "touched" by any PC version of Outlook or Outlook 2001 for the Mac. I have not had a chance to talk with the Exchange Server admins to see if there have been any settings changed on the servers. We are using Exchange Server 5.5 and I believe we have all of the latest service packs for Exchange and Windows.

September 12, 2001
Peter Rock has seen the problem with older versions of the Outlook Mac client:

Regarding your item "Outlook 2001 errors with address book" which referred to an error message when downloading the offline address book...This is not an Outlook 2001 specific problem. I had this error while using the "old" Outlook (8.2.2). It was related to a setting on the exchange server and was not a client issue. My system admin was able to clear up the problem by adjusting the Exchange Server parameters.

According to my system admin, the change is under "exchange server admin" (manages exchange server) "DS site configuration properties". Look for the tab "offline address book". The global address book needs to be selected (not recipients).

Suggestions for setting up Mac Outlook to avoid problems

July 6, 2001
Jeff Roback

I've seen a lot of reports on your site regarding trouble using TCP/IP to connect Mac Outlook clients to Windows Exchange servers. We work a lot in cross-platform environments, and had good luck doing this, but have found that DNS and confusion about Internet domain names versus Windows domain names is usually the source of problems. Below is a tech note I put together for our staff. Hopefully others at your site will find it helpful.

SETTING UP MAC OUTLOOK CLIENTS FOR EXCHANGE SERVERS:

The biggest problem with Mac Outlook clients results the fact that the Outlook client INSISTS upon doing full DNS resolution on the servers name and the domain names in your TCP/IP control panel--ignoring whatever you enter in the initial profile configuration screen.

Here's how we resolve this :

For this e.g.: Your exchange server is called ACMEMAIL, in Windows domain ACME, with registered domain name acme.com

Remember: Windows NT machines have TWO different domain names: An Internet domain name (acme.com) and a windows NT domain name ACME. In Win 2000 this gets blurred a little....

Step to setup Mac Clients to connect to a Windows NT Exchange Server:

1) Make sure you've created a DNS "A record" for the windows computer name of your exchange server. (acmemail.acme.com). This must be done by whomever hosts your domain name. Usually your ISP, but we host our own using Mac-based QuickDNS :)

2) In the Mac TCP/IP control panel under "additional search domains" put the exchange server's registered Internet domain name (acme.com) *** Very important and often missed

3) Open the Outlook client to create your profile. Enter the WINDOWS name of the server (ACMEMAIL) and the name of your Exchange mailbox.

(NOTE: During logon, it does NOT necessarily use the server name info you entered here -- it uses this info for its initial contact with the server, and which point it asks the server its name (ACMEMAIL). Upon your next logon, it takes "ACMEMAIL" and then appends strings from your "additional search domains". It then does a DNS lookup for acmemail.acme.com. This is why you can key in the IP address for ACMEMAIL and "Check name" works, but you can't login. Check name uses what you entered, logon uses the resolved DNS address.

You should then be all set.

February 19, 2002
Daniel Granja

I discovered that the ExchangeServer's DNS host name (for example "mail" in mail.yourdomain.com) needs to be the same as the NT Server's own internal computer name. If the two are different, which isn't all that uncommon, then your Outlook 2001 client setup will successfully connect and create a profile, but when you try to log on you will receive errors regarding the information store and the client will shut down when trying to connect.

In the short term, I solved this on my machine by creating a host file which points the NT computer name to the actual registered DNS name. The appropriate fix is either to have the computer and DNS names match, or enter a DNS record for the computer name.

Now if I can only find out why my Entourage client can send Internet mail through my Exchange server, but my Outlook 2001 client can't...

(See our Mac OS X Report page for configuring a hosts file in OS X.)

TIP: Retaining Folder Views

July 9, 2001 -- Roger Timpson send us a tip on how to retain folder views in Outlook 2001. First, he describes the problem:

If you make any change, then leave that folder, when you return it is back to the default view. (Most people I work with have their own preference for how they like their messages displayed.)

Timpson then described how retain the folder view:

If you want a view for server-based folder, you create it with "Define Views..." in the "Folder views" group. Then select the folder you want to change, and select "Properties" under the File menu. Click the "Administration" tab and you'll see "Initial View on folder" next to a drop down menu. The new view will be in that menu - choose it and you're done!

If you want a view for one of your personal folders, create it in the "Personal views" group. These will show up in the "View/Current View>" menu. When you choose it here, it will be retained. This is apparently the way it works in the Windows client .

Problem (and workaround) with rules: Outlook 2000 SP-2 and Outlook for Mac rules compatibility

July 9, 2001
Em Herzstein

Taking things cautiously, I upgraded one of my clients to Outlook 2001 from 8.2.2. She reported the next day that most of her mail was disappearing: she had "rules" configured to filter messages from different senders into different mailboxes in her personal folders.

She saw the mail appear briefly in her inbox and then vanish, not appearing in her personal folders or anywhere else she could find.

I found that I needed to go through all of the rules and, for each destination mailbox, click on the destination button and then navigate to it via Outlook's interface, in effect "showing" Outlook again where the destinations are. After that, the rules worked okay.

Microsoft's recommendation

July 17, 2001 -- Microsoft has posted this note about and issue about rules with Mac and Windows clients to Exchange Server:

If you use Outlook for Macintosh on a Microsoft Exchange Server and install Microsoft Office 2000 SP-2 (for Windows), you will experience a change that affects the Outlook for Macintosh Inbox Assistant rules. After installing Office 2000 SP-2 for Windows, you need to remove the rules created by Outlook 2000 Rules Wizard from the Exchange Server mailbox, and recreate your rules with the Outlook for Macintosh Inbox Assistant.

The Microsoft page goes on to give instructions on how to remove the rules created by Windows and recreated the rules with Outlook for Mac.

(Thanks to Monty Solomon for passing that along.)

How to view mulitple months in the Calendar window and other tidbits

July 9, 2001
Jeff Sternberg

One "first impression" caught my eye, from Dr. David Toub, July 2:

"Lack of certain view options, such as the ability to see the first few lines of an e-mail in the Inbox pane, the ability to view more than one month on the right side of the Calendar window"

While the first item looks right to me (I haven't found this feature in Outlook 2001), the second item is actually incorrect. All you need to do is drag to the left the separator between the month calendar/task list and the daily, weekly, or monthly view on the left. When you get the right column wide enough, two months show in the right side of the Calendar window. I agree that viewing two months in this section of the interface is quite handy -- it should probably be the default arrangement, in my opinion.

Another missing feature

Overall this seems to be a solid final version. However, the missing features your readers have noted are irksome. I've discovered one more: in Outlook 2000 for Windows, you can right-click a folder, choose Properties, and then configure the AutoArchive tab. This handy little feature will automatically archive old messages to a Personal Folder for you. It's nice for the "Sent Items" folder, for example. You can still manually copy mail to a Personal Folder, though.

Slow-down when dragging a large number of e-mail messages

And one more performance issue, possibly a bug: selecting and dragging many mail items from the mail list to a different folder is kind of tricky. If you select and then try to drag more than about 50 e-mail items, the interface for dragging feedback slows down considerably. This gives you the impression that the program has frozen; on the contrary, it's just working hard, and not giving you any feedback about what it's doing. Eventually, if you release the mouse over the target folder, the items will be copied. Of course, drag-and-drop for one or a few messages works just fine; I would suspect that some optimization needs to be done for drag-and-dropping many messages.

Offline use of Outlook 2001: Contacts folder won't download.

July 9, 2001
Dr. David Toub

I have found that unlike 8.2.x, Outlook 2001 does not easily permit me to download my Contacts folder (fka Personal Address Book) for offline use. Rather, and to my surprise this past weekend, I was left with an Offline Address Book containing my company's global address list, but not my personal addresses. After much trial and error, what seems to work best is to designate the contacts folder as being available either online or offline (via the Properties:Synchronization tab) and then remembering to sync the contacts folder manually. The option of "Download Address Book" does not work properly, at least for me.

Also, the weirdness involving certain drop-down menus may be related to a conflict with DAVE, although I have not absolutely confirmed this as of yet.

If you've seen this problem, please let us know.

TIP: Addressing to multiple contacts from contacts view

July 11, 2001 -- A reader (who wishes to remain anonymous) sent us this tip that only works in the new Mac version:

Outlook Mac has another feature that is hidden from the Windows users. Addressing a message to multiple contacts from the contacts view:

In the Mac version: Select several contacts (as usual, shift click for a range; command click for noncontiguous) and select "New Message to this Contact". Voila, a message addressed to all the contacts you selected.

In the Windows version: Select several contacts and select ... , no, right click ... , no ... . Uh? There is a "trick" that shouldn't work but does: Drag and Drop the contacts onto your INBOX (Don't try this in Outlook Mac). A new message will generate addressed to all your selected contacts.

Windows feature not in Mac

July 11, 2001
Danie Foshee

One feature the Windows Tasks has is the Timeline view, where the all Tasks are viewed in a Gantt-like chart view.

Problem with Outlook 2001 crashing/quiting

A reader reports Type two errors; some suggestions as to the cause are below.

July 11, 2001
Doug Chapman

After connecting with the Exchange Server and displaying the Inbox Window, Outlook 2001 crashes with a Type 2 error.

Macsbug indicates a problem (PowerPC unmapped memory exception) in the routine "strcmp" (location +0001C) in the CFM "MSL C.PPC.DLL".

Outlook 2001 will start and run in off-line mode without crashing. The error occurs when connecting to the server (Version 5.5 Enterprise, service pack 3). The Mac system is on an NT network running TCP/IP with Open Transport version 2.7.6. The Macsbug information indicates that Outlook is executing some code associated with MAPI access to the server.

The error occurs whether access is direct or through the dial-up service to the same server.

The Mac system is a PowerBook G3 Series, running 9.1, with 320 MB of memory. The error is consistent with or without virtual memory.

There is no problem running Outlook 8.2.2 to the same server.

Reducing the Mac extensions loaded to the "9.1 base extensions only" set provides no relief.

Outlook 2001 has been reinstalled several times, after removal of all previous Outlook files. The beta version was never run on the machine.

If you've seen this problem, please let us know.

A fix and possible causes

July 16, 2001
Doug Chapman

I have got Outlook 2001 running -- after thoroughly checking out extensions and control panels as possible sources of conflict, I used TechTool Pro to do a thorough check of the machine and files. A few bundle bit and date changes were made. I also rebuilt the desktop. Outlook is now working correctly - I suspect it was the desktop file!

July 16, 2001
Ken Hoope suspects Outlook profiles are the cause:

We've been upgrading approximately 100 users to Outlook 2001 from 8.2.2. We've seen the crash below when profiles are inherited from 8.2 and have been able to solve it by removing, then rebuilding the profile. Only one profile might be bad when the rest (we have up to ten users on the same machine) are fine. Outlook profiles are hinky things at best.

More on the Type 2 problem

September 25, 2001
John Daly

About 20 percent of the people I upgrade to Outlook 2001 have this problem. Of those, half of them have had the problem go away for no reason. The Exchange admins and myself worked for a week on one, changing the profiles, changing what server the user was located on, resetting everything from scratch, all to no avail. Then one morning when we hadn't changed anything for a day or so, the user calls me and tells me it works fine now.

I will note one additional thing about my problem that isn't posted on your website: It doesn't crash unless you leave it sit idle for 45-60 seconds. As long as the users are active, Outlook 2001 works fine. If they pause in writing an email to answer the phone, in about 45-60 seconds, it will unexpectedly quit with a type 2 error.

Outlook Express to Outlook 2001 import

July 11, 2001
Joe Bisson

It seems that another key feature left out of Outlook 2001 is the ability to import mail and folder structure from Outlook Express to Outlook 2001. It is possible to import contact information, but I see no way to import OE E-mail. Oh yea, a Netscape and Eudora import would have been cool too.

Disappearing mail: problem and fixes

July 17, 2001
Boudewijn de Jong

I also see my mail disappear in outlook 2001. We had problems with Outlook 8.2.2, after a while we can only open one mail message and we can not reply at all. The program says not enough memory. Also some machines can not connect to the mail server-- it just crashes.

So when I saw Outlook 2001 I installed it. But I also have a Outlook version on a Windows machine. So when I had trouble in my G4 with Outlook I just opened Outlook in the Windows machine. But now I have Outlook 2001 and I open Outlook in the windows machine my mail in the inbox of the Mac disappears.

I installed outlook 2001 2 times because after a 2 weeks I again had trouble with replying and opening.

Suggested fixes, explainations:

July 18, 2001
John Wolf

I think Boudewijn de Jong's problem is that he has his PC set to file incoming mail to the inbox in his personal folders (.pst file), and not leave it in the server inbox. So, it appears like it has been deleted on the Mac, when in fact is is just filed on the PC, and his inbox is rightly empty.

We see that here all the time for users that use both Mac and PC's.

Paul Shields describes it this way:

When the user opens the Windows version of Outlook, it is most likely set to download all mail to the local PST file. This is the default behavior in many version of Windows Outlook. Obviously, once downloaded locally, the mail is no longer on the server and no longer visible to the Mac client. It is a little deceptive because it downloads the mail to a folder called Inbox, so people may not realize what is happening. Check the Mail preference in the Control Panels.

As for the other problems, I'm not sure, but I leave Outlook 2001 running continuously on my G4 with no problems. It does have memory leaks, so after long period it may hang and it is very sensitive to network/server outages or loss of connection.

Problem with sending meeting updates to resource accounts

July 23, 2001
Brian Willett

This report describes a problem I've found when sending Meeting Update requests to resource accounts in Outlook 2001.

1) A meeting organizer creates meeting in her calendar and invites a resource (in this case a conference room).

2) The invited resource automatically accepts the meeting request.

3) The meeting organizer later goes in to modify the original appointment, perhaps changing some text in the original message or adding additional invitees, etc.

4) The meeting organizer is then prompted to re-send a Meeting Update to all attendees, including the invited Conference Room.

5) At this point one of two bad things happen, depending on whether or not the Meeting Organizer changed the date/time of the original meeting:

a) If the time of the updated meeting is the left as-is or is only changed so that it still overlaps the original meeting time, the Conference room automatically declines the Meeting Update. When the meeting organizer examines the status of the invitees by double-clicking the appointment in her calendar, the Conference Room now displays a "Declined" status. However, if she opens the Conference Room's calendar (File>Open>Other User's Folder>Conference Room) she will find the originally accepted meeting still scheduled for the original time.

b) On the other hand, if the meeting organizer sets a completely new date/time when modifying the original meeting, the Conference Room resource will automatically accept the Meeting Update if the new requested time is free. Opening the Conference Room's calendar reveals that the resource has added a completely new and separate meeting to its calendar rather than modifying the original appointment.

The gist of the problem

In either case, the conference room resource is not recognizing that the Meeting "Update" it receives from the meeting organizer is intended to modify an existing meeting set up by that organizer. Instead, it processes the update message as an entirely new meeting request. Thus, if the time has not changed, it detects a time conflict; if the time is different (and free) it accepts the request as a new one. This is sure to cause confusion.

PLEASE NOTE: Per Luis Antezana's June 26, 2001 post to the MacWindows Outlook Beta Reports page, the resource's calendar has been configured so that another account named "Conf Rm Meeting Accepter" acts as its meeting-accepting delegate. An Outlook client workstation is then left logged in to the Conf Rm Meeting Accepter account so that it can auto-accept any meeting requests on its behalf. This configuration is a workaround to Outlook's lack of auto-accept functionality when receiving meeting requests from Outlook 97 and Outlook 2001 clients unless a computer is left logged into the resource account.

If you've seen this problem, please let us know.

Can't connect to VPN using Outlook 2001

There are suggested fixes below.

July 23, 2001
Paul Freedman

Having migrated to Outlook 2001 from the beta AND Microsoft Exchange Server 2000 simultaneously, we can no longer connect via VPN (virtual private network) using Outlook 2001.

We CAN connect via VPN (TunnelBuilder) and CAN access files, etc. on the server. We CAN check names via Outlook settings. However, we cannot get Outlook to open up. It does not connect with the Exchange Server.

If you've seen this problem, please let us know.

July 24, 2001
Brian Thomas

We are also experiencing the exact same problem using the same configuration. If anyone figures this out it would be great to know.

January 4, 2002
Joshua Hadley

We are having numerous "just plain problems" with Outlook under Mac OS 9.0.2 and 9.1. The main issue is with connection timeouts or something similar. You'll be working along, typing an e-mail, and all of a sudden you get a small message box with a barber-pole, saying that Outlook is "communicating with the server", when in fact it is NOT communicating with the server. This may or may not resolve itself in a few minutes -- or a few hours. We connect to our server via a VPN, created by a Windows 2000 Server, via 768K DSL. Windows boxes running Outlook almost never exhibit connection problems, only Macs. We've gone as far as setting up hosts files in the TCP/IP control panel, but that didn't seem to have any effect.

Another problem we see is upon quitting the app -- sometimes it "just sits there", e.q. leaves the icon in the applications area of the title bar (Mac OS 9) but does not go away. A Force-Quit cures it.

[These problems] seem to be random--sometimes they happen, sometimes not. After about 4 months of having it installed on about 10 Macs (various models), we cannot isolate the problems to any particular set of circumstances.

January 15, 2002
Warwick Teal

I also see the same symptoms when connected to my corporate network via VPN. My other network connections (Netscape, I.E., various apps, DAVE, FTP, etc. etc.) all work fine every time except MS OUTLOOK EXCHANGE.

It was working every time since the last few days and now despite how I use it under OX/X in classic mode. I am looking for some ideas on how to shoot the problem.

If you've seen this problem, please let us know.

A likely fix

July 24, 2001
A reader named Michael offered a suggestion that sounds like a possible solution:

I saw this problem during a migration. It was the default transport type being set to AppleTalk instead of TCP/IP in Outlook. A quick change in the prefs fixed it up.

Another possibility: configure a hosts file

July 24, 2001
Ed Dyer

This is usually caused by a problem with the hosts file. If the user can still get web access to work through a browser then that is definitely it. The thing that puzzles me is the user can still check names through the settings file-usually a problem if the hosts file is flawed. Just in case, make sure the WINS IP is still the same-the number in the hosts file.

Settings change in the Advanced tab to get VPN working

February 8, 2002
Jason Halvorson

Within the Exchange Server settings, you can disable the Server Polling option in the Advance tab. This should take care of the issue, if it is same one I've had in the past.

I am no expert, but it appears that Outlook on PC's and Mac's love to have uninterrupted connections to servers. If there is even a slight hiccup, the client has a bit of a fit. This is the setting change we had to make in order to make MS Outlook stable when using a VPN client:

February 8, 2002
Jason Elliott

We've had similar problems on our corporate network. If you connected through a cable modem or dialup that was not Sprint or AOL, the Outlook client would work fine via VPN. There's something about the authentication the VPN client uses that is not supported over some ISP's networks.

On the other hand, we have the Outlook Web Access setup, so that's a workaround. It's worked pretty well so far.  

Outlook 2001 can't print Task lists

July 26, 2001
Brad Hough

Does Outlook 2001 print a list of Tasks? I have been unable to print anything other than individual Tasks, although the Help files installed with Outlook 2001 claim that it is possible...

It seems that the print dialog that should appear when selecting Print from the File menu while viewing a Task list does not show up. Instead, a more generic print dialog box appears without the options described in Outlook's help files. The more elaborate print dialog box does however appear when choosing to print a Calendar. This would indicate that the code is built-in to the application, but is simply not "switched-on" for Tasks.

You can see the described print dialog boxes by opening the Microsoft Outlook Help Topics from the Help menu and selecting the Printing category. Next click on "Print a Calendar or Task List."

Workarounds:

July 31, 2001
Drew Klonsky says they only way he knows is to use ages-old Mac trick of tacking a screen shot using Command-shift-3. (If you use Command-shift-4 , you can draw the area you want to capture.) This creates a Pict file that you can then print. (If you have a better idea, let us know.)

August 1, 2001
Lianne Gaunts

This is not a better solution but a different one. We have kept Outlook 8.2.2 on our machines so that first thing in the morning we can open 8.2.2 and print the task list. Then quit 8.2.2 and launch 2001. So far this seems to be working for those people who want to print task lists.

Outlook 2001 hanging in OS X Classic mode

July 26, 2001
John Chardine

I have been running Outlook 2001 in Classic mode of Mac OS X for a while and put up with the occasional hang (symptoms are total hang in Classic and the X Process Viewer shows the TrueBlueEnvironment taking almost all the processor). However, I have had to go back to 9.1 with the latest trouble. I opened Outlook 2001 in Classic mode the other day and every mouse click moved the highlighted mail message to the Deleted folder, and from with that folder, mouse clicks moved highlighted mail somewhere else. I ended up losing a bunch of new e-mails which I hope can be recovered by the system administrator.

July 31, 2001
Michael Cohen

I've seen the Outlook 2001-in-Classic hang that John Chardine reported in today's note, and this afternoon I saw something similar to his moving mail issue: in my case, Outlook seemed to confuse the cursor coordinates so that clicking in the folder bar caused a checkbox in an appointment window to toggle. I had never seen anything like this happen until today, and coming across Mr. Chardine's report a few hours later was reassuring.

Suggestions for dealing with the problem

August 1, 2001
Phil Truesdale

I, too, have experienced Outlook 2001 hogging the processor and hanging when running in the classic environment. I've had luck tweaking this setting:

Tools Menu > Services > MS Exchange Server > Properties > Advanced. Select the option to check for messages every 30 seconds. I've experimented with different intervals, 15 - 60 seconds, without any difference.

I do the same if I'm VPN'd in to work. Outlook seems to keep a persistent connection/tickle to the server and if it loses it for whatever reason it hangs the entire classic environment.

August 1, 2001
Martin Chagnon

I have the same problem, hanging & using a lot of CPU. It seems that if you don't use CPU monitor, or the process viewer or TOP, the Classic environment is more stable.

Printing 5-day view, deleting messages

August 8, 2001
Shan Younker

I've run across a few more problems in Outlook 2001 not addressed on your site:

1. I usually print a 5-day view of my calendar. In Outlook 8.2 anything marked as an 'all day event' would show up at the bottom of the calendar print out in the 'Other' section. In Outlook 2001 the all day events show up at the bottom but they also show up in the 'timed' section of the calendar. If you have more than 2 or 3 all day events then they 'push' your timed events off the print out. A bummer for those of us still relying on a paper calendar. 

2. I have personal folders set up for my Outlook and all incoming e-mail is moved to my personal folders 'Inbox' The problem is that I get an error message when I try to delete items from my inbox. The message states 'An item could not be deleted. The action could not be completed.' If I remove the personal folders from the services dialog and then re-create them, I can delete items until I quit and restart Outlook. The problem then returns.

If you've seen these problems, please let us know.

Problems with Attachements

Reader problem with MIME encoding of attachments

July 6, 2001
Matthew Wallis

Re Mac Outlook 2001, it seems there are problems sending attachments to external Windows users with MIME encoding selected in either Outlook or the Exchange server. It's okay to recipients using Macs however, and it's okay to Windows or Mac users if you use UU encoding. We've only just started using Exchange server so I don't know if this was an issue with earlier versions of Outlook for Mac.

This problem seems to be particular to Outlook 2001 as I've tried sending the same files to the same people through the same Exchange Server using both Outlook 8.2.2 and Outlook 2000 and the problems do not occur with 8.2.2.

November 15, 2001
Matthew Wallis

I thought you might like to hear an update on the problem we were having with MIME encoded attachments sent from Outlook 2001 being unopenable in PC e-mail clients (OE, CompuServe, Hotmail) but OK in PC Outlook. Microsoft said they were able to replicate the issue, and after first saying that the problem had not been reported before as there was nothing in the knowledgebase it turned out that in fact it had been reported and that a fix for the problem had been refused. They also said that in fact Outlook 2001 handles MIME encoding in a RFC-compliant way but that the problem occurs because of the receiving software not being able to handle this method (introduced in 2001 presumably as there is no problem if you use 8.2.2), or in other words it's an "interoperability" issue.

Workaround

July 10, 2002
Tobias Hall

We just ran into the problem of Windows machines not being able to open up attachments from Macs using Outlook 2001.

The best workaround we found was to use the old Exchange prefs file from 8.2.2.

I presume that since the old client had more options regarding mime settings these are maintained under the old prefs file but the new client still uses them.

If you've had this problem, please let us know if this tip works for you.

Problem with encoding attachments

August 17, 2001 -- Scott Goodfellow noticed that when he sends Word 2001 to PC users with Word 2000 using Outlook 2001, the files arrive as Mac-encoded files, and the PC can't open it. However, the problem doesn't occur with Outlook 8.2.1. Goodfellow says:

Choosing Mime (or any other encoding option) doesn't make any difference.The file still appears (in Outlook 98 on NT4) as foo.doc.bin BUT (correctly) as foo.doc in Outlook 2000 on W2000. Outlook 8.2.1 (Mac) has no problems encoding Office 97-2001 files.

August 30, 2001
Shelley Le Roy

I can confirm this similar problem at my work place. We receive e-mail from government customers who use Macintoshes nearly exclusively. We have NT 4.0 and the standard Outlook, almost all attachments have the extra file extension of *.doc.bin for Word files. The files can be retrieved by converting them using Stuffit Expander on the Windows machine.

I have a Macintosh at home and have tried the different file formats for attachments but have never figured out the pattern. The problem has to be somewhere on the NT servers at work.

If the senders using Macintoshes send a copy to my Mac home account, I have not problems with the attachment. I am using Eudora 4.2 and lately 5.1 at home.

August 30, 2001
Pat Kelly

Can I guess that this affects emails sent to users outside the Exchange domain? I am currently involved with the implementation of the introduction of Exchange to a predominantly Mac site, am not a Windows guru but this issue cropped up already. My MS colleague who installed the Exchange server said that file encoding in Outlook is set at the server. He turned off the facility that allows users to send RTF files (about the only item of choice left to an Outllook user) and this issue was overcome. (I think - still testing - complicated by remote users who can still set how encoding is handled in their pop clients).

Running Outlook 2001 under Mac OS X 10.3.2; a fix and a problem. February 17, 2004 -- Regarding Panther's problem with Outlook 2001 seeing public folders on Exchange, reader Charles Killorin says "I can't see them either." However, Massimo Mauro has a suggestion:

The persons in trouble with Outlook 2001 in Panther must have just upgraded their computers (from 9 to X) and as a result Outlook 2001 does not run, because the parameters are no longer right. What one should do is instead to run the application "Outlook Settings" (under MacOS 9, but it runs under Classic) and rewrite all their settings. I can guarantee it works that way.

Mauro also has a problem with attachments with an older Exchange Server, Outlook 2001, and Mail:

We have an old Exchange Server (not even 2000 yet) with Outlook 2001 clients plus Mail.app clients (running under Panther). With this lethal mixture there seems to be no way to send attachments in a way recognized by both classes of e-mail clients. If the Panther Mail.app client send attachments as "Window friendly" then the Outlook 2001 will recognize it properly, but the reverse path does not work: one receives on the Panther Mail clients attachments embedded within a "MIME attachment" which have then to be peeled off by TNEF's Enough. This is a major pain in the neck.

As an IT professional I must say that the very limited configurability of Panther Mail (whose help details all trivia and explains no real hard issue) shows clearly that this product is far from mature and cannot be deployed in a corporate environment, even though it can talk with Exchange servers.

As we have reported before, TNEF's Enough is a Mac utility used for fixing attachments sent by Outlook for Windows.

If you've seen this or have a suggestion, please let us know.

Fix: adjust your extentions mappings

Two readers both say that making some adjustments in the File Mapping section of the Advanced tab for the Internet control panel will fix this problem:

JSeptember 19, 2001
John Wolf

When I first installed Outlook 2001 beta, Excel attachments would arrive to PC users with the .xls.bin name. If I recall, the problem was with the Internet control panel. Outlook 2001 appears to be even more dependent on the Internet control panel file mappings than previous of Outlook.

If I recall, the .xls file mapping wasn't right. Fixing it took care of the .xls.bin problem, and other PC users in my office could receive Excel files from me without problems again. (Before that I was launching Outlook 8.2.2 just to send them.)

If other users of Outlook 2001 have just specific file types that don't work, I'll bet the file mappings for those types are messed up.

JSeptember 19, 2001
A reader named Eduo

I saw this as a pending problem and thought I might provide some help. Outlook 2001 for the Mac now uses the Internet settings for encoding files to be sent. This means that if a file is defined as MacBinary in the Internet control panel it will be encoded (the method used by, for example, Interarchy, of checking if there is a resource fork and only encoding if it exists, is not applied here). This means that by making the Outlook 2001 client more Mac-friendly the developers actually added a new level of configuration to it that needs to be checked.

To fix this go to the File Mapping section of the Advanced tab for the Internet control panel and search for the doc extension, it may appear more than once (mine appear three times). You have to make sure that the appropriate type and creator are selected but also that in the advanced options part the part that says "binary data" is specified. If "Macintosh" is selected as the data type the file will usually be encoded to MacBinary.

You should do this for all of Microsoft's file types (from memory those would be .pps, .ppt, .doc, .dot, .xls, .xlt).

Another attachment problem with Outlook 2001: "Conversion to Internet format failed"

September 13, 2001
Matthew Smith

Since switching to Outlook 2001, we have the following problem. When sending emails with certain attachments (mostly jpeg files) to the Internet, the following error occurs and the message will not send:
Your message did not reach some or all of the intended recipients.
The following recipient(s) could not be reached:
Unable to deliver the message due to a communications failure
The MTS-ID of the original message is: c=US;a=;p=SCM;l=DILBERT-010830185035Z-2256

MSEXCH:IMS:SCM:SCM1:DILBERT 0x80070057 (00050311) Conversion to Internet format failed

I use a client other than Outlook 2001 for my local mail... it's Mac OS X's Mail.app. When I send the message from a user to myself from Outlook 2001 with certain attachments, it screws up the IMAP client. It doesn't show the email that has the attachments or any after it. If I log in via outlook 2001 and delete the offending email, suddenly all the emails show up again. This has got me baffled! The only workaround I've found so far is to put all of the files into an archive (.zip or .sit) and send that. It works, but I wish I could solve the problem as it is very troublesome for the user experiencing it.

Solutions:

September 14, 2001
Dr. Tom Hayes

I had the same/similar problem that reported the same error.

The problem turned out to be in the TCP/IP control panel. Basically the FULL server address/name was 'server.subgroup.domain.ie' rather than just 'server.domain.ie'

Within the Outlook setup I had used both the IP address and the full name and everything was configured properly, but return the quoted error whenever I actually went to use Outlook.

The solution was simple, I just had to add 'subgroup.domain.ie' to the 'search domains' in the TCP/IP control panel, in addition to 'domain.ie', and everything worked fine.

September 14, 2001
Luis Antezana

I've seen Matthew Smith's problem (9/13/01) before. It seems to happen only when sending more than one attachment in a message. I haven't given it the scientific top-to-bottom investigation as to the cause. I do know that simply sending one attachment per e-mail is a workaround to this problem. His note that putting all the files into a single archive file is actually the way to effectively send more than one attachment at a time, but then you're asking for some skill at the receiver end, too.

Your other users' problems (7/6, 7/17, 8/30/2001) with Outlook 2001 attachments are also familiar. There are settings on the Exchange Server to address this to some extent. Using the Exchange Administrator program, click on the "Connections" header under "Configuration" under your local post office, and then get Properties for the "Internet Mail Service" option. Under the "Internet Mail" tab there are many options that control the format of your messages and attachments. My server is currently set to send attachments in plain text MIME format, not HTML. There is also an "Advanced..." button which brings up a few more options. Here I have the "Send Microsoft Exchange Rich Text Formatting" option set to "User," as I expect the user to be aware of their recipients' capabilities for displaying RTF.

At the client level it is my hypothesis that it is relevant to deselect the "Always Send to this recipient in Rich Text Format (RTF)" checkbox in the e-mail address properties window. I have to admit this is untested. I only deselect RTF because I don't like to add layers of complication to my messages. I realize this may seem to conflict with my above statement that users should be able to select RTF if they like, but we're just demonstrating what is the base level to avoid attachment problems.

Finally, as we are all aware of the different servers and processes to which our e-mails are subjected as they make their way around the world, sometimes you just have to test which format works better with a particular recipient, using the Options button in the message toolbar and then the "Send Options" button after that to choose between UUEncode, MIME, BINHEX, and Don't Know for your attachment format. We have some clients whose e-mail clients/servers turn out to accept any format, some that can only take UUEncode, and some that can only accept MIME. If one has problems with one format, just try the next and then make a note so you always send to that person in the correct format.

Using these methods we do not have any problems sending attachments in Outlook 2001. As always, test these settings in your own environment - you may have reason to tell the server to always send attachments in UUEncode format, for example. What's key is to be aware of the options so you can find what works for you.

November 1, 2002
Laura Bryson

We have been experiencing the issue with "conversion to Internet format failed" for email messages containing attachments since moving to Outlook 2001. It was happening mostly on Outlook 2001 clients but sometimes on Outlook 2000 clients as well so it took a while to sort it all out.

We have finally traced the problem down to Macintosh characters (including spaces!) in filenames. We are running Exchange Server is version 5.5 SP4 on NT 4.0 SP 6a. All clients are either Win2K Pro w/ Outlook 2000 or Mac 9.22 w/Outlook 2001.

When a document is saved on a Macintosh with a filename not using 8.3 file naming convention, then any Outlook client sending the attachment to an external Internet mail account could (and usually does) receive this error. We are instructing users to rename the files using 8.3 filenames (document.doc, filename.pdf, etc.) when sending files outside. This usually resolves the issue in our environment.

Illegal characters in file names may cause Outlook attachment problems

April 5, 2002
Rob Thomson

Thought I should let you guys know of a solution I have found for the problem of mail messages sent from the Mac client getting jammed in the Exchange servers message queue.

The problem appears to be related to the way in which the attachments are saved prior to being attached to the email message.

A common habit on the Mac is to use the file names which contain illegal PC characters. e.g. 'Presentation 2/10/2000.' When sending mail from the Outlook 2000 client, the Mac client attaches the file happily, but the server just can't deal with the attachment name.

Remote access in Outlook for OS X

August 17, 2001
Diarmuid Mallon

I've got Outlook 2001 working under X. How the heck do I get it to work remotely? For the companies Windows clients, you can direct dial the exchange server, but it doesn't seem to work for X.

August 30, 2001
Peter Attanasio

In response Diarmuid Mallons problem with connecting remotely to an Exchange sever. I know that you have to set up a host file just like under OS 9 and I saved mine in the OS 9 desktop folder on OS Xs desktop. Then While you are Running OS X open the OS 9 TCP/IP control panel and select the hosts button and select the file you saved. You have to remember to put a blank line at the end of the host file or Outlook will crash.

August 30, 2001
Paul Lira mentions that his company has a web interface set up with the Exchange server:

We access mail via the web browser and a password keychain. We simply type in http://mail."company name".com and we are prompted with a user name, password, and domain.

A more detailed suggestion

September 4, 2001
Adrian Black

I actually use Mac Outlook:2001 under OS X to connect to my Office Exchange Server, and it works really well. I am not sure what Diarmuid is doing, but I will take you through what I do to connect to the Exchange Server remotely over a dial-up connection.

With Outlook:2001 itself, make sure that your Profile (the one you created when you installed it) is using TCP/IP for the connection, that "Connect with the network" is selected, and the "Choose the connection type when starting" box is checked (this will allow you to select Online/Offline on Startup). All of this can be found under the Services (found in the Tools Menu), Microsoft Exchange Server Service.

Next, I set up a separate Network Location (in OS X) for my Office's dial-up. This may not have any impact to the overall functionality, but I just find it easier.

Now, there may be one thing that is different here. When I dial-up to my Office's Exchange Server, I am not Dialing it directly. I am connecting to my Office's LAN (via a secure connection), and then running Outlook:2001 in OS X and selecting Online (in Outlook:2001) at startup. As I am using TCP/IP for the transport, and when I connected initially to my Exchange Server/Mailbox it was via TCP/IP (i.e., the IP Number, not the DNS Name), I connect to my Exchange Server without a hitch.

So, rather than Dialing the Exchange Server directly, see if you can dial-in to your Office's LAN, and then connect to the Exchange Server via TCP/IP.

A solution

May 2, 2002
Diarmuid Mallon

Well I've have some more time to play, and I found the following solutions:
  1. Set up Mac OS X (via Network Prefs) to dial up the Exchange server
  2. Outlook 2001 MUST be set up with delivery to your default Mailbox folders (set via preferences). Mine originally was set to deliver to another PST file (this was because our Exchange set up only allows 100 MB of mail in our Inboxes.). The Inbox must be configured to be able to be synchronized
  3. With Outlook NOT running, connect to the Exchange Server via dial up
  4. Start Outlook in Offline mode
  5. Now Synchronize, and you can send/receive mail

There are two problems with this

  1. The Address box refuses to synchronize
  2. When I'm in the office, connected to the Exchange Server via the network, Outlook is very unstable. However if I reconfigure mail to be delivered to my 'other' PST file, it is rock steady.

Outlook 2001 for Mac won't accept meetings.

September 20, 2001
Debby Garcez

I have one user who's not able to Accept any meeting. He can Decline but the Accept button is grayed out.

A fix:

September 24, 2001
David Hanke found a solution:

The solution [is] to remove his delegate and then re-add her.

He found the answer at the Mac Manager list web site.

Outlook 2001 crashing Classic in Mac OS X 10.1

October 2, 2001
Paul Lira reports this problem with Outlook 2001 in Mac OS X 10.1:

When you try to execute Outlook 2001, it starts up Classic but immediately force quits (bomb's?) Classic and of course, Outlook 2001. This all happens before the splash screen and login.

A number of readers responded, but there is no agreement: some readers see it, others don't.

October 4, 2001
Frank Born

This is exactly what happens. (Though classic is crashing on STARTING Outlook 2001 on my machine).

An anonymous reader describes the problem this way:

I have been using Outlook 2001 with OS X 10.04 and now 10.1 for the past 3 weeks. Outlook starts up fine but after a variable length of time it freezes and the only way I can close it is by using force quit and then it takes out classic. I had the same problem using outlook 8.2.

October 4, 2001
Greg Smith has better luck:

I've got 10.1 and Outlook running. Although I have had some crashes (without error messages) I can mostly get it to run. Sending this to you from it. I also would like to note that I didn't have to do anything special to get it to work.

October 4, 2001
Robert Croy:

I have been using Outlook 2001 since beta with all of the builds of OS X and now 10.1 5G64 and I have never had a crash of Classic caused by Outlook.

October 4, 2001
Steve Mitchell:

I'm running Outlook 2001 with 10.1 and have been since Monday. I have no such problem with it and it is on all day. I will, periodically have a refresh speed issue when it is in the background and the genie effect works, but that is minimal. Was using it with 10.0 before the update.

Log in works fine, mail notification works fine (icon bounces when mail or meeting alert shows. Cursor changes too), syncs folders and it hasn't failed once. Kind of wonder what he is working on.

October 4, 2001
Laszlo Kardos:

I have a Pismo 500mhz with 256 MB memory. Disk is partitioned for OS X and Classic. Runs Quark, Photoshop, Illustrator etc... to.

I have been using Outlook 2001 and Mac OS X 10.1 (Classic running Mac OS 9.2.1) for the last two days at work and have had no problems.

The trick to making Outlook work is to ensure that "hosts" have been configured. Under Mac OS 9.x that was done using a host file that was selected through the TCP/IP control panel. Under MacOS X hosts are defined in the NetInfo Manager by adding machines. I don't have the technical step-by-step, however I originally discovered the solution at MacWindows.

OS X 10.1 is working well. It is ready for prime time in a Windows-centric work environment.

One fix:

October 5, 2001 -- The reader who first reported the problem of Outlook 2001 crashing in OS X Classic, Paul Lira, told us that he has solved his problem:

I haven't pinpointed what bug was causing the problem. However, I deleted the Outlook 2001 folder and no Microsoft extensions and then reinstalled Outlook 2001. It worked! Since I didn't delete any preferences, it remembered my exchange server etc. Thanks for the posting! It's nice to know it is a bug and not incompatibility. All functions now appear to be fine.

OS X 10.1 seems to be okay

October 5, 2001
Ross Atkin

Just though I'd let you know about my experiences with outlook 2001, particularly in regards to it's stability in the classic environment.

I have been running outlook 2001 under classic for approx. 2 months, with varying results. With 10.0.4 and 9.1, outlook was relatively stable, only crashing every few days or so, usually taking the classic environment with it. The crash was always the same, the classic environment would freeze, and running process viewer would show that it was using approx. 70 percent of processor time.

When I updated to 9.2.1, the crashes increased in frequency, until Outlook was unable to stay open for more than about 10 minutes at a time. As an experiment I logged onto the server on both my Mac and my desktop PC, and discovered that Outlook 2001 was hanging when receiving email. I was just about to delete 2001 and start using outlook 2000 via Virtual PC, when I upgraded to OS X 10.1. Since Saturday I have been running outlook without a single crash! A well recommended upgrade!

October 5, 2001
Ed Dyer

For me, experiences on a PowerBook G3 and PowerBook G4. Outlook 2001 Beta worked fine with 9.1 classic and 10.0-10.0.?. Minimal crashes.

Outlook 2001 Final crashed occasionally with 9.1 and 10.0.?-10.0.4. Usually related to sleeping the classic environment.

Outlook 2001 Final crashed whenever left alone in 9.2.1 Classic for more than 2 minutes. Changing sleep prefs in the control panel had no effect.

Outlook 2001 Final crashed whenever it received a message in 9.2.1, no OS X. Very interesting.

Outlook 2001 Final crashed on first launch of Classic 9.2.1 in Mac OS X 10.1. Restarting classic worked. Has not crashed since.

October 26, 2001
Dr. John Chardine

In an earlier post I reported frequent system hangs running Outlook 2001 under Mac OS 10.04 Classic mode. I have recently upgraded to 10.1 and can report that with AppleTalk turned on (don't know if this made a difference) Outlook 2001 works very well with none of the previous problems occurring. I cannot offer a technical explanation as to why it suddenly works (can someone else?) but at this point I am just pleased that it does.

Incidentally, I have not experienced the Calendar crashing Outlook 2001 or Classic- as reported in other posts.

Outlook 2001 hanging with Time Zone in OS X Classic: problem and workaround.

December 5, 2001
Darryl Zurn reports another problem with Outlook 2001 hanging while running in Mac OS X Classic. He also provided a workaround:

I've been running OS X occasionally with Outlook 2001, and now since upgrading to 10.1 or 10.1.1 (I didn't use Outlook between the two upgrades!) I've been getting an odd hang.

Starting Outlook 2001 in OS X used to give a small dialog asking to set the Time Zone. That went away with one of the OS X upgrades, I don't remember which one, but now that dialog is back and won't take "OK" for an answer!

The dialog would pop up incessantly preventing any work from being done, and selecting any of the 4 dialog time zones (for Central time, either Central America, US Central, and 2 others) didn't make any difference, the dialog would pop back up within a second.

My solution was to reinstall the Outlook 2001 program and create a new profile. This seemed to fix the never-ending dialog, but I would be able to dismiss it after only 2 or 3 tries.

So reinstalling Outlook and creating a new profile seemed to help this problem.

Another suggestion

December 10, 2001
Daniel Foshee

I've seen the Time Zone error described in other posts... Also, I can start up the Exchange app, log on, and it will say the Exchange Server is unavailable, with a Cancel or Retry button. Hit the Retry button and it logs on.

It turns out that you have to go a bit further than just reinstalling and recreating a profile, although most might do this anyway; 'reinstall' means different things, perhaps.

When I deleted the Exchange Preferences and everything in the Exchange Profiles folder (found in the System Folder's Preferences folder; I suspect you could just throw away the Exchange Profiles folder altogether, or perhaps just the Profile Registry), and THEN double-clicked the newly installed Outlook, then both the Time Zone and Server Unavailable problems went away after I created a new profile.

Try OS 9.2.2

December 18, 2001
Jim Howard

It looks like from the simple tests that I have done, that Mac OS 9.2.2 fixes the problem of appointments showing up an hour early when running Outlook 2001 under Mac OS 9.2.2 Classic and Mac OS 10.1.1. This occured in time zones that never changed time zones (Arizona, in my case).

Outlook 2001 Calendar crashing in Mac OS X Classic

October 16, 2001
Tim Sismey

I'm running Outlook 2001 under MacOS X, 9.2.1 Classic and to start with, I couldn't get Outlook to work at all (it would open, load all my mail and then quit)....To start with, Outlook would crash as soon as it had loaded (I'd glimpse my messages for a second, and then it'd crash). I found that checking the 'encrypt information when using the network' box (in the Advanced tab of Outlook Settings) stopped this happening, and I could access my mail.

Now, I can use the mail side of things fine (although it is a little unstable - quits randomly), but if I go anywhere near the Calendar it will crash immediately. This includes if someone sends me an appointment, or if a reminder that is already in my calendar tries to execute.(But popup reminders appear to work OK now). 

The Microsoft newsgroup has one suggestion from someone who traced the problem to the Calendar information being kept on a different exchange server to Mail, but that definitely isn't the case here.

[This first occurred with OS X 10.0.4] I'm now running 10.1 and 9.2.1 Classic and I'm having exactly the same problem as I was before.

If you've seen this problem, please let us know.

Suggested fix

October 17, 2001
Luis D Antezana believes the answer is found in Microsoft Knowledge Base article Q223459, which he also believes is the key to upgrading Outlook 2001 Beta users without deleting or reentering Calendar data:

The answer to Tim Sismey's problem may lie in ...the MS Knowledge Base article that referenced the "/cleanscheduleplus" switches, etc. His problem seems to be similar to ones I've seen and repaired successfully using that method.

I can address Microsoft's claim that Calendar entries from Outlook 2001 Beta clients need to be manually deleted and reentered when switching to Outlook 2001 Final or problems could occur.

Although most everyone has undoubtedly made their switch from Outlook 2001 Beta to Final already, this info may be helpful to anyone experiencing trouble with Calendar data, which can be the reason for Outlook lockups on launch, busy dates not showing as bold, unavailable Calendar info when other users attempt to schedule meetings, and/or an "Unable to load free/busy information" error message.

To restore proper Outlook 2001 functionality, access the troubled Outlook account from a Windows machine. Using the "Run..." command in the Start menu, enter the filepath to the Outlook application followed by a space and then the /cleanschedplus switch, followed by relaunching with the /cleanfreebusy switch, and for safe measure I relaunch again with the /cleanreminders switch. (You can create desktop shortcuts for each of these three launches that included the switch command in them. There's probably a way to do all the switches in one launch!).

Using this process preemptively I have been able to successfully upgrade all my Outlook 2001 Beta users to Final without deleting or reentering any Beta client generated Calendar data.

Please refer to this MS Knowledge Base document for more information.

Configuring Hosts files in Mac OS X

Please see our Mac OS X Report page.

Problem with opening Office v.X attachments in Outlook 2001.

December 10, 2001 -- Jay Rolls reports an odd problem with Office X attachments in Outlook 2001 for Exchange Server:

With the new Office X, whenever I click on a Word/Excel/PPT attachment in Outlook, it properly launches the appropriate X based application, but defaults to a blank document. If I switch back to Outlook, click on the attachment again, it pops back to the open application and properly opens the document. Be interested to hear if any of your other readers have experienced such behavior.

September 16, 2002
Beth Tidwell

Same problem as posted by Jay Rolls. While running Outlook 2001 in Classic Environment, if I click on an MS office attachment and the appropriate Office application is not already running, the application launches and opens a blank document rather than the attachment. Once the application is running, it opens the document if I click on it again.

September 17, 2002
Chris O'Connor

If Explorer isn't running when I click on a URL within an Outlook email a dialog box asking for the location of the proper app opens. If Explorer is running the link works just fine.

Problem is fixed with Jaguar

September 17, 2002
Gary Panganiban

I used to see this problem with Mac OS X 10.1.5 or earlier. But once I updated it to Mac OS X 10.2, it seem to fix it.

September 17, 2002
Steven Turner

I had the same exact problem until I did a clean install of Jaguar and reinstalled Office v.X. Attachments open first time without a problem.

September 17, 2002
Oliver Tsai

I had the same problem, i.e. that if I click on an MS office attachment and the appropriate Office application is not already running, the application launches and opens a blank document rather than the attachment. Once the application is running, it opens the document if I click on it again. However, this problem went away when I upgraded from 10.1.5. to Jaguar.

Password changing problem

December 18, 2001 -- Costas Manousakis reports that he has see a problem with changing passwords with Outlook for Exchange Server. (We don't know of this is related a known problem with changing passwords for Windows 2000 Server.) Manousakis says:

We have this problem with the ability to change passwords on a Mac clients using Outlook 8.2.2 or 2001. Whenever it is time for users to change their passwords (it has expired, or new user and needs to change it for the 1st time), they are not able to change it. After they enter all information in the dialog boxes (username, domain, old password new password twice) they just get a response 'The NT domain password could not be changed. A required action was not successful due to an unspecified error.'

December 28, 2001
Gary Simpson

There are two articles that address this. Check out Knowledge Base Articles Q236111 and Q156182. I haven't tried these yet so I do not know if they will fix the problem.

The second of these articles says that a Registry edit is required.

December 28, 2001
Daniel Foshee has some other suggestions:

Costas might try one of several things:

1) Get the Server Administrator to activate the 'Allow users to change password on workstation' option. I *think* it's in the Services for Macintosh section of the 2000 file server, and there might be an similar option in the Exchange Server.

2) Make sure the server (regular server or Exchange) has the latest SP.

3) Install the latest MS-UAM client (up to version 5.9, methinks), instead of using Apple's User Authentication Module. This purports to be able to allow users to do what Costas wants, albeit on the domain level.

I'd like to point out that I'm testing the last option right now; I've already found that if you try to do it ahead of time, it doesn't work, so I'm waiting for my time to expire naturally, and see if a message pops up.

April 11, 2003
Sasha Kubis has a suggestion:

From experience and without having read any Microsoft Knowledgebase articles, I can offer you this. Mac users of Outlook 2001 cannot change passwords because of their lack of access to the 2000 domain; regardless of the fact that you are prompted for the domain. The best work around for this is to simply have the user logon through Web Access and change their password there.

April 14, 2003
Simon Gibbs adds his thoughts to the ongoing discussion of changing passwords with Outlook 2001 Mac:

It is possible for Mac users to change domain passwords through Outlook.

We have 120+ users using Outlook 2000 client connecting to Exchange 2000 SP3 in a Win2K AD domain. The users are forced to change passwords every 6 weeks and do so without any problems.

As long as the user has 'change password' permission in AD this shouldn't be a problem.

Additionally we didn't have any issues with Outlook 8.2.1 and Exchange 5.5 logging into a Win NT domain, which was the previous setup.

Non-network Outlook 2001 problem running in Classic

December 20, 2001
Scott Ackerman

Having an interesting problem with Outlook 2001. I am running OS 9.2.2 in Classic mode under OX 10.1.1. When I am in the office, connect to the network, and running Outlook online all is fine.

When I run Outlook offline, I have a problem. If I try to open an e-mail, by double clicking it or using the Open command, the system behaves as if it opened the e-mail but it is no visible. There is a selection for the open e-mail under the window menu, but I cannot see the e-mail. The same occurs if I try to create a new e-mail.

All else seems to work fine. I can successfully connect to our exchange server remotely. I can view e-mails via the preview. I have tried deleting the preference file. I have tried creating a new profile. I have tried reloading Outlook 2001.

January 4, 2002
Stewart Johnson

I have a very similar problem, although I don't think it's related to Mac OS X. Mac OS 9.2.2 seems to perhaps contribute to the problem though. Same symptoms, but as far as I can see is related to the program directory being damaged. On trying to open one of my mailboxes I get an end of file error, and from then on I can't see any messages. The mailbox highlights, but no messages are seen.

I haven't tried downgrading the OS yet, but am not absolutely sure that it is the crux of the problem.

Outlook 2001 Palm syncing solution

February 8, 2002
Matt Green

Just wanted to let you know that we found a solution that will allow Mac users to sync their Palm Handhelds to the Exchange server. A company called Extended Systems makes a server that interfaces with the Exchange database and allows the users to Hotsync through the Ethernet version of the Palm cradle. The server software is sold per license for 5-9 users = $249 ea. and 10-49 users - $209 ea. We have a few users who have Palm Vx units which don't have an Ethernet cradle, so a company called Port Smith makes a serial to Ethernet adapter for $169 that will allow each user to sync. This setup would also work for PCs but isn't necessary since the conduit is already built for the PCs and Outlook. This solution bypasses the Palm Desktop/Outlook sync completely and goes straight to the Exchange server.

If you've tried it, we'd like to know how well it works.

Moving emails with attachments using Outlook 2001 under Classic: antivirus software the problem?

April 19, 2002
Murray Miskelly

I am running OS X (10.1) with Outlook 2001

I receive a large amount of mail with attachments that are residing on a central Exchange Server. I want to archive them to a local folder with the intention of burning the local folder to CD. I can select multiple emails without attachments and drag them to the archive folder, but if I try with more than one message with an attachment I get an error "An Item could not be moved. A Client operation error occurred".

I have restarted in OS 9.1 but get the same answer.

I am sure that I could do this previously. I do not know if the installation of OS X is related.

I have tried moving the items to a temporary folder on the Exchange server and then returning them to my Mailbox with a rule active to say move to the archive folder, this doesn't appear to work. I can forward the message to myself, but again this has to be done per message.

If you've seen this problem, please let us know.

May 1, 2002
Richard Jenkins

We run a 14-server Exchange installation at our University. We use Norton's software to protect our server cluster from doing naughty things, but this also precludes moving multiple messages with attachments.

Apparently the virus scanning software has a problem with multiple scans, and the results are the same as Murray is reporting. It might be worth talking to his server admins and seeing if they have recently implemented something similar.

It affects all clients however, Wintel and Mac.

May 2, 2002
Brian Frobisher agrees the antivirus software does cause some problems:

Norton for Exchange causes all sorts of interesting stuff to happen. Try to create a .PST file for a user, you get all sorts of errors etc. It is a known problem and Norton has not done anything to fix it.

Known Bug: Iomega OS 9 driver slow down Mac with Outlook

May 9, 2002 -- Sonya Reasor reports that she was have a problem with Outlook 2001:

Outlook 2001 seems to cause abysmally slow typing in all applications after being open for a while. I've run across a few other people... I'm running OS 9.1 with 512 MB RAM.

She then followed up with the cause:

I finally was able to solve the problem yesterday. The issue was a problem with the Zip driver - not sure specifically what, but someone recommended that I try just inserting a zip into the internal drive. Amazingly, it immediately fixes the slowdown. We rarely use zips, so I could just leave it in there, but I imagine that an updated driver will fix the problem. I'd been using Iomega Driver v. 6.0.8 (created 12/11/00).

May 10, 2002 -- A number of readers verified this problem. Mike McDuffy sent us links to Apple articles on the problem:

We've seen this problem on a B&W G3 running Mac OS 9.1 and the internal Zip Drive but Outlook Express is being used instead of Outlook.

The AppleCare Knowledge Base has an article discussing this slowdown (article 106742). They also have one discussing jumpy pointers when copying to or from a Zip disk (article 106534) and audio skipping when copying to or from a Zip disk (article 106533).

The Apple article says the problem only occurs with the Mac OS 9 Zip driver, not in Mac OS X:

The Mac OS 9 Zip driver can cause the Finder to perform slowly when there is no Zip disk in the internal Zip drive. Iomega is aware of this issue and is investigating possible solutions for Mac OS 9 Zip software.

Suggested fix: downgrade drivers

May 14, 2002
Thomas Koons

The fix I have read which also worked for me was to downgrade Apple's CD/DVD driver from 1.4.7 to 1.4.3. This older version does not have the slow down issue and does not seem to cause any other problems.

Some how Apples CD/DVD driver and Iomega's Zip drivers affect each other and downgrading Apples CD/DVD driver fixes it.

[The problem] seems to happen only when your computer has gone to sleep and then you wake it. It happens in many MS apps. Entourage feels it pretty bad.

May 17, 2002
Bill Dobbs verified the fix:

I'm running a beige G3 tower with Mac OS 9.2.2. Experienced the same typing slowdown (as reported by others) while running MS Entourage after waking the Mac from sleep. Downgrading the Apple CD-ROM driver to 1.4.4 and the Iomega Zip Driver to 6.0.8 seems to fix the problem. No need to upgrade to OS X as Apple's site recommends.

TIP: Outlook/Exchange 2001 under OS X/Classic and recurrence and time zones. June 12, 2002 -- Jim Howard reports this issue and a work around for Outlook 2001 running in Mac OS X Classic:

Using the Outlook for Exchange client, anytime you create an appointment with recurrence in a time zone without daylight savings (Arizona for example), the appointment is created an hour earlier than what you started with. Each time you update and save the appointment without specifically changing the appointment time, for example changing the reminder time, the appointment shifts an hour earlier each time. Works OK under 9.2.2 and from web access to Exchange. Appointments without recurrence seem okay.

There's also a discussion above of an issue with time zones and Outlook hanging (along with workarounds).

September 9, 2002
Jim Howard

The problem of "recurring" calendar appointments in time zones without daylight savings was not fixed under Mac OS X 10.2, Classic 9.2.2. One-time (nonrecurring) appointments seem okay. Any change (including the initial creation) of a recurring appointment causes it to appear an hour earlier on the schedule. It's not clear where the problem lies (Apple or Microsoft).

Appointments did work okay for a while when Mac OS 9.2.2 was introduced (under Mac OS X 10.01) in December 2001. I didn't test recurring appointments under that earlier combination. They stopped working in June 2002 when 10.04 or 10.05 was introduced. The version of Outlook (2001) was the same. So is Outlook incorrectly getting/calculating the time/zone from the OS or is the OS providing the wrong time? Hard to tell without the source code. Even setting the second time zone in the EDIT, Preferences panel gives inaccurate times (Panel shows Pacific and Arizona as being different, main calendar display the same). Appointments coming from PC Outlook and the Web (from either my own account, or other coworkers) are off by an hour. I've deleted all the preferences, reinstalled Outlook, and checked the default time zone/daylight savings configs. We've been fighting this for a long time.

If you've seen this problem, please let us know.

Microsoft Outlook 2001 yields invisible buttons.

July 10, 2002
Mark Read reports a problem with Outlook 2001 on Mac OS 9.2.2 on some systems, which he says is a known problem:

After installing Microsoft Outlook 2001 onto system 9.2.2 on our new flat-panel iMacs and Quicksilver G4's, I noticed that all the "on" radio buttons were invisible. This is both within the "Outlook Settings" control panel and the actual Outlook application. Microsoft Australia, Apple Australia and Microsoft U.S. have all been able to reproduce the problem and are looking for a fix. Our old CRT iMac's running 9.2.2 didn't have this issue.

If you've seen this problem, please let us know.

July 12, 2002
Simon Gibbs

Just to confirm the invisible radio buttons. I'm running a Quicksilver G4, OS 9.2.2, Outlook 2001 Build 1808 and any radio buttons that are selected in the pref panels appear invisible. Those that aren't selected are OK.

Almost all of the Macs I look after - approx. 200 - running 9.1 don't display the problem

July 12, 2002
Daniel Foshee

We're running OS 9.2.2 (not Classic, and not OS X) on QuickSilvers and see this problem, but also on Graphite DP G4s. Sometimes a complete clean install (make sure you remove the profiles and preferences in the System Folder) will fix it, sometimes not. I've applied all OS 9.2.2 updates and it doesn't fix it.

July 12, 2002
Chris Drosos

We are experiencing the same issue with our QuickSilver 2002's running 9.2.2...

July 12, 2002
Michael Dixon

I have seen this bug frequently with Mac OS 9.2.2 on various Macs, including new PowerMac G4 800 MHz models and the cheap Mitsubishi Diamond 73 17-inch CRT displays that Apple sells. Outlook 8.2.2 doesn't have this problem.

Nvidia graphics cards appear to be the common link

July 12, 2002
Ted Brown

We have the same problem here for any G4 w/ an NVIDIA card. G4's w/ ATI cards and PowerBooks do not have the problem. Since I use the same base image, I'm laying the blame on the NVIDA video driver. Upgrading to the latest NVIDIA drivers doesn't solve the problem, nor does deactivating the ATI drivers.

July 15, 2002
Nick Pitman

Well known problem here. We have G4/450s and G4/933s both running 9.2.2 and problem only exists on the 933s. I too think is a NVIDIA video card problem.

I expect either a new video driver or a (long awaited) service release of Outlook 2001 will fix this problem.

July 15, 2002
Steven Blackwell

A somewhat similar problem was reported at least 18 months ago in FileMaker Pro 5.0v3 with fields formatted to display as radio buttons becoming invisible. The workaround was to switch to check boxes, with validations--if needed--to prevent multiple entries.

NVidia cards were the common element here.

Workaround

July 17, 2002
Derrick Lloyd found a workaround for the problem. However, the workaround causes another conflict with Retrospect backup software. Lloyd also confirms that NVidia graphics card is at the root of the problem, specifically an NVidia extension file:

I have been working with this issue for about 3 weeks now, here is what I have found. This is a display issue. The radio buttons within the Outlook Settings control panel, as well as the dialog message used to either open or save an attachment file are functional, just displayed incorrectly. Whatever button that is selected is invisible. The problem is absolutely related to NVIDIA extensions and more specifically the "NVIDIA 2D Acceleration" extension.

Renaming the NVIDIA extensions or just the "NVIDIA 2D Acceleration" extension so that they are loaded into the system first corrects the Outlook Setting control panel display issue. However, this workaround creates another issue if you are using Retrospect as your backup program of choice, at least under a network backup scenario. On shutdown the system now freezes at the Retrospect screen saver message. Neither of the choices "Restart" or "Shutdown" are functional. I have tried also changing the order of the Retrospect control panel as well, without success. I have also applied the new "nVidia_Driver_Update_3.0" patch, which did not correct the display issue.

If you have G4 Tower systems that come with the ATI Radeon 5200 Dual Graphic cards, this should not be an issue.

Outlook 2001 fails in Jaguar

Problem:

October 21, 2002 -- Michael Wilmar saw Outlook 2001 stop functioning when he upgraded Mac OS X to v10.2:

I have just upgraded to Jaguar and I cannot get Outlook 2001 to work in Classic mode. It will not connect to Exchange Server. It worked fine under 10.1.5 and when I boot into 9.2.2. All other functions work fine in 10.2. Have trashed Outlook Preferences, Profiles and everything else. Have followed instructions to create new "Host" file using Netinfo Manager. Nothing works.

Suggestions:

October 23, 2002
Nick Rubery

Had the same problem with one of my office iMacs, struggled for a week trying, periodically, all the options I could think of. Eventually, backing up data, Mac OS 9, wiping the disk and reinstalling Jaguar solved the problem. Odd, deleting the profiles, prefs at al didn't do a thing. It only happened on one out of 10 machines so far.

I find running Disk Warrior vital after an exercise like this.

Outlook is tolerably stable under Mac OS X 10.2, providing the network connection is clean and you set the mailbox up to download mail to the client's machine.

October 23, 2002
Dan Foshee

I just recently had a problem with getting Outlook 2001 to work on a dual 1 GHz "Mirror" G4 (running Jaguar, but also booting OS 9/Classic on a separate partition in addition to Classic being on the Jag partition, which was the primary/first partition). It would start up just fine, but replying to or sending a message would cause Outlook to quit. I too would completely trash the Profiles, Preferences, everything related to Exchange and Outlook, but still the behavior in both OS 9's and OS X.

After I completely trashed and emptied the Trash can, I booted into OS 9.2.2 on the OS X partition. I then installed Outlook, rebooted still in OS 9.2.2 and configured Outlook. The problem disappeared. Once I was satisfied with the setup on that partition, I did the same with the second OS 9 partition. Problem gone. Then I switched the boot OS to Jaguar, and once Classic was fired up, activated Outlook. The problem was gone.

October 23, 2002
Paul Gorski

I have Outlook 2001 and Jaguar 10.2.1 running on two G4 466 computers with 384 MB of RAM. (That is, Outlook runs in Classic.)

If you have a user having a problem, I would make sure that Outlook is configured to use TCP/IP as opposed to AppleTalk as its network protocol. (And double-check to make sure you've properly configured your Exchange "machine" in NetInfo Manager on the client Mac.)

A fix and confirmation

November 1, 2002
Peter Attanasio

I had this same problem after updating to Jaguar. After booting into OS 9, I found that the TCP/IP control panel defaults to Classic. Resetting this to my previous configuration and then booting back to OS X fixed the problem.

November 6, 2002
Michael Wilmar

Peter Attanasio had the right answer. Apparently, Mac OS X creates new TCP/IP settings for the Classic mode. Somehow they work for the most part, even though they are not the ones that had been in use previously. Resetting them worked exactly the way Peter said they would.

The TCP/IP settings that OS X creates for Classic appear to be based on the settings one creates for OS X. The problem is that even though one sets up TCP/IP settings of OS X that use DHCP, etc., when they are carried over to Classic, all that goes away; existing TCP/IP OS 9 configurations are ignored; and a new TCP/IP manual setting is created in addition to the existing OS 9 TCP/IP configurations. For some reason this manual setting was good enough to get me to the Internet and to other places on our network but not to Outlook.

Alternative to Exchange client for Mac OS X for the Unix savvy?

December 2, 2002 -- Ximian's Evolution is a client for Microsoft Exchange for Linux/Unix that the company says is an alternative to the Outlook client. Unfortunately, there is no Mac OS X version, but the company says that with some effort, it can run on Mac OS X:

Evolution will compile and run on Mac OS X if you have an X server and the GNU developer's toolchain installed. This has been done and is reported to work quite well.

This isn't exactly a trivial task. Fortunately, reader Adrian C. reports that there are detailed instructions on installing X, GNOME, and Evolution on OS X. The instructions were written by someone at Ximian.However, as the reports below show, there is still one missing piece for Mac OS X the prevents Evolution from being used as an Exchange client.

December 4 2002
Aaron Weber of Ximian, Inc., reports:

Theoretically, it would work. However, we don't ship Ximian Connector for OS X, so the answer, I'm afraid, is that no it hasn't really been tested and is not an available alternative to Outlook on Classic. We have considered shipping Evolution/Connector for OS X, but are unlikely to do so in the foreseeable future, due to support and engineering constraints.

December 4 2002
Santino Rizzo tried it, thought it worked well, except for the fact that it won't work as an Exchange client:

I've installed GNOME and Evolution using Fink under Jaguar. If you follow the instructions posted and have a lots time (days) to kill while you wait for it to compile it works flawlessly. One problem is you can't use it as an Exchange client. The Exchange Connector is proprietary code so you can't get the source and you have to buy it from them - if they ever compile it for OS X.

December 4 2002
Ted Brown expands

Alone, Ximian's Evolution is not a a client for Microsoft Exchange, rather it is an open source messaging client with similar features to an Outlook client implemented using open protocols.

You can connect Evolution to an Exchange Server using Ximian's Connector For Microsoft Exchange.

This software is not open source, so cannot be ported by the end user, only by Ximian. So, right now, there is no way to get Evolution to work as a full fledged Exchange client for Mac OS X.

From the FAQ ():

Q: Can I get the source code for Ximian Connector?

A: No, Ximian Connector is a proprietary software product. It will be offered under a different license than other Ximian products. That license is available here.

Without the connector, you can connect to Exchange servers w/ IMAP (but so can any other IMAP client, including Mail.app) and I'm pretty sure the calendaring functions do not work.

Evolution itself is open source, so work can be done to make sure that w/ X and Gnome installed, Evolution compiles and runs normally. Then, if there is interest, Evolution could be ported so it didn't require X (this is probably a significant project). In any event, interest in Evolution running on Mac OS X is the best way to convince Ximian to port the Connector to Mac OS X. The Connector is probably fairly easy to port if the rest of Evolution is running.

Just though that people should know the score before spending oodles of time to end up frustrated. If you know the score first, you know what you're in for. Getting Evolution to run is probably a worthwhile project in itself.

December 20, 2002
Alex Priest

I just saw your report on Ximian Evolution and Connector, including Aaron Weber's (Ximian) comment [that Ximian doesn't ship Connector for OS X, so that Evolution could no be used on OS X with Exchange Server].

I spoke to Nat Friedman, Ximian's cofounder at a conference recently and asked him about the possibility of a Connector port. I mentioned that my organization had about 500 Mac users in the process of migrating to OS X. He said that 500 users was enough to warrant porting Connector. Even if I could not drum up the funding for a contract, I would think it would be fairly easy to wrangle 500 customers for such a port.

The problem is Evolution itself. Is Evolution under X11 any better than Outlook 2001 under Classic? So far I have not seen any significant advantage. What we need is a Cocoa port of Evolution. Classic chicken-egg problem: Ximian needs demand to port Connector and users need natively GUIed Evolution to generate that connector demand. But without Connector, porting Evolution isn't that compelling a project.

Utility converts Mac, Win Outlook contacts for Entourage 2001.

December 2, 2002 -- An Applescript called Export-Import Entourage 1.2.2 (US $12.50) by Paul Berkowitz can move Contacts, Calendars, Tasks and Notes to and from other PIM programs on the Mac and Windows. It also imports "Outlook-type" CSV files from Windows.

Reader John Glasgow wrote to say that "it works flawlessly."

December 4, 2002 -- Brian Platts has a follow up report on Export-Import Entourage 1.2.2 for importing contacts into Entourage from Outlook. He says that an upgrade to AppleScript fixes Microsoft freeutility that does the same thing:

Hi John...thanks for posting the information re " Paul Berkowitz Utility converts Mac, Win Outlook contacts for Entourage 2001".

A couple of points however...

Having downloaded the AppleScripts, I found the answer to my original question as to why the Microsoft utility no longer worked under 9.2.2. In the Berkowitz Read Me, there is an instruction to update AppleScript to 1.8.3. I did this and the Microsoft utility worked again!

Also, you state the price of the Berkowitz utilities as $12.95. In fact, it's now $20. No big deal, but worth mentioning if one only needs to import contacts, which can be done for free if the Microsoft utility is used.

Winmail.dat files on Macs from Windows users

The DataViz web site has an article about Mac users receiving attachments named "winmail.dat" from Windows users running Outlook for Exchange. These files consist of either the RTF text formatting information (bold, italics, etc.), which can be discarded, or are an actual attachment combined with the RTF formatting data of the e-mail message. DataViz recommends having the PC user turn off RTF in Outlook, and describes how do to this in the article.

Fortunately, there is a fix on the Mac side: TNEF's Enough, a free utility that can decode these files.

On Decemember 16, 2002, Martin Forrester says that it "handles winmail.dat files perfectly in my experience." Jonas Maebe also said it works well.

Outlook 2001 problem with Address book drop down menu.

March 12, 2003
Tony Perialis

I'm having a problem with Outlook 2001 Mac and Exchange 5.5 on Win 2000 Server.

The menu will not "pull down" so that I can select Contacts, Personal Address book, or Global Address book. Basically the drop down menu has become static.

This started happening after the Exchange Server computer was upgraded to Win 2000 from NT. Never had this problem with NT. Nothing was done to Exchange Server software.

March 14, 2003
Tony Perialis told us he thinks he found the answer to the problem in a Microsoft knowledge base article called Outlook for Macintosh May Lose Connectivity.

March 14, 2003
Peter Durkee suggested this:

Since the Personal Address Book and Contacts are considered services in Outlook, maybe they were somehow lost when the server was upgraded. Tony should go into Tools -> Services to see if they're still listed there along with the Exchange server.

For what it's worth, I'm using Outlook 2001 with Exchange 5.5 on a Windows 2000 server, and it works fine for me.

March 14, 2003
Kelvin Tsang had this suggestion:

We never have this problem. We have our Exchange 5.5 running on a Win 2000 server for 1.5 years and everything is fine. The difference I can see if we do a fresh install of Win 2000 and Exchange 5.5, not an upgrade from NT as Tony pointed out. That could be the culprit.

March 17, 2003
Leigh Chambers

We look after the Macs on behalf of a large company and have recently suffered exactly the same problems as Tony Perialis. Unfortunately we do not have access to the Exchange Server, as this is managed by the internal IT team. We are assured that no changes have been made to this server, which is running NT4 and Exchange 5.5.

However, every Mac on the network is suddenly having the Global Address and Personal Address problems. From the Microsoft technote Tony posted, our problem would point to the first cause of too many address book views set up on the server, as the chances of dozens of Macs simultaneously running out of resources seems very unlikely.

Identification of problem

March 21, 2003
Leigh Chambers

Just to confirm that our problem was caused by the accumulated address views on the various Exchange servers, as we suspected. The Macs now have working address books again. Here's hoping this is resolved with the to-be-released Exchange-compatible Entourage!

Problem with Outlook 2001 hanging in Mac OS 9.2.

April 11, 2003
Sasha Kubis

I currently have over 50 Mac users on 9.2 who have been using Outlook 2001 to access their exchange mail. All of them intermittently report Outlook freezing on either launching or after they've left their machine for several minutes. The first scenario is when a user first comes in, fires up their machine, and launches Outlook. They will type in their password and hit enter and Outlook will just sit there thinking. It will never time out or produce any sort of error, just simply sits there. It can be force quit and the user can continue working on anything else. If they try to launch Outlook again the same thing will most likely happen. On some occasions it will successfully launch. If however the user launches another network application in the mean time such as IE or Netscape and establishes a network connection first, and then launches Outlook again, it works like a charm. The second scenario is identical but involves a user waking the computer up out of a sleep. If the machine had Outlook open, Outlook will just not respond and will need to be force quit. If Outlook was not open, then it will have the same hang on login. Once again, establishing a network connection with another application fixes the problem.

Unfortunately telling 50 Mac users that they always have to open and then quit IE *before* they use Outlook is not a good solution. Please assist.

Suggestions

April 14, 2003
Guy Masson

I see this similar problem on my network of over 100 Outlook 2001 users. What I have done is change the way Outlook retrieves mail for users that have this issue.

In the Outlook preferences panel, choose services. Select the Microsoft Exchange Server properties. Select the advanced tab and select the check for changes box. I've made an arbitrary choice of either 120 seconds or 180 seconds.

This seems to have resolved this issue - or at least made it a non-issue.

FYI - all of my users connect via TCP/IP as opposed to using AppleTalk.

April 14, 2003
Paul Gorski

Regarding Outlook 2001 freezes on login or after sleep under MacOS 9.2.2:

I've seen similar problems, as described by one of your readers. I've had better luck with Outlook connecting via TCP/IP. And if your reader is connecting via TCP/IP, I suggest they look at the MacOS 9 TCP/IP control panel (in Administrator mode), OPTIONS... and leave "Load only when needed" UNCHECKED.

April 14, 2003
Walter Zrzavy

I had the same problems with Outlook. I corrected this by changing from AppleTalk to TCP/IP in the Outlook setting. This requires a correct DNS entry for the Exchange server, and on the client a domain suffix in the TCP/IP control panel.

If you've seen this problem, please let us know.

Problems with Outlook Web Access with IE 5.2

April 18, 2003
Jay Craft has seen problems with Outlook's web access in Mac OS X, but not in Classic or Mac OS 9:

At my company, some users are getting an "access denied" message when trying to use Outlook Web Access (on Exchange Server 2000). This is when they are using IE 5.2 under OS X. Interestingly, using their same login credentials when booted in OS 9 or from IE 5 in Classic works fine. Also- on the same Mac, you can log on with another user's logon credentials and get in fine. So it seems to be something strange with certain user accounts, that only causes a problem when logging in with IE 5.2 under Mac OS X.

Suggestions

April 22, 2003
John Jarrard

We have had a similar problem in the past... Here's what we did to fix it... It turned out to be a weird thing with NTCR Authentication. You have to make sure your time zone, date, and time are properly set. Buried deep in Microsoft's tech support we found an article verifying that the time and date are facts in the authentication hash algorithm. It seems as though it is not always the case, whereas some people could get in with no problems at all... even with the date set to 1970.

April 22, 2003
Luis Antezana:

One way to solve the "Failed to get Inbox" error message is to quit the web browser and reopen it for each new OWA user who needs to log on, rather than simply choosing OWA's "Log Out" icon. Perhaps this technique might help Jay Craft with his "Access Denied" messages. The fact that log-ins can succeed with other users and from Classic shows that the other important factors seem to be in place for accessing OWA.

On an unrelated note: has anyone had any trouble opening Office attachments directly from Outlook 2001? (not that we'll have to worry about this for much longer :) We're having some inconstancies in that area with one of our machines, and it happened before the 10.2.5 update. I have a feeling it's related to old or bad fonts, but I wanted to check with the community, too.

April 22, 2003
Peter Dodge:

Jay Craft may not be aware that Mac users must specify the domain by prefacing the username with the domain name. He should try <domain>\<username> in the user's name field when logging in.

April 28, 2003
Chris VanNess

We were not having this issue until our Exchange admin rebuilt our OWA server. Since then we have had several reports from people getting the "error: Access Denied" message when trying to authenticate. I have actually been able to recreate the problem and find a temp fix for it. I reset the users password using "Active Directory users and groups" (on a Windows machine) and the user was able to access OWA. Once the user changed their password using their Mac OS X machine, they were denied access again. I have seen weird password issues like this before, but for the life of me, can't remember enough about them to give anymore info.

Outlook Web Access and VPNs

April 23, 2003
Brian Frobisher

We are using a Cisco VPN concentrator and NT servers here at work.

All my Macintosh users must create their passwords on a PC or the server for them to be authenticated for Web Access or VPN access. People who create passwords using Apple UAM's are not accepted properly either for Web Outlook access or VPN connections.

August 25, 2003
Craig Hesson

My school district is experiencing the same problem as reported by Jay Craft on April 18, 2003. Some users are getting an "access denied" message when trying to use Outlook Web Access (on Exchange Server 2000). This is when they are using IE 5.2 under OS X. Using their same login credentials when booted in OS 9 or from IE 5 in Classic works fine. On the same Mac, you can log on with another user's logon credentials and get in fine. So it seems to be something strange with certain user accounts, that only causes a problem when logging in with IE 5.2 under Mac OS X.

If you have a suggestion, please let us know.

Exchange patches and Web access

May 16, 200
Tony McArthur notice a problem with Mac and Windows Outlook clients when he updated Exchange server:

Our techs have installed the latest patches from Microsoft onto our Exchange Server. Since then, we are only able to access Outlook via Internet Explorer. This hold true for Windows machines and Macs. The server insists on the viewer specifying the domain. We can find no way of doing this in other browsers. Apparently this is an additional security feature. I have tried a number of "tricks" like domain\user but nothing has worked. It is not a huge problem but it is annoying. I believe that Outlook 2003 will use a browser interface so we might have this problem for some time.

May 20, 2003
Payman Parastaran offers a fix and an explanation. He says it is an issue of NTLM authentication:

I believe what Tony McArthur is saying is that the only browser that can be used after applying the Exchange patch is Internet Explorer rather than not being able to use the traditional Mac or Windows Outlook client. This is most likely due to the authentication mode setting within IIS or the Exchange Server application changing upon patch application from requiring basic authentication to one of requiring NTLM authentication. The only browser that supports NTLM authentication under Windows and Mac OS is Internet Explorer.

Simply changing this setting will restore previous functionality. As long as the OWA (Outlook Web Access) server is on the same domain as the Exchange server (or even the same machine), it should not be necessary to specify the domain in the form of typing "domain\user" as the username.

Outlook Mac can't see Exchange 5.5 Server.

The Problem

June 5, 2003
Jeremy West has a problem with his Exchange 5.5 server -- none of his Macs can see it. He has hosts files configured.

We've got a strange Outlook problem.

Last night we took our Exchange 5.5 Server (NT4 ) offline for a couple hours and the file msvcrt.dll was replaced because of a software compatibility issue with Netback 4.5 and Exchange 5.5. Since this morning every Mac Outlook 2001 client on our AD network gets an error saying "The Specified Microsoft Exchange Server is unavailable or a connection cannot be established."

When I try to create a new profile and test the settings I get the same error. We have host files configured for all of our Mac clients that points to the correct server on the network, but Outlook still cannot access the server. Outlook Web Access can connect successfully from the Macs and we are using that as a temporary fix. We have another domain on our network with its own Exchange 2000 Server and all the Mac clients can connect to that server without issue. Our DNS info looks good and we are running DHCP on the network.

Using my Network Utility app in OS X, I was able to ping the server by IP address but not by the Fully Qualified domain name. I resolved that issue by adding an entry into the Host info in NetInfo Manager following the steps I found on your site, but Outlook still will not find the server. I didn't have any problems pinging servers by their FQDN on the domain that has the Exchange 2000 server. None of the PCs are affected.

This message showed up during the reboot last night:

Source MSExchangeSA

Event ID: 2042

Unable to get the AppleTalk network address of the Microsoft Exchange Server computer.

I can't seem to find any info in Microsoft's Knowledge base about this error, but I can't figure out why it would matter. That server isn't running any AppleTalk services and our clients connect using TCP-IP.

June 11, 2003
Rick Hardin

I happen to be having the EXACT same problem with a client's Exchange Server 5.5 installation. After an Exchange Server 5.5 restart one night THE Mac in the network would no longer see the server. The Mac is running 10.2.6.

I did the Net Info Manager entries and can ping the server even using the Exchange server name of "nt_server" (after NetInfo entry)...With Outlook 2001 I could never get the program to see the server. I have since installed Entourage X (included with Office X). After changing the config around I got it to work using the IP address of the server, not the name. Everything started to apparently work when all the messages started to sync with the server. We did a few comparison with the messages and determined that it was all correct. After getting the contact with the server we tried to send an e-mail to a coworker and it worked fine. The coworkers email is in the same domain. We tried an email to ANYONE outside and no go. It always came back with the message "Relaying Prohibited 5550" or something to that effect. The Exchange server thinks the mail is coming from OUTSIDE the network somewhere.

The problem I am having now is I can't get the clients email to email out to anyone other than the same domain. I have talked with the Admin and tried to allow relaying through the appropriate port (I forget which one), but he has it restricted for the domain as a whole. He is not very open to reconfiguring all 4800 users to make one port exception on her IP address.

June 11, 2003
Kenneth Saxe

We are experiencing a similar issue. We have a brand new Dell Power Edge Server running Windows 2000 Small Business Server (including Exchange 2000). SP3 and all the latest service packs have been applied. TCP/IP is the only protocol running.

The Server and Windows-based workstations can access Exchange via Outlook or Outlook Web Access. However, the Macs cannot access Exchange via Outlook or Outlook Web Access. The Macs can access a shared MacFiles folder stored on the server.

Suggestions

June 11, 2003
Jeremy West

Here's an update on the Exchange 5.5 issue we were having last week.

Our network engineers were able to fix the issue last night. They found that our Veritas Netbackup 4.5 software that was installed last week replaced a system file called msvcrt.dll with an incompatible version that conflicted with Exchange 5.5. Originally, they just renamed the dll file and copied the original back in the same directory only to discover that the system was still using the incompatible dll even after it had been renamed. Once they deleted the incompatible dll from the directory and restarted the server all of our Macs can once again resolve the name of the Exchange server in the Outlook Settings.

June 11, 2003
Glenn Perez

I don't know if this the same problem but I found that when running Outlook Client for the Mac in Classic while running OS X. The Outlook client software could not find my Exchange Server 5.5. The fix was to boot in OS 9.xx and to select the host file in the TCP/IP control panel.

This control panel must be set to the Administration mode which is done by going to the Edit menu and selecting User Mode. Once you have selected your host file while still in OS 9.xx setup you Outlook profile using the Outlook Settings control panel. After finished configuring an Outlook profile boot back into OS X and Outlook client for Mac will now see and work with Exchange 5.5. I hope this helps

June 11, 2003
Jim Trikakis

I suggest registering DNS registering the exchange server, Using DDNS won't work, it must be BIND registered.

June 11, 2003
Peter Dodge

I can't tell from his post, so Jeremy West may have already checked this, but he should probably make sure the Outlook client settings and make sure they are set to connect via TCP/IP and not AppleTalk. It's not enough to just connect the workstation via IP, the Outlook software needs to be configured for IP as well and overlooking something like this is easy to do.

June 11, 2003
Dedrick Allen

Sounds like Jeremy could have a DNS issue. Make sure the Mac's are getting the IP addresses of your DNS servers that service the domain with the Exchange 5.5 server. Make sure DHCP is giving out that info upon request for an IP.

Then use MacPing from one of the Mac's with the problem and ping the Exchange 5.5 server using the FQDN to see if it replies. If not, you still have a DNS issue. Make sure your DNS servers have an valid entry that points to your Exchange 5.5 server and that its up to date. Also when replacing a system file such as msvcrt.dll you should almost never replace it with an older versioned one unless your absolutely sure everything will still function correctly. Its usually pretty save to replace it with a newer version. Try putting the original file back and see if the problem still occurs.

June 12, 2003
Kenneth Saxe

By implementing the "hosts file recommendation" from the microsoft.com web site we are now able to see the Exchange server. However, when running Outlook 2001 for Mac, each time we reboot the workstation we have to create the profile in Outlook 2001 for Mac.

June 12, 2003
John Leonard

I have seen this problem several times (Mac OS 9.2). In fact I saw it yesterday when I got a call from a Mac HelpDesk user. I think you should get a "-1 error" message when it happens.

I believe it is a CONFLICT with another application running and not Outlook itself. If you notice:

1. All your Outlook settings are correct!

2. Even if you create a new Exchange account and new user properties, the problem will still exist.

The fact is, this unique problem is not really directly related to Outlook nor Exchange but the OS indirectly causes this problem.

What to do?

Well, there are several things;

1. Nothing! (hehe) Seriously!

For example, this problem occurred at a Mac client of mine around 5:30 pm so I asked her to TRY again tomorrow. She did, and it was able to access exchange this time! Problem SOLVED! I suspect that during this time, the OS internally resolved the conflict!

2. If you or the client is in a hurry, then try the good old Zap THE PRAM routine. ( during reboot hit the apple key and Option key and P and R key at the same time--You may need to call a friend over to hold down all the keys) Sometimes this can resolve it!

3. Well, the last resort is......

Since it is an internal conflict with Outlook and another unseen OS event, it is telling you that the OS is getting dirty (not the application).

Note: If you try to reinstall Outlook 2001, you will STILL get the same problem (that is because it is OS related).

Try Reinstalling the OS, not a clean install <OR> throw the preference file for Outlook in the System Folder ->Preferences folder.

The next time you run the program, it will build itself a brand new preference file that, if you are lucky, lacks whatever the corruption was causing the problem.

Again, don't spend too much time on the issue since if you leave it alone for a day, the Mac OS SHOULD resolve it. But if you keep getting the issue, it is giving you hints it is that time to do another CLEAN OS install on that machine!

Problems with Outlook 2001 Using Cisco VPN.

July 8, 2003
Michael Wilmar is having a problem with getting Outlook to work through a virtual private network connection:

I am running Jaguar 10.2.6. with Cisco VPN client 3.7.3(A). Everything working well except for Outlook 2001 when I try to send a message. Almost every time I get a "Trying to Communicate with Server Message" and eventually a time out. Otherwise all functions in Outlook working fine. Anyone else run into this problem?

July 10, 2003
Mark Stewart

Almost always, when I see a problem in a VPN tunnel, it is related to MTU. Have the user try the following [in Terminal] before opening his VPN tunnel:
sudo ifconfig en0 mtu 1400

(where en0 is the interface that the VPN traffic is flowing through- this is assuming Ethernet connectivity)

That should put his MTU low enough to allow for VPN and/or DSL overhead. Outlook can occasionally have other problems in a tunnel.

July 10, 2003
Mark Johnson

The problem described usually occurs with a slow or inefficient connection. The overhead of the VPN, Classic, and the Outlook client make it difficult to establish the connection. Sometimes it will work and other times it will not. I've seen this consistently over some DSL connections, but not others. In those cases where you cannot connect via the client, use the web interface or wait to see if Microsoft's Entourage support is any more robust as a native X client. BTW, might upgrade to the 4.0.1a client to see if it helps.

July 10, 2003
Michael Morris

I have the same problem, and have partially solved it by disabling any firewall software on my client computer before initiating the VPN connection. If you use an Airport base station, you will need make a direct wired connection to your ISP to bypass the Airport's built-in firewall as well.

I have had mixed results - network traffic makes a big difference.

July 10, 2003
Terry Knudtson

We've had the same problems here at my work. On the local network Outlook works fine. And sometimes we can even get it to work through VPN with dialing onto the net. But then the user will take it home and not be able to connect through DSL or cable modem. It just times out and won't connect. Even if you manually enter in the DNS info under OS 9, it still won't connect. We're pretty sure the problem is with Outlook running under OS 9 and the Cisco VPN client being OS X.

Now I haven't had a chance to fully try it with the version 4 of the Cisco client yet but I'm not holding my breath on this. We really need MS to finish the update to Entourage and get it working Exchange Server properly.

July 10, 2003
Bob Storey

I have a similar problem with Outlook 2001 client not able to communicate with the server only I have several Sonicwall SOHO3s VPN'd to a Sonicwall PRO 230. Outlook 2001 seems to lose it's connection to the server. I'm not sure which ports the Outlook 2001 client uses to communicate with the exchange server. Sonicwall tech support says I can "up" the timeout on the TCP session if I knew what ports were being used for the Outlook 2001. Upping port 25 doesn't help.

ALSO, I used Outlook 2001 with the built in PTPP client in Mac OS X and had problems connecting to the exchange server until I lowered the MTU from 1500 to 300. But other programs don't like the change, so I can't use the same technique with my Sonicwalls as I did with my single Mac OS X workstation.

Gary Simon
July 15, 2003

I was getting this same problem with my network at home. It turned out that when I switched out my 4 Port Router / Firewall (SMC Barricade) and replaced it with a D-Link (DI-804V), the problem went away. I could also reproduce the problem on another network just by installing the SMC router.

Richard Jenkins
July 15, 2003

We have had a bit of a discussion about this at my Uni, and there seems to be a lot happening with Ethernet frames once you add VPN and PPPoE. My info is theoretical at the moment as I don't have ADSL yet, and none of my staff/guinea pigs/testers have reported back with problems or otherwise.

The other posts seem to be on the right track, but I'm not sure how the OS X/Cisco VPN client handles Classic IP, so setting the MTU in Classic might be a waste of time. Cisco certainly seem to think their product changes the OS X MTU automatically.

In the meantime, here's a document I sent out to our Mac admins last week:

Problem: Sometimes Outlook doesn't work on home ADSL connections.
Environment: OS 9, Netlock VPN Client, ADSL.
Potential Solution: Use the Netlock MTU Reducer to reduce the MTU size.
Implications: ADSL network performance improves, Outlook can connect via the VPN over ADSL.
Exclusions: OS X and the Cisco VPN client are not affected. PPP is not affected.

Discussion: Some users may be experiencing problems with network performance/timeouts or failure of initial connections when using Outlook and the Netlock VPN over ADSL. There are a variety of reasons for this and not all of them respond to therapy. One might, however:

When VPN/IPsec and PPPoE are used the contents of the Ethernet packet changes. There is more stuff added in each packet, reducing the room in the packet left to actually transmit the data. If the amount of data in each packet exceeds the allowable size, the remainder is put into the next packet and sent as a fragment, to be joined back to the original at the destination - so you get two packets instead of one.

Consequently, sad things happen: the data has to be broken up and reassembled, and some fragments might not make it, requiring a resend. Some firewalls/ISPs don't transmit fragments so the information never gets there - the connection attempt fails or drops out when data starts transmitting.

Cisco says:

The maximum transmission unit (MTU) parameter determines the largest packet size in bytes that the client application can transmit through the network. If the MTU size is too large, the packets may not reach their destination. Adjusting the size of the MTU affects all applications that use the network adapter. Therefore the MTU setting you use can affect your PC's performance on the network.

MTU sizing affects fragmentation of IPsec and IPsec through NAT mode packets to your connection destination. A large size (for example, over 1300) can increase fragmentation. Using 1300 or smaller usually prevents fragmentation. Fragmentation and reassembly of packets at the destination causes slower tunnel performance. Also, many firewalls do not let fragments through.

Netlock says:

We have seen some problems with high speed networks, where the MTU is smaller than expected, which can appear as if some applications work, but not others. Other symptoms include problems copying large files, but not small files. The fix is to reduce the MTU size to about 1385 bytes. MTU-related problems are common to PPPoE users, independent of our client.

Reducing the size of the MTU tells your computer to send smaller chunks of data through the network adapter. This gives the data a better chance of fitting into a packet that has all the VPN and PPPoE stuff in it as well, and consequently has a better chance of traversing the network in one go. This is especially relevant when transmitting large amounts of data as there is a greater chance of filling each packet to the limit (e.g.. connecting to exchange and downloading a bunch of messages).

Netlock makes an application temporarily reduce the size of the MTU for Mac OS 9, the Netlock MTU Reducer. This is a workaround that they expect to incorporate into a future version of the client. The Netlock MTU Reducer changes the size of the MTU from 1500 to 1385, but only until the next reboot. I suggest that it be moved to the Startup Items folder so that it loads automatically - there's already plenty to do to establish a VPN connection in OS 9 as it is...

You can get the Netlock MTU Reducer from:

http://www.netlock.com/support/ (Search for Article ID KB-1072)

My testing hasn't revealed any problems or performance handicaps on my test box on our local network.

PPP (dial up) uses it's own MTU value and isn't affected, and the Cisco client for OS X changes the MTU dynamically and is likewise immune.

References:

http://www.cisco.com/univercd/cc/td/doc/product/vpn/client/rel4_0/admin_gdvcach6.htm#1163720

http://www.netlock.com/support/ (Search for Article ID KB-1072)

http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/ethernet.htm#xtocid8

Warwick Teale
July 15, 2003

Here's some experiences and "magic-voodoo' workarounds for Michael. It was working ok for me.

Frankly OUTLOOK 2001 (OS 9) sucks for reliability over a VPN link. It locks up, is slow, is just generally unusable under Classic mode when used with VPNCLIENT...

So I have been using ENTOURAGE via iMAP to get to my EXCHANGE server - it is brilliant and a huge improvement over OUTLOOK 2001. There are some glitches but I'm far more productive now.

Incidentally - best working config for OUTLOOK 2001+VPNCLIENT has been OS X 10.1.4 (pre JAGUAR) , OS 9.2.2 and VPNCLIENT 3.5.2 or earlier... no problems for months! (but that's old news).

However to Mikes problem, in summary I think there are two main problems:

a) Set the OS 9 MTU (en0 or en1) to 1356 bytes as used by the CISCO VPN client. I have seen this problem for VPNCLIENT V3.2.x all the way to the present version 4.01. See below on how to do it. This may solve the slow downs and lockouts you seem to experience when 'communicating with the server".

b) OUTLOOK 2000 (OS 9) insists on using a fully qualified name (via a DNS) to resolve the exchange server. Sure you can prepare it with preferences/services/exchange server/'check names' but it will return a qualified name. It seems to insist on using this name (i.e. my.companys.exchange.server). The problem is that CLASSIC mode apps don't pick up the DSN.

You can try and use a Hosts file in the OS 9 system folder and bend the TCP/IP control panel to point to this hosts files. There is a lot of doc on this but I found it quite ineffective.

You can also try and add a name in netinfo manager.app/domains/machines. This works great for OS/X but still OS/X apps don't' seem to find it.

So I am very frustrated with it since late 2001 but have persisted until a few days back when I finally as so fed up I implemented Entourage.

I don't know if it works or not. Mostly is doesn't unless I do a few things:

First, I copied a new TCP/IP control panel into SYSTEM FOLDER/ PREFERENCES and yes I added and modified his HOSTS file and did it work. NO!

This is a long email and I'll show you what I did to finally get my emails from my company's OUTLOOK exchange 5.5 server via VPN.

Here's my situation:

  • OS 10.2.6
  • Outlook 2001 exchange client (needs OS 9 to run)
  • Airport using NAT and DHCP (typical usage) - home and hotel and someone else's place of business through a firewall.
  • Broadband and PPP sometimes when desperate.
  • Must connect through CISCO VPN 3000 concentrator at work.
  • Use Cisco latest VPNCLIENT 4.0 for 10.2.5+
  • USE ~/Library/CLASSIC for all classic mode prefs.
  • Sometimes use IPNETTUNER to change the MTU's from 1500 to 1356 for better connectivity under cisco VPNclient.

There seem to be five MAJOR issues that plague this situation not to work.

1) INABILITY for CLASSIC mode to locate HARD CODED DOMAIN NAMES in both the OS X NETINFO MANAGER/DOMAINS/MACHINES

2) INABILITY FOR CLASSIC TO USE THE HOSTS FILES IN EITHER SYSTEM FOLDER or any of its directories.

3) OUTLOOK slows down badly while synchronizing files or CONNECTING directly.

4) Outlook on "new setting" / "create account" or preferences/services/exchange server - may take an IP address instead of a server name however, for any further usage is seems to need a NAME like "exchangeserver.mycomany.com" and Classic doesn't seem to resolve this all the time.

5) there is NO VPNCLIENT from CISCO for OS 9.. and besides I don't like rebooting all the time.

I tried so many things here and NEARLY resorted to using my fallback of VPC 6 (virtual PC) with WINDOWS OUTLOOK client. Naturally this works flawlessly (bugger!) but it is a nuisance having to use VPC. This is the only reason I bought VPC years back was to access corporate emails under exchange before I discovered the OUTLOOK 2001 EXCHANGE OS 9 client.

I found that in the above situation there is NO rules or special sequence of starting up VPN, then classic then OUTLOOK. This does not fix the DNS lookup issue for Classic b ut THIS does!

To do this you will need IPNETUNER and some classic mode PING and TRACE tool. use WHATROUTE. There are trial 30 day versions of these else buy it.

SUGGESTIONS FOR USING OUTLOOK 2001 under OS X and VPNCLIENT:

I would highly suggest that you operate OUTLOOK using an OFFLINE file and DON'T use any .PST files. Why? Because it sucks when you have to FORCE Outlook 2000 client out and it may possibly damage any .PST file you are using. Then, unless you have a backup you will need to fire up Windows and have you take hours to repair the .PST files (another reason to have VPC 6 on hand) . Having been caught with this a few times while traveling, I couldn't be bothered.

a) Using an OFFLINE file requires SYNCHRONIZATION but that's a small price to pay for being unable to get company emails when you HAVE to have hem and everyone uses windows and PCs.. There's two copies of your emails too. not just you .PST files... and WHAT if you never had a back AND .. bang1 - no DDM anymore. whoops.. yes been there!

b) offline mode also provides you a backup. You have the original emails still on your company's server. IF they use an EMAIL archiver then you're sweet forever!

c) just back up you OFFLINE files DAILY locally.

Oh.. and when OUTLOOK appears hopeless LOCKED UP - DON'T FORCE IT OUT. Yss you may corrupt your .PST files as above. I suggest you just STOP and RESTART the VPNCLIENT connection... works most times hen after 2 minutes OUTLOOK 2001 gets going again.

You can imagine what a pain this is.

PREPARATION one time:

1.a) create a separate "SYSTEM PREFERENCES/NETWORK/test vpn and outlook" location. I use this for my AIRPORT - using DHCP. Nothing special here.

1.b) assume your USUL network config is called SYSTEM PREFERENCES/NETWORK/"normal use with airport"

2) ADD in the DNS names that are used by your company. These are usually behind a firewall or or just local to your place. Feel also free to use their IP address instead. I have two I use. Using either seems to result in the same.

3) Save this configuration but DON'T apply it. Keep using SYSTEM PREFERENCES/NETWORK/"normal use with airport". Make sure you set up the airport or what ever else you need. May be ass in the optional SEARCH DOMAINS like company.com for things to resolve but I dunno if this added any thing .

PROCEDURE:

4) Now START the CISCO VPN client using your usual connection that you would use when stuff works for your NON-OUTLOOK usage. For example, a plain AIRPORT/DHCP/NAT . Oh it might make good sense to use the IP address for the cisco VPN router because you will have to restart the CISCO client in a moment in an environment that uses only your company's FIREWALLed DNS and your VPN router server may not be found via a name search.... maybe.

5) Now start the CLASSIC mode form the SYSTEM PREFERENCES/CLASSIC pane. Classic starts while VPN is up... well sometimes it doesn't matter.

6) Now while all this is up, Reset your new network preferences for the setting you created at first called " test vpn and outlook" ". You will notice that the VPN connection probably drops, a good sign for knowing that maybe you gonna have some success.

7) Reconnect the VPN client again. using the same router as before. Something has triggered CLASSIC mode into now seeing the name server you need for OUTLOOK!

8) USING OS X "network manager" or the Terminal tool, see if you can TRACEROUTE (or TRACE) the path to your company's exchange server (i.e. "exchangeserver.mycomany.com"). If not, try and TRACE via it's IP address and see where you get. If no success, maybe resolve the PATH or why you can't get it. Else....

9) Start IPNETUNER in classic mode. Set the MTU address for the ETHERNET to 1356 to be the same as the one used by OSX's VPNLCLIENT. As an example, in OSX's terminal tool issue the command "ifconfig en1" . On my machine (this TI) en1 is the airport. You will see the MTU (mtu) is something other than 1500 bytes.

10) Verify that classic can resolve your exchange server NAME (exchangeserver.mycomany.com" ). So STart WHATROUTE and perform TRACE for your exchange server name.

11) If not, RE-set your new network preferences for the setting you created at first called " test vpn and outlook. You will notice that the VPN connection probably drops then GOTO step 7.

11) Still with me?? (yes it is a pain in the arse). START OUTLOOK CLIENT in your usual way.

12) Re-synch your outlook files ONE at a time via tool/synchronise/this folder

I have no idea why those work. I had everything working with out any of this bugga-boo a month ago and then after my company changed the local exchange server I had a load of troubles. I think it is reolated to DSN resolution in CLASSIC mode.. maybe only me. The MTU setting also seems to help to avoid losing connectivity.

I was so frustrated doing this that I now use ENTOURAGE-X via IMAP, sendmail and LDAP.. works great if you don't need that CALENDAR sharing. I can fire up ENTOURAGE-X and VPNCLIENT 4.0 and get my corporate emails in 30 seconds. You could use any IMAP mail client like OSX's mail.app.

July 22, 2003
Mark Phillips

Looking through the issue, most people are going on about setting the MTU size but this just as easily be a firewall problem. It could be something as simple as not having the necessary port open on either the local firewall or the firewall in the DMZ.

A simple check would be to log anything that gets dropped on the firewalls and then have a trawl through the log files.

If you can verify that any of these approaches works (or doesn't work), please let us know.

Problem with attachments in Outlook 2001 and Panther

February 4, 2004
Michael Wilmar

I have recently bought a new PowerBook with Panther preinstalled. I use it in my office, where I must interface with an Exchange Server for email. Our IT staff is not yet ready to enable IMAP and the other features that are needed to make Entourage for Exchange Server fully functional, or indeed functional at all. As a result, I am stuck with Outlook 2001 for a while.

I am finding that, except for Word documents, I cannot open attachments (e.g., .html or .pdf files) from within Outlook. I have to save them to the Desktop and open them from there. The message I get is "The application associated with this attachment cannot be started."

Outlook Help says that Outlook looks to the PC Exchange Control Panel for conversions. However, this Control Panel is not supported in Classic. Has anybody found a way to open attachments from within Outlook?

February 9, 2004
Mark Cole

I can confirm Michael Wilmer's observation about Outlook 2001 no longer opening attachments from within Outlook. This did work for all versions of 10.1 and Jaguar, but was broken starting with 10.3.0.

February 9, 2004
Michele Corum has a suggestion for opening attachments:

Welcome to the wonderful world of Microsoft Outlook 2001 running in Classic! I find that having the following applications launched helps me to open attachments and hyperlinks in Outlook 2001: Word, Excel, Acrobat, Explorer. However, many times I still need to copy to attachment to my desktop to open.

February 17, 2004
Charles Killorin says "I can't see them either."

A suggestioned fix

February 17, 2004
Massimo Mauro

The persons in trouble with Outlook 2001 in Panther must have just upgraded their computers (from 9 to X) and as a result Outlook 2001 does not run, because the parameters are no longer right. What one should do is instead to run the application "Outlook Settings" (under MacOS 9, but it runs under Classic) and rewrite all their settings. I can guarantee it works that way.

February 19, 2004
Marcos Rivas of Argentina offered another suggestion for the problem of Outlook 2001 attachments in Mac OS X 10.3:

Try changing the file associations with the OS 9 Internet control panel in the Classic environment in OS X 10.3

Change the file association in Advanced/File mapping in the Mac OS X set for the applications where you receive the error "unable to find specified application".

Try to use an application that works in OS 9 or a carbon one. That works for me.

Another Attachments problem

February 17, 2004
Massimo Mauro

We have an old Exchange Server (not even 2000 yet) with Outlook 2001 clients plus Mail.app clients (running under Panther). With this lethal mixture there seems to be no way to send attachments in a way recognized by both classes of e-mail clients. If the Panther Mail.app client send attachments as "Window friendly" then the Outlook 2001 will recognize it properly, but the reverse path does not work: one receives on the Panther Mail clients attachments embedded within a "MIME attachment" which have then to be peeled off by TNEF's Enough. This is a major pain in the neck.

As an IT professional I must say that the very limited configurability of Panther Mail (whose help details all trivia and explains no real hard issue) shows clearly that this product is far from mature and cannot be deployed in a corporate environment, even though it can talk with Exchange servers.

As we have reported before, TNEF's Enough is a Mac utility used for fixing attachments sent by Outlook for Windows.

If you've seen this or have a suggestion, please let us know.

Outlook 2001 with Exchange 2003

Several readers responded to our question about using the Outlook 2001 Mac client with Exchange 2003. Most report that it works just fine. One reader had a problem.

February 4, 2004
Greg Krabbenhoft:

I recently upgraded our exchange server to 2003 and have found no adverse effects using either mail.app or outlook 2001:mac. Everything seems to work just as it did before.

February 4, 2004
Brian Hoppe:

The company I work for recently upgraded to Exchange 2003 Server. In our experience, it was a smooth, uneventful upgrade (at least as far as Outlook 2001 compatibility is concerned). There have been no issues or problems with connectivity or functionality that I am aware of. Most of the 10 Macs in our organization are still running Mac OS 9.1 or 9.2.x. (there are also several hundred PCs, mostly running Windows XP or Windows 2000). I am the primary end-user support person for our Mac users, and I'm sure I would have immediately heard if there were issues.

I've also done some informal testing of Outlook 2001 under Mac OS X 10.3 on an iBook. As has been reported previously on MacWindows, Outlook 2001 wouldn't run under Mac OS X 10.3 until I created a self-mounting disk image and copied Outlook to it. After I did this, Outlook runs and connects properly to the Exchange 2003 server. I have not tried the latest version of Entourage X with Exchange support.

February 4, 2004
Christopher Kasper:

I run an Exchange 2003 Server using both Outlook 2001 and Entourage X clients. I have not noticed any problems with either piece of software resulting from migrating to Exchange 2003. They work fine

February 4, 2004
Kay Christianson, however, has a problem:

Run from either 9 native, or 9 Classic within 10.2 or less (not 10.3), Outlook 2001 appears to function fine against the 2003 server.

Unfortunately, as far as I know, no one has been able to reliably get 2001 running in Classic under 10.3.

There are big threads on the permissions issues involved, and the fixes listed to date apparently don't work for all users.

If you have a suggestion for Christianson, please let us know.

Mac IMAP clients cannot see Exchange Public Folders

February 4, 2004
Josh Wilmoth is having the problem reported last week with an inability to see Exchange's public folders with IMAP clients such as Mail. If you've seen it, please let us know.

 February 17, 2004 -- Regarding Panther's problem with Outlook 2001 seeing public folders on Exchange, reader Charles Killorin says "I can't see them either." However, Massimo Mauro has a suggestion:

The persons in trouble with Outlook 2001 in Panther must have just upgraded their computers (from 9 to X) and as a result Outlook 2001 does not run, because the parameters are no longer right. What one should do is instead to run the application "Outlook Settings" (under MacOS 9, but it runs under Classic) and rewrite all their settings. I can guarantee it works that way.

Using Panther Classic to run Outlook 2001 on Tiger

November 17, 2005
Manuel Hernandez from Spain recommends using the Panther's Classic to run Outlook 2001 in Tiger:

I had the same reported problem when I attempt run Outlook 2001 over iMacs G5 with Tiger.My solution: Install again Tiger erasing the disk, and install the version of Classic from Panther, Mac OS X 10.3.x.It was not necessary to do with the last version of Tiger (10.4.2) is not necesary that.
If you've tried this

 
| Top of the Outlook Special Report Page |

Other MacWindows Departments


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

| Product Solutions | News Archives | Site Map |
|
MacWindows Home |