Error message says cannot find wab.dll

[Guest]

Using Windows Vista and Outlook 2000. Trying to import Contacts into
Outlook, I get an error message that says: An error occurred while
attempting to open the Windows Address Book. Unable to find the WAB.DLL.

 

[Russ Valentine [MVP-Outlook]]

Expected and well documented. Outlook 2000 in IMO required Outlook Express
which no longer exists in Vista. I would expect neither Outlook 2000 nor
2002 to function properly in Vista.

 

[Tricia]

What about on Windows XP where this Outlook 2000 was originally bundled with.
I all of a sudden, after downloading updates from MS, get this same error
message when trying to enter appointments on my calendar?

Expected and well documented. Outlook 2000 in IMO required Outlook Express
which no longer exists in Vista. I would expect neither Outlook 2000 nor
2002 to function properly in Vista.
--
Russ Valentine
[MVP-Outlook]

Using Windows Vista and Outlook 2000. Trying to import Contacts into
Outlook, I get an error message that says: An error occurred while
attempting to open the Windows Address Book. Unable to find the WAB.DLL.

 

[Brian Tillman]

What about on Windows XP where this Outlook 2000 was originally
bundled with. I all of a sudden, after downloading updates from MS,
get this same error message when trying to enter appointments on my
calendar?

Click Start>Run. Enter "wab.exe" (without the quotes) in the OPen field and
click OK. What happens?

 

[Tricia]

A prompt asked me to make the address book my default, I said yes. Then it
opened an address book file. I then tried Outlook, but still get that error
message about not finding the wab.dll.

 

[Brian Tillman]

A prompt asked me to make the address book my default, I said yes.
Then it opened an address book file. I then tried Outlook, but still
get that error message about not finding the wab.dll.

See this: http://support.microsoft.com/kb/196210

 

[Tricia]

I tried the http://support.microsoft.com/kb/196210 procedure, but it didn't
change anything. I am just stumped. Now I am also receiving an explorer
application error now that says "The instruction at "0x300ac323" referenced
memoy at "0x056ae314". The memory could not be "read". I have reinstalled
Windows XP and Office in the last week due to explorer error messages and
eventually it not working at all. Thank you so much for trying to help me!

 

[Brian Tillman]

I tried the http://support.microsoft.com/kb/196210 procedure, but it
didn't change anything. I am just stumped. Now I am also receiving an
explorer application error now that says "The instruction at
"0x300ac323" referenced memoy at "0x056ae314". The memory could not
be "read". I have reinstalled Windows XP and Office in the last week
due to explorer error messages and eventually it not working at all.
Thank you so much for trying to help me!

I'm afraid I, for one, am out of suggestions. Sorry.

 

[Tricia]

Thank you. I reinstalled the Windows XP. While doing that it noted that the
wab.dll file was missing or corrupt along with about 5 other files. Maybe I
have gotten all the use out of this XP that I can. It is starting to get
annoying.

 

[Russ Valentine [MVP-Outlook]]

There's your problem then. Just rename every wab32.dll file you find, then
repair Outlook Express.

 

[Brian Tillman]

Thank you. I reinstalled the Windows XP. While doing that it noted
that the wab.dll file was missing or corrupt along with about 5 other
files. Maybe I have gotten all the use out of this XP that I can. It
is starting to get annoying.

You should be able to perform a repair install of Windows that will replace
the files.

 

[Crib92]

I am having a similar problem with Vista and Outlook 2000. I can't open the
address book, import into it. (Missing WAB.DLL file) Basically no sucess at
all. Would appreciate any insight into how I could get this to work. I
can't say that my experience with Vista so far is all that great. Many
compatability issues.

 

[Russ Valentine [MVP-Outlook]]

Have you read any of the countless posts here that already answer your
question? This is not a Vista issue. You are attempting to use software that
is years out of date and years out of support with a new OS. Not sure what
you were thinking would happen.