Outlook 2001 and Panther - solution?

[Hal4sn_MN]

Hello.

Possible solution?

I've experienced the issue with Outlook 2001 not launching because of the
error "The set of folders could not be opened. The attempt to log on to the
Microsoft Exchange Server has failed."

Creating partitions and disk images is not an option for our Mac OS X 10.3
images in our enterprise.

What I noticed is that I if I setup the user's Outlook profile (within
Outlook Settings) and then authenticate in an application such as NAV's
Auto-Protect preference panel, Directory Access, or NetInfo Manager, the
known issue with timed-extra privs kicks in and then the person can
successfully launch and use Outlook. Once this step is complete, the person
can always launch and use Outlook. It's important to note that the customer
has to be setup as an administrator in Mac OS X's accounts.

Can someone else give this a try? It's been difficult to repeat.

Jason

 

[William M. Smith]

Hello.

Possible solution?

I've experienced the issue with Outlook 2001 not launching because of the
error "The set of folders could not be opened. The attempt to log on to the
Microsoft Exchange Server has failed."

Creating partitions and disk images is not an option for our Mac OS X 10.3
images in our enterprise.

What I noticed is that I if I setup the user's Outlook profile (within
Outlook Settings) and then authenticate in an application such as NAV's
Auto-Protect preference panel, Directory Access, or NetInfo Manager, the
known issue with timed-extra privs kicks in and then the person can
successfully launch and use Outlook. Once this step is complete, the person
can always launch and use Outlook. It's important to note that the customer
has to be setup as an administrator in Mac OS X's accounts.

Can someone else give this a try? It's been difficult to repeat.

Hi Jason!

Can you point me to more information about the "known issue with timed-extra
privs"?

I've seen this problem once at work and ended up installing Panther fresh on
the machine instead of upgrading to correct the problem (among other
unrelated issues).

I'll have the opportunity to set up another machine soon and I can try to
recreate the problem again before deploying it.

Thanx! bill