Greetings--
A client of mine and I are having a problem accessing the address
book from within MSWord. We each are using different versions of
Windows (he has Win98, I have Win95a), different versions of Word
(he has Word97 SR-2, I have Word from Office 95), and different
versions of Internet Explorer/Outlook Express (he has IE 5.0 B2,
I use 4.01 SP-1 with patches). To make matters even more
complicated, his machine is a Gateway 2K PII 266, w/ 64 MB RAM,
mine is a P233 MMX with 64 MB RAM. I believe that our problem
has a similar root. When we click "Tools", "Envelopes and
labels", then click on the address book icon in the dialog box,
we receive the following message (with a minor variation, in his
case):
"Logon Failed. You must log on to Microsoft Exchange to
access your address book. Error Code ""
(0x8007000E/0x00000000)" [His variation was "Unspecified error"
following Error code.].
I know our hard- and soft- ware differ, however; I can't help but
believe there is a common cause for this problem.
The Microsoft Knowledge Base (Article ID: Q178481 WD97: Errors
Accessing the
Address Book Icon) listed this message almost verbatim as a
symptom of Outlook Express having been selected as the "Simple
MAPI Client" on the General tab of OE's "Tools >> Options" menu.
(Selecting this does generate a message to the effect that
certain functions like the address book will not function
properly when this option is chosen. I chose it to see if I
could provoke the same behavior my client's machine shows. It
worked, however; "un-choosing" it fails to remedy the problem.)
My client tells me, though, that OE with IE 5.0 B2 does not have
this option on any of the tabbed dialogs under "Tools >>
Options". I located what I thought was the setting to change in
the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Outlook
Express. The DWORD hex value had been changed from 0 to 1. I
changed it back to 0 on my machine and the check mark was removed
from "Make OE my Simple MAPI Client". I posted my client to
advise that he try this, then reboot and see if the problem had
been cured. (I did the same.) I found, after rebooting, that the
problem had not been resolved, indicating to me that more
registry settings probably need to be changed.
I apologize for the length of this post, but I felt it was
necessary for clarity. I hope someone on the list has perhaps
experienced this and has an effective recommendation.
TIA,
Paul A. Shippert Library/Media Specialist
"All what we got here's American-made.
It's a little bit cheesy, but it's nicely displayed." Frank
Zappa
[log in to unmask]
Curious about the people moderating your
messages? Visit our staff web site:
http://nospin.com/pc/staff.html
|
