New MS Office 2003 pro install, Outlook crashes

[Guest]

I have been using Outlook Express for email on a Toshiba notebook with
Windows XP Pro. I just installed MS Office 2003 Pro and it has defaulted to
MS Outlook as the email program. I installed it as administrator and outlook
works fine when I'm logged on as adminstrator. When I'm logged on as another
user however, each time I open Outlook, windows installer wants to
re-configure MS Office... box appears "Please wait while Windows cofigures
MS Office Prof Edition", it seens to finish then repeat several times, then
comes up with the message ".. outlvba.dll is not a valid Office add-in". I
close this box and then it attempts several more times to "configure" MS
Office, finally stops, and then the Outlook window opens. Outlook will then
function for reading mail in inbox but when I attempt to save a sender's
address in contacts, all hell breaks loose. The windows installer configuring
office thingy repeats until it locks up. I then have to "CTRL-ALT-DEL" to
close down windows installer. I get an error mesage "MAPI32.DLL is corrupt
or the wrong version".
I have 1. run the repair-reinstall Office, 2. downloaded office2003 service
pack and installation, and from the office website checked for other updates
and installed them. These measures have not fixed the problem. I ran
reinstall again still to no avail.

Can anyone out there help me?

 

[Can-so]

Go here and rename the outlvba.dll to outlvba.old

C:\Program Files\Microsoft Office\OFFICE11\ADDINS

Then do a detect and repair of office

--
"Bother," said Pooh as he struggled with the computer.

"It never does quite what I want."

"I wish Christopher Robin were here."

 

[Guest]

Bother indeed! This bear needs more honey.

I did exactly as you suggested and unfortunately it did not solve the
problem. It continues to tell me that the re-installed outlvba.dll is not a
valid Add-in.
Should I do something about the corrupt MAPI32.DLL?

 

[Can-so]

Ok then enter the registry and back up the following folder
HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins

Then delete any sub folders of addins


--
"Bother," said Pooh as he struggled with the computer.

"It never does quite what I want."

"I wish Christopher Robin were here."

 

[Guest]

Thanks for your response, "Can-so"

Discovered how to open regedit, and looked for the folder you mentioned
however there was no "Addins" subfolder in
HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\

In the meantime I've reverted to using Outlook express as my default email
program, quite happily for now, though I suspect Outllok has more to offer.

 

[Brian Tillman]

Discovered how to open regedit, and looked for the folder you
mentioned however there was no "Addins" subfolder in
HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\

They might also be in
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Addins

 

[Can-so]

whoopsie my bad
Long day at the office should have mentioned that string as well

--
"Bother," said Pooh as he struggled with the computer.

"It never does quite what I want."

"I wish Christopher Robin were here."

 

[sdmaley]

*I have been using Outlook Express for email on a Toshiba notebook
with
Windows XP Pro. ... *

I've got WinXP Pro on a desktop, that recently complained the
%SystemDrive% was running out of space. As the largest hog in that lot,
I decided to uninstall MS Office Pro 2003, and reinstall it to a more
spacious partition.

As you noted, Outlook 2003 runs fine from an Admin account, but not
from a lesser (such as PowerUser) account.
What you didn't mention about the error popup is that Outlook is
looking for outlvba.dll in a subdirectory of %UserProfile% (at least in
my case). I suspect that is some kind of default path, where Outlook
looks if it can't find outlvba.dll where it should be according to the
registry.

The problem appears to be one of permissions, but to what?
Could be key(s) in the registry, could be Security Policy, could be
access rights to outlvba.dll where MS Office Pro 2003 installed it. The
path to outlvba is correct under
{HKCR}\CLSID\{799ED9EA-FB5E-11D1-B7D6-00C04FC2AAE2}.
The problem may be that {HKCR}\Microsoft.VbaAddinForLook (which refers
to the key that has the path to outlvba), has permissions only for
Administrators and SYSTEM. Need to add PowerUsers (or whatever group or
user will be used), w/ Permission Read, which consists of: Query Value,
Enumerate Subkeys, Notify, and Read Control.