View Single Post
  #7  
Old February 7th 06, 12:22 AM posted to microsoft.public.outlook.program_addins
Paul
external usenet poster
 
Posts: 3
Default Outlook Connector for IBM Lotus Domino

JB,
Make sure when you look in Control Panels-- Add/Remove Programs, that
the "Change or Remove Programs is selected and at the top of the
window, the "Show Updates" is Checked. The KB892843 was a Hotfix that
was pushed sometime in January via the Windows Automatic update. If
the Checkbox is not checked, it won't show up on the list. There are
two entities that comprise the Hotfix that have (KB892843 ) as part of
the name. Once they're removed, re-boot and install the OLCONN2 again,
and follow the install.
If you've never had Outlook working with your Dominos server via the
Outlook Connector, you must have the Lotus Notes Client set up and
running with a valid .id file. The Outlook Connector set-up uses the
local Notes Client info to get the server name and ID file

Paul

J. B. Roman wrote:
Hey Paul,

I have followed all of the threads relating the Domino Connector Add-In as
well as researched the Internet because I am unable to get the Domino
Connector to establish a connection with the server. I tried every
combination of uninstalling-reinstalling that was possible without any luck.
I also looked for the KB892843 update that you mentioned. I found that I
don't have it installed on the machine. I running Windows XP Pro with
Office 2003 Pro (SP2). I was wondering if there is any other possible
solutions this problem.

Thanks in advance for your help,

J. B.


"Paul" wrote in message
oups.com...
Wayne & Abel,

Nice Catch!! Been having the same problems with olconn2 and Domino
since mid Jan 06. olconn2 was working fine for over a year, even after
the SP2 upgrade. Tried every combination of uninstall-reinstall that
was possible. Since I did not have the "show updates" checked in the
add-remove programs control panel, I did not see the KB892843 update.

I uninstalled the olconn2, and the two updates under KB892843,
re-booted, reinstalled olconn2 and life is good again (with office 03
SP2). The problem appears to be solely from "Security Update for
Outlook 2003 (KB892843)"

once again, nice catch! Thanks


Ads