Domino Designer Crashes on Open

I have a problem with Domino Desgner where it crashes every time I try to open it.

I have tried:

  • Opening Designer on its own

  • Opening Designer from the Notes Client

  • Running ZapNotes3

  • Deleting the Workspace Folder

  • Running a repair

Nothing seems to work. I have copied the FATAL section of the NSD if anyone can help it would be appreciated.

Thanks

############################################################

FATAL THREAD 1/32 [ NLNOTES: 1734: 1400]

FP=0x0013d17c, PC=0x60001a29, SP=0x0013d170

stkbase=00140000, total stksize=212992, used stksize=11920

EAX=0x0d5da84a, EBX=0x0d050fe4, ECX=0x00000009, EDX=0x0d052820

ESI=0x0d051000, EDI=0x0d5da866, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00210283

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

@[ 1] 0x60001a29 nnotes.Cmovmem@12+329 (d051024,d5cc088,fffe)

@[ 2] 0x600041d4 nnotes.ODSReadMemory@16+116 (13d338,3,d5cc088,fffe)

@[ 3] 0x6009dc02 nnotes.CSiteMapEntry::GetToolbarData+642 (6ab3618,0,13d5c4,13d5b4)

@[ 4] 0x6306da42 nnotesws.CNEMToolbarEntryStore::GetElementData+66 (13d654,0,6aa5018,6ad1c18)

@[ 5] 0x6306d0a6 nnotesws.CNEMToolbar::ReadConfig+390 (6aa4d18,6aa4d18,6aa5018,0)

@[ 6] 0x630751c6 nnotesws.CNEMToolbarMgr::AddToolbar+70 (4,2,4,1)

@[ 7] 0x630a09d1 nnotesws.CNEMToolbarMgr::ShowAllToolbars+241 (0,1,1,0)

@[ 8] 0x630bb2ad nnotesws.NEMSmartCreateIconbar@4+141 (6aa5018)

@[ 9] 0x630d4936 nnotesws.InitHomeBase@8+662 (b06e6,100100)

@[10] 0x6306873b nnotesws.CSubprogram::Create+3227 (6,13dbbc)

@[11] 0x630a53fb nnotesws.EmonNewSubprogram@48+539 (0,3ea,0,0,0,0,0,0,0,0,0,0)

@[12] 0x63597d53 nnotesws.CreateEditSub@52+1651 (0,0,4f01a6c,0,0,0,0,0,0,0,0,0,0)

@[13] 0x6359a613 nnotesws.OpenResource+4819 (13e604,1ba1b24,0,0,0,0,0,0,0,0,0,0,0)

@[14] 0x63069cf0 nnotesws.DeskOpenResourceExt@36+48 (13e604,0,0,0,0,0,0,0,0)

@[15] 0x6356971d nnotesws.DeskLaunchDefaultWelcomePage+269 (0,103,0,0,0,0,0,0,0)

@[16] 0x635730f0 nnotesws.ProcessWksMsgExt@32+6736 (25,6540000,20000,1,0,0,0,0)

@[17] 0x63034a6b nnotesws.CheckWksMQ@4+427 (0)

@[18] 0x635749ac nnotesws.ProcessDeskPollTimer+124 (13f68c)

@[19] 0x630259b4 nnotesws.CDeskSubprogram::SubMessageProc+660 (1c18618)

@[20] 0x63024e2e nnotesws.MainWndProc@16+8046 (1f03b0,113,1,0)

[21] 0x7e418734 USER32.GetDC+109 (63022ec0,1f03b0,113,1)

[22] 0x7e418816 USER32.GetDC+335 (0,63022ec0,1f03b0,113)

[23] 0x7e4189cd USER32.GetWindowLongW+295 (13f7ac,0,13f7d0,630baa23)

[24] 0x7e418a10 USER32.DispatchMessageW+15 (13f7ac,1,70100,63020000)

@[25] 0x630baa23 nnotesws.NEMMainLoop@4+803 (4013a0)

@[26] 0x004019cb NLNOTES.WinMain@16+1579 (630f9de0,0,16231d,0)

@[27] 0x00401e89 NLNOTES.WinMainCRTStartup+389 (12cfb0,7c90e920,7ffd6000,80544c7d)

[28] 0x7c817077 kernel32.RegisterWaitForInputIdle+73 (401d04,0,78746341,20)

Subject: Info from development

This is a known issue that is caused by a corrupted bookmark.nsf. The only current workaround is to rename your bookmark.nsf and have it be recreated. Checking to see if there is a way to salvage any of your bookmark.nsf

ADC7MF38E: AutoADC: ACCESS_VIOLATION in process nlnotes and function Cmovmem

Subject: That worked

That worked and solved the issue - thank you.