Ive had the Outlook connector working for ages now with very few problems. For the last week however it seems to die as soon as I go in. I havent had a notes upgrade. My Outlook is 2003. Any ideas ? I have got an NSD log file if that helps
Subject: Outlook crashes with an NSD message
Hi
Can you post the FATAL THREAD section of the NSD files with the few lines under it
For example:
############################################################
FATAL THREAD 1/2 [ domdsm:107a8:67076]
FP=0x0012a34c, PC=0x60069a86, SP=0x0012a2f0, stksize=92
EAX=0x01a3088c, EBX=0x01a48650, ECX=0x0000bffe, EDX=0x01a325e6
ESI=0x00004000, EDI=0x0032ff78, CS=0x0000001b, SS=0x00000023
DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010206
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x60069a86 nnotes._fdDelete@4+118 (4000,12a368,608770ef,4000)
@[ 2] 0x60069a0c nnotes._OSFileClose@4+12 (4000,12adc0,12a380,60872ea7)
@[ 3] 0x608770ef nnotes._sqloclose+15 (4000,12b59c,5010,0)
@[ 4] 0x60872ea7 nnotes._sqlpgclf+71 (12adc0,1aaa2cb,70,1aaa2f3)
@[ 5] 0x60885458 nnotes._sqlpgfdl+616 (12b9a4,1aaa2cb,41,12be44)
@[ 6] 0x60876a6f nnotes._sqlpgcdl+927 (12bf44,12b9a4,0,12be44).
Date
Topic
Frequently asked question - How to analyze Notes/Domino NSDs? (Jean-Yves Riverin)
or call IBM support.
JYR
Subject: RE: Outlook crashes with an NSD message
Hi,
you only need the FATAL THREAD section like this one, not the whole file cause it’s too big 
############################################################
FATAL THREAD 1/2 [ domdsm:107a8:67076]
FP=0x0012a34c, PC=0x60069a86, SP=0x0012a2f0, stksize=92
EAX=0x01a3088c, EBX=0x01a48650, ECX=0x0000bffe, EDX=0x01a325e6
ESI=0x00004000, EDI=0x0032ff78, CS=0x0000001b, SS=0x00000023
DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010206
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x60069a86 nnotes._fdDelete@4+118 (4000,12a368,608770ef,4000)
@[ 2] 0x60069a0c nnotes._OSFileClose@4+12 (4000,12adc0,12a380,60872ea7)
@[ 3] 0x608770ef nnotes._sqloclose+15 (4000,12b59c,5010,0)
@[ 4] 0x60872ea7 nnotes._sqlpgclf+71 (12adc0,1aaa2cb,70,1aaa2f3)
@[ 5] 0x60885458 nnotes._sqlpgfdl+616 (12b9a4,1aaa2cb,41,12be44)
@[ 6] 0x60876a6f nnotes._sqlpgcdl+927 (12bf44,12b9a4,0,12be44).
Subject: RE: Outlook crashes with an NSD message
############################################################
thread 1/15: [ NLNOTES:031c:0d4c]
FP=0013cee4, PC=7c90eb94, SP=0013ce80, stkbase=00040000, stksize=94208
############################################################
[ 1] 0x7c90eb94 ntdll.KiFastSystemCallRet+0 (750,36ee80,0,13d368)
[ 2] 0x7c802532 KERNEL32.WaitForSingleObject+18 (750,36ee80,0,31c)
@[ 3] 0x601a5383 NNOTES._OSRunExternalScript@4+579 (13d680,200,0,7c884780)
@[ 4] 0x601a4344 NNOTES._OSFaultCleanup@12+1060 (0,0,0,13e1a4)
@[ 5] 0x601aec27 NNOTES._OSNTUnhandledExceptionFilter@4+183 (13e1a4,862c97b,13e040,7c863016)
[ 6] 0x0862c9de eS4dc3ui+903646 (13e1a4,0,0,0)
[ 7] 0x77c32f0f msvcrt._XcptFilter+353 (0,13e1a4,77c35cf5,13e1ac)
@[ 8] 0x00401e15 NLNOTES._WinMainCRTStartup+335 (12f0cc,7c90ee18,7ffd5000,0)
[ 9] 0x7c816fd7 KERNEL32.RegisterWaitForInputIdle+73 (401cc6,0,78746341,20)
############################################################
FATAL THREAD 1/15 [ NLNOTES:031c:0d4c]
FP=0x0013e580, PC=0x611ecee6, SP=0x0013e580, stksize=0
EAX=0x00000000, EBX=0x00000000, ECX=0x00000000, EDX=0x00000100
ESI=0x00000004, EDI=0x0013ebe8, CS=0x0000001b, SS=0x00000023
DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010213
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x611ecee6 nnotesws._DeskGetFilename@8+6 (0,13e598,80e0ee8,103)
@[ 2] 0x6163c1c6 nnotesws.intFailoverEntry+54 (103,13ebe8,8e0e0f4,130000)
@[ 3] 0x611cdd2b nnotesws.OpenResource+1067 (13ed64,0,13ed94,0)
@[ 4] 0x611cd8fc nnotesws._DeskOpenResourceExt@36+44 (13ed64,0,13ed94,0)
@[ 5] 0x619af06c nnotesws._ActivateHotSpotLink@12+812 (0,48f,8c3abfc,3)
@[ 6] 0x611c3202 nnotesws._PopUpEvent@20+1874 (8c3a948,8c3ad0c,3,450315)
@[ 7] 0x611a82ed nnotesws._HotSpotRunEvent@20+189 (8c3a948,8c3ad0c,3,450315)
@[ 8] 0x611a81e0 nnotesws._DocDispatchRABEvent@20+144 (8e0e0f4,73433ec,3,450315)
@[ 9] 0x6194bf01 nnotesws.@DocMouseButtonUp@16+833 (315,1,4a0e3a,8e0e0f4)
@[10] 0x611b0b03 nnotesws.@DocWindowsMessage@24+8339 (0,450315,13f430,13f424)
@[11] 0x611adb12 nnotesws._DocRichTextWndProc@16+258 (8e0e0f4,202,0,450315)
[12] 0x7e418734 USER32.GetDC+109 (611ada10,4a0e3a,202,0)
[13] 0x7e418816 USER32.GetDC+335 (0,611ada10,4a0e3a,202)
[14] 0x7e41c63f USER32.IsWindowUnicode+161 (611ada10,4a0e3a,202,0)
[15] 0x7e41c665 USER32.CallWindowProcW+27 (611ada10,4a0e3a,202,0)
[16] 0x5d095e5e COMCTL32.InitCommonControlsEx+10309 (4a0e3a,202,0,450315)
[17] 0x5d09602f COMCTL32.DefSubclassProc+145 (77fb058,4a0e3a,202,0)
[18] 0x5d095fe4 COMCTL32.DefSubclassProc+70 (4a0e3a,202,0,450315)
[19] 0x5d0d04bf COMCTL32.MakeDragList+9574 (4a0e3a,202,0,450315)
[20] 0x5d09602f COMCTL32.DefSubclassProc+145 (77fb058,4a0e3a,202,0)
[21] 0x5d0960be COMCTL32.DefSubclassProc+288 (4a0e3a,202,0,450315)
[22] 0x7e418734 USER32.GetDC+109 (5d09607d,4a0e3a,202,0)
[23] 0x7e418816 USER32.GetDC+335 (0,5d09607d,4a0e3a,202)
[24] 0x7e4189cd USER32.GetWindowLongW+295 (13f7c0,0,13f7e0,61221f28)
[25] 0x7e418a10 USER32.DispatchMessageW+15 (13f7c0,61221c60,61180000,1)
@[26] 0x61221f28 nnotesws._NEMMainLoop@4+712 (401000,12f0cc,15236c,0)
@[27] 0x0040156d NLNOTES._WinMain@16+1389 (400000,0,15236c,1)
@[28] 0x00401dfa NLNOTES._WinMainCRTStartup+308 (12f0cc,7c90ee18,7ffd5000,0)
[29] 0x7c816fd7 KERNEL32.RegisterWaitForInputIdle+73 (401cc6,0,78746341,20)
Subject: RE: Outlook crashes with an NSD message
Client crashes when using invalid Notes link with 6.5.4 client
Product:Lotus Notes > Lotus Notes > Version 6.5.4
Platform(s):Mac OS, Windows
Doc Number:1207931
Published 2007-07-09
Technote
Problem
You are using the Lotus Notes 6.5.4 client when it crashes. You were attempting to execute an invalid Notes URL link when the crash occurred.
You can observe this issue in the following situations:
When entering the link in the Address bar
When entering the link from the Operating System’s Start → Run command. In this scenario, the crash occurs after you are prompted for your password.
When referencing the link for a database reference within the Choose Web Page settings and adding a Web page to the Welcome Page frameset. The crash occurs when you click the Finish button and when you attempt to launch the Welcome Page. The crash also occurs when you switch Location documents if that document loads the Welcome Page.
This issue did not occur on the Notes 6.5.3 client or in earlier versions.
In earlier releases, one or more of the following errors can occur when you encounter the situations described above:
“File does not exist”
“You are not authorized to perform that operation”
“Unable to load frames content”
The Fatal Thread in the resulting NSD can vary, but may begin with one of these calls:
Example 1:
nnotesws._DeskGetFilename
nnotesws.intFailoverEntry
nnotesws.OpenResource
nnotesws._DeskOpenResourceExt
nnotesws._DeskOpenURL
nnotesws._DeskOpenURLString
nnotesws._DeskProcessInitialDbName
nnotesws._OpenNotefileFromName
nnotesws._DeskProcessClientOpenRequest
. . .
Example 2:
nnotesws._DeskGetFilename
nnotesws.intFailoverEntry
nnotesws.OpenResource
nnotesws._DeskOpenResourceExt
nnotesws.CEditorMonitorSubprogram::InstanceInit
nnotesws.CSubprogram::Create
nnotesws._EmonNewSubprogram
nnotesws._CreateEditSub
nnotesws.OpenResource
nnotesws._DeskOpenResourceExt
. . .
Solution
This issue was reported to Quality Engineering as SPR# JPIK6CJR5H, and has been addressed in 6.5.5 and 7.0. The fix eliminates the crash, and instead causes the expected error messages to appear.
Excerpt from the Lotus Notes and Domino Release 6.5.5 MR fix list (available at IBM Developer):
Web Navigator
SPR# JPIK6CJR5H - When entering an invalid URL Notes no longer crashes. This regression was introduced in 6.5.4.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Supporting Information:
The only workaround in 6.5.4 is to enter a valid and existing server name.
If the invalid URL entry exists within the Welcome Page design, work around this by renaming the bookmark.nsf file in the Notes data directory. A new file will be created when you restart Notes.
After upgrading to a release where the issue is fixed, you can use the renamed file.
A cumulative client hotfix (CCH) is available for Notes Client 6.5.4 that fixes the issue reported in SPR# JPIK6CJR5H. Since hotfixes do not receive the extensive testing that maintenance releases and fix packs do, customers are encouraged to implement workarounds or deploy a release containing the fix. However, if workarounds are not possible or applicable and you still need a fix, contact IBM Technical Support to request the CCH containing the fix for this issue.