Outlook 2001

[Kevin at CDC]

I have a user running Outlook 2001 under Classic 9.x on
Mac OS 10.x. After migrating the user to a new domain, he
gets the following message, "The set of folders could not
be opened. The attempt to log on to the Exchange computer
has failed". He was logging on fine before the move, but
not after the move. He doesn't get a prompt for a password
or domain when he attempts to open Outlook so I'm not sure
what domain or password info is being passed to the
Exchange server. The server name resolves when pinged
using OS X utility and the user authenticates fine when
checking the Exchange server properties for his profile.
I've created a hosts file and placed it in the system
folder thinking that may help, but no joy.
Any help on this is greatly appreciated.

 

[William M. Smith]

I have a user running Outlook 2001 under Classic 9.x on
Mac OS 10.x. After migrating the user to a new domain, he
gets the following message, "The set of folders could not
be opened. The attempt to log on to the Exchange computer
has failed". He was logging on fine before the move, but
not after the move. He doesn't get a prompt for a password
or domain when he attempts to open Outlook so I'm not sure
what domain or password info is being passed to the
Exchange server. The server name resolves when pinged
using OS X utility and the user authenticates fine when
checking the Exchange server properties for his profile.
I've created a hosts file and placed it in the system
folder thinking that may help, but no joy.
Any help on this is greatly appreciated.

Hi Kevin!

After migrating the user to the new domain, did his Exchange server change?
Is he still trying to access the same server using the same server name or
same server IP address?

Outlook 2001 runs in Classic, which has its own networking apart from Mac OS
X. Because you can ping in Mac OS X, does not necessarily mean that Classic
is able to connect.

A Hosts file by itself is not enough. The Classic TCP/IP Preferences must
point to the Hosts file. If you're able to boot into Mac OS 9, you can open
the TCP/IP Control Panel and then select the Hosts file. You can then boot
into Mac OS X and Classic will still work for you.

If you have a situation where you can not boot into Mac OS 9, email me
privately and I can provide you a couple of files that are preconfigured
with the settings you'll need.

Hope this helps! bill

 

[Steve]

I have a similar problem that I have been able to unresolve.

I recently upgrade from OSX 10.2.7 to OS 10.3. Outlook 2001 worked in
Classic mode with 10.2.7, but when I try to launch it in Classic under
10.3, I get the following message: The set of folders could not be
opened. The attempt to log on to the Microsoft Exchange Server has
failed.

If I reboot under OS9, Exchange works!

I have thrown away all Outlook preferences, reinstalled outlook, and
not yet linked any of my personal folders into the new installation.
There is a hosts file in place that is pointed to through the TCP/IP
control panel. Outlook continues to work in OS9, the server registers
through the Outlook Settings control panel, but I continue to get the
error when I try to run in Classi under OSX.

I am a corporate user without IT support and desperately need to get
this issue resolved.

Any help appreciated!

Steve

 

[William M. Smith]

I have a similar problem that I have been able to unresolve.

I recently upgrade from OSX 10.2.7 to OS 10.3. Outlook 2001 worked in
Classic mode with 10.2.7, but when I try to launch it in Classic under
10.3, I get the following message: The set of folders could not be
opened. The attempt to log on to the Microsoft Exchange Server has
failed.

If I reboot under OS9, Exchange works!

I have thrown away all Outlook preferences, reinstalled outlook, and
not yet linked any of my personal folders into the new installation.
There is a hosts file in place that is pointed to through the TCP/IP
control panel. Outlook continues to work in OS9, the server registers
through the Outlook Settings control panel, but I continue to get the
error when I try to run in Classi under OSX.

I am a corporate user without IT support and desperately need to get
this issue resolved.

Hi Steve!

If you're able to boot into Mac OS 9 and not have problems, then something
is wrong in Panther.

Panther upgrades seem to break something that Outlook 2001 needs. This has
been the topic of several discussions here, but no one seems to have found
the solution to fix it. It doesn't seem to be a permissions problem

The workarounds so far have been to simply copy the Outlook folder to
another disk or partition or even to use the Disk Utility to create a disk
image (.dmg) file and set this to mount at login.

After reading about this problem for a while here, I too came across it at
work and decided to simply blow the system away and install Panther from
scratch rather than upgrade from Jaguar. This is drastic, but I don't have
the problem with a clean install.

bill

 

[Pauls Sloss]

Panther upgrades seem to break something that Outlook 2001 needs. This has
been the topic of several discussions here, but no one seems to have found
the solution to fix it. It doesn't seem to be a permissions problem

The workarounds so far have been to simply copy the Outlook folder to
another disk or partition or even to use the Disk Utility to create a disk
image (.dmg) file and set this to mount at login.

After reading about this problem for a while here, I too came across it at
work and decided to simply blow the system away and install Panther from
scratch rather than upgrade from Jaguar. This is drastic, but I don't have
the problem with a clean install.

bill

I have had the same problem with the archive install of Panther on a
test machine at work. For about a month the same error message came
up, then all of a sudden, last week, I could log on.

I've tried to upgrade another Jaguar machine to Panther and have come
back to the same problem. I cannot upgrade to Entourage because the
IT dept are having trouble implementing Exchange 2000, so we are
stuck with Exchange 5.5 for a while.

Panther has no separate TCP/IP or Appletalk control panel, so I assume
all networking is handled by the X side. The hard part is finding
someone responsible for troubleshooting the problem from either
Microsoft or Apple with a view to establishing where the problem lies
and possibly providing a patch or hack.

For now I will try the disk image solution, as it is too big a task to
rebuild all the other workstations. I've just spent a month trying to
activate our Quark licences, a fresh Panther install will put me back to
square one.

 

[Steve Tenney]

I have had the same problem with the archive install of Panther on a
test machine at work. For about a month the same error message came
up, then all of a sudden, last week, I could log on.

I've tried to upgrade another Jaguar machine to Panther and have come
back to the same problem. I cannot upgrade to Entourage because the
IT dept are having trouble implementing Exchange 2000, so we are
stuck with Exchange 5.5 for a while.

Panther has no separate TCP/IP or Appletalk control panel, so I assume
all networking is handled by the X side. The hard part is finding
someone responsible for troubleshooting the problem from either
Microsoft or Apple with a view to establishing where the problem lies
and possibly providing a patch or hack.

For now I will try the disk image solution, as it is too big a task to
rebuild all the other workstations. I've just spent a month trying to
activate our Quark licences, a fresh Panther install will put me back to
square one.

There is a comment on Mac-In-Touch that this problem is related to the
inability of Outlook 2001 under Classic to resolve the DNS. The
solution was to replace the machine name (in the OSX CP) with the IP
number. I am experiencing this problem, but the DNS is specified in
the OSX network panel as an IP, so that doesn't seem to fix the
problem. Anyone have any additional thoughts?