Invalid Add-in error message

[Guest]

When I open Outlook 2003, I keep getting the following error message:
C:\Documents and Settings\Amanda\Application
Data\Microsoft\AddIns\outlvba.dll is not a valid Office Add-in. Then I am
booted from Outlook. How can I fix this?

 

[neo [mvp outlook]]

Try renaming outlvba.dll to outlvba.bak. Go to the add/remove applet in the
control panel and perform a detect and repair on Office/Outlook 2003.

/neo

ps - outlvba.dll normally exists at \Program Files\Microsoft
Office\OFFICE11\ADDINS. I've never seen it under a user profile.

 

[Guest]

The add-in error for OUTLVDA.DLL appears to relatively common. There are
many posts on the WEB but NO official fix or sugeestions how to troubleshoot
the error - except this one from NEO, which I will try.

Microsoft needs to deal with this error and give us the troubleshooting tool
to resolve this Office 2003 add-in issue. It appears inconsistently and
randomly reappears after the dll has been re-enabled.

I am using an Office 2003 Pro upgrade from Office 97 Pro. OUTLVBA.DLL is
version 11.0.5516.0.

My Addins folder contains:
FOLDER C:\Program Files\Microsoft
Office\OFFICE11\ADDINS\ ------- 0 16 598,943 598,943
FILE ---A---- 8/3/1998 17:28 8/3/1998 17:28 2/26/2005 10:30 623 DLGSETP.ECF
FILE ---A---- 8/3/1998 17:28 8/3/1998 17:28 2/26/2005 10:30 808 DUMPSTER.ECF
FILE ---A---- 7/31/1998 11:01 7/31/1998 11:01 2/27/2005 11:16 830 FAXEXT.ECF
FILE ---A---X 7/10/2003 01:23 7/10/2003 01:23 2/27/2005 11:23 7,168 MSOSEC.DLL
FILE ---A---- 3/18/2003 15:45 3/18/2003 15:45 2/27/2005 11:15 179 MSOSEC.XML
FILE ---A---- 10/7/1998 23:46 10/7/1998 23:46 2/26/2005 10:30 778 MSSPC.ECF
FILE ---A---X 3/18/2003 15:23 3/18/2003 15:23 2/27/2005
10:30 344,064 MSVCR71.DLL
FILE ---A---X 7/10/2003 01:11 7/10/2003 01:11 2/27/2005
11:15 77,824 OTKLOADR.DLL
FILE ---A---X 10/24/2003 15:16 10/24/2003 15:16 2/27/2005
10:36 44,656 outbak.dll
FILE ---A---- 9/2/1998 16:22 9/2/1998 16:22 2/27/2005 11:15 1,936 OUTEX.ECF
FILE ---A---- 7/20/2000 10:04 7/20/2000 10:04 2/27/2005 11:16 862 OUTEX2.ECF
FILE ---A---X 7/23/2003 22:32 7/23/2003 22:32 2/27/2005
11:16 45,112 OUTLVBA.DLL
FILE ---A---- 10/7/1998 23:47 10/7/1998 23:47 2/26/2005 10:30 626 PMAILEXT.ECF
FILE ---A---- 2/20/2005 08:12 2/20/2005 08:12 2/26/2005 10:30 464 safemail.ECF
FILE ---A---- 8/3/1998 17:28 8/3/1998 17:28 2/26/2005 10:30 693 SCRPTXTN.ECF
FILE ---A---X 8/28/2003 18:21 8/28/2003 18:21 2/27/2005
11:24 72,320 VCMailE.dll

Any suggestions?

Thank you
Leroy

 

[Guest]

I am back again. I went to the add/remove applet in the control panel to
perform a detect and repair on Outlook 2003. There is only a "detect and
Repairs Errors in my Office Installation" nothing particular to Outlook. I
also needed to go into Task Manager to stop background Office applications
that were running before running the Office repair function.
Windows reports the repair was successful. The Repair replaced the same
outlvba.dill version/date/size file into the ADDIN folder. Nothing is
presently disabled in Outlook 2003.

We'll see if this fixed it.

 

[Guest]

See http://support.microsoft.com/?kbid=235009 for a possible solution

 

[Guest]

Well, the detect/repair idea did not fix the problem. After just a few days,
I got the popup that there was an error and the add-in would be disabled when
Outlook opened.
Suggestions?

 

[Guest]

I took a look at the support page 235009. I did not have an Outlook Sync
option to clear. So no help for me.
Suggestions?

 

[Guest]

I tried all the posted solutions. There is nothing in the Com addins box to
disable.

Yesterday, I ran the Office removal tool several times (it would constantly
freeze up - "not responding") and ran the detect and repair options in Office
2003 and in OneNote 2003. I no longer have a OLSpacop toolbar or a OneNote
toolbar in Outllok 2003 but more importantly, I am no longer getting the
error messages and the disabled dll.

..Iit most be more M$ FM, Microsoft F**king Magic.

 

[Guest]

I have verified that if I install the OLSpamCop addin, I get the dll error.
If I uninstall the add-in, the error messages stop. I am unable to determine
the underlying cause of the error messages and the disabled dll.