NotesUIWorkspace.Folder causes NSD

I am not sure if this is a known problem or not but…

I am trying to capture some information at the time a user moves a document to a folder. This will allow me to measure whether or not the user has actioned a mail message within a given SLA.

I have changed the Folder\Move To Folder action from @Command(Folder) and replaced it with the following lotusscript:

Sub Click(Source As Button)

Dim s As New NotesSession	

Dim cdb As NotesDatabase

Dim dc As NotesDocumentCollection

Dim ws As New NotesUIWorkspace

Set cdb = s.CurrentDatabase	

Set dc = cdb.UnprocessedDocuments



Call MoveToFolder(dc)



Call ws.folder(, False)

End Sub

The MoveToFolder script is contained in a seperate script library and contains code that updates each document with the time it was moved, who moved it and it then evaluates whether or not the SLA was achieved.

This works fine as long as the user selects the message from the view and then clicks on the action, however, if the user is in the message (as a uidoc) and then clicks on the action Notes crashes (runs NSD)

I have removed the call to MoveToFolder and it makes no difference.

Is it not possible to run the lotus script Notesuiworkspace.folder command from within an open document?

The help file states: that this method moves the current selected or open document.

Has anyone come across this problem before and if so do you have any suggestions?

Thanks in advance

Alex

Subject: NotesUIWorkspace.Folder causes NSD

Hi,

Post the FATAL THREAD section of your nsd files (Located in Data\IBM_TECHNICAL_SUPPORT) or look here—

JYR

Subject: RE: NotesUIWorkspace.Folder causes NSD

Thanks for looking, here is the FATAL THREAD section from my NSD:

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

FATAL THREAD 1/10 [ NLNOTES:0d54:0768]

FP=0x0013de7c, PC=0x6005909f, SP=0x0013de38, stksize=68

EAX=0x0659dcd0, EBX=0x00000000, ECX=0x00000000, EDX=0x00b55b88

ESI=0x06122954, EDI=0x0013de74, CS=0x0000001b, SS=0x00000023

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

Exception code: c0000005 (ACCESS_VIOLATION)

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

@[ 1] 0x6005909f nnotes.LSsInstance::AdtCallBack+223 (b55b88,611de540,106,6122938)

@[ 2] 0x60069201 nnotes.LScObjCli::CallAdtProc+145 (61228f8,106,0,72a67b8)

@[ 3] 0x600913eb nnotes.LScObjCli::DropDead+27 (61228f8,72a66b4,72a6668,65b001e)

@[ 4] 0x60027d57 nnotes.LSsThread::ClearEventArgs+71 (72a6668,1,72a6668,65b2aa8)

@[ 5] 0x60021336 nnotes.LSsThread::NRun+838 (72a6668,b57630,b55b88,13e020)

@[ 6] 0x60023106 nnotes.LSsThread::Run+182 (72a6668,13e008,61a941de,b55b88)

@[ 7] 0x600b475a nnotes.LSsInstance::Resume+26 (b55b88,b57568,0,b57630)

@[ 8] 0x61a941de nnotesws.LSEcInstance::StepClientScript+110 (b57568,70534f0,b57568,0)

@[ 9] 0x611a83a3 nnotesws.LSEcInstance::Resume+243 (b57568,0,70534f0,0)

@[10] 0x61a94519 nnotesws.LSEcInstance::DebugClientScript+169 (b57568,65b2aa8,2,13e10c)

@[11] 0x61a92ae4 nnotesws._LSEDebugCommand@12+20 (b57568,65b2aa8,2,13e2dc)

@[12] 0x61a92a62 nnotesws._LSEDebugStepInto@8+18 (b57568,65b2aa8,70534f0,708a670)

@[13] 0x615c2b5d nnotesws.CLSDDocument::DebugScript+205 (70534f0,2,80000000,66)

@[14] 0x615c5fb9 nnotesws.CDebuggerPaneSubprogram::ExecuteScript+217 (7073470,2,66,0)

@[15] 0x615c56de nnotesws.CDebuggerPaneSubprogram::WMCtrlNotify+78 (708a670,13e03d8,66,13e41c)

@[16] 0x615c540b nnotesws.CDebuggerPaneSubprogram::SubMessageProc+955 (708a670,111,80000027,12802fa)

@[17] 0x61184a06 nnotesws._MainWndProc@16+6966 (13e03d8,111,80000027,12802fa)

[18] 0x77d48734 USER32.GetDC+109 (61182ed0,13e03d8,111,80000027)

[19] 0x77d48816 USER32.GetDC+335 (0,61182ed0,13e03d8,111)

[20] 0x77d4b89b USER32.GetParent+364 (97fce8,8666b8,80000027,12802fa)

[21] 0x77d5f3e3 USER32.SendMessageA+73 (13e03d8,111,80000027,12802fa)

@[22] 0x6118aa12 nnotesws._BmpButtonWndProc@16+2866 (775a5f4,202,0,c003c)

[23] 0x77d48734 USER32.GetDC+109 (61189ee0,12802fa,202,0)

[24] 0x77d48816 USER32.GetDC+335 (0,61189ee0,12802fa,202)

[25] 0x77d489cd USER32.GetWindowLongW+295 (13ebcc,0,13eb84,77d5e097)

[26] 0x77d48a10 USER32.DispatchMessageW+15 (13ebcc,77d5f39a,68,13ebcc)

[27] 0x77d5e097 USER32.IsDialogMessageW+219 (13e03d8,89a130,7073470,7b02d6)

@[28] 0x612ce365 nnotesws.ModelessWindowDispatch+229 (4,7073470,7053070,659dca8)

@[29] 0x612ce5ef nnotesws._NEMMainLoopIDE@8+271 (0,7053070,0,70534f0)

@[30] 0x615b4c7e nnotesws.LSDThread::RaiseEvent+318 (10,659dcd0,659dca8,b57568)

@[31] 0x611de6b1 nnotesws.CLSUIDocument::RaiseEvent+225 (7756ef4,659dca8,61b39638,0)

@[32] 0x611df3db nnotesws._DocScriptRaiseEvent@28+555 (70534f0,659dca8,d5,0)

@[33] 0x612ad07a nnotesws.CBaseDocSelection::CommonCommand+1050 (65a62a8,13f22c,0,659dca8)

@[34] 0x612696a8 nnotesws.CRWDocSelection::CommonCommand+5064 (65a62a8,13f22c,659dca8,0)

@[35] 0x6155db81 nnotesws.CROActionSetSelection::ExecuteScriptedObject+129 (77498f4,659dca8,0,d5)

@[36] 0x61569930 nnotesws.CROActionSelection::Execute+224 (659dca8,6302c4,77498f4,0)

@[37] 0x6155e180 nnotesws.CROActionSetSelection::CommonCommand+96 (77498f4,13f34c,13f3c0,6156eb20)

@[38] 0x6156ed47 nnotesws._ActionBarWndProc@16+551 (0,111,6002401d,d50544)

[39] 0x77d48734 USER32.GetDC+109 (6156eb20,6302c4,111,6002401d)

[40] 0x77d48816 USER32.GetDC+335 (0,6156eb20,6302c4,111)

[41] 0x77d4b89b USER32.GetParent+364 (89ce38,898538,6002401d,d50544)

[42] 0x77d5f3e3 USER32.SendMessageA+73 (6302c4,111,6002401d,d50544)

@[43] 0x6118aafd nnotesws._BmpButtonWndProc@16+3101 (777ccf4,111,6002401d,0)

[44] 0x77d48734 USER32.GetDC+109 (61189ee0,d50544,111,6002401d)

[45] 0x77d48816 USER32.GetDC+335 (0,61189ee0,d50544,111)

[46] 0x77d489cd USER32.GetWindowLongW+295 (13f7c0,0,13f744,77d5e097)

[47] 0x77d48a10 USER32.DispatchMessageW+15 (13f7c0,77d5f39a,d0,13f7c0)

[48] 0x77d5e097 USER32.IsDialogMessageW+219 (6302c4,989ce0,0,77d5f39a)

@[49] 0x612ce365 nnotesws.ModelessWindowDispatch+229 (8,61221c30,61180000,1)

@[50] 0x61221e92 nnotesws._NEMMainLoop@4+610 (401000,12eed0,152374,0)

[51] 0x0040156d NLNOTES (400000,0,152374,1)

[52] 0x00401dfa NLNOTES (12eed0,7c90ee18,7ffde000,8054a6ed)

[53] 0x7c816fd7 KERNEL32.RegisterWaitForInputIdle+73 (401cc6,0,78746341,20)

Regards

Alex

Subject: RE: NotesUIWorkspace.Folder causes NSD

Hi,

Your NSD

@[31] 0x611de6b1 nnotesws.CLSUIDocument::RaiseEvent+225 (7756ef4,659dca8,61b39638,0)

@[32] 0x611df3db nnotesws._DocScriptRaiseEvent@28+555 (70534f0,659dca8,d5,0)

@[33] 0x612ad07a nnotesws.CBaseDocSelection::CommonCommand+1050 (65a62a8,13f22c,0,659dca8)

@[34] 0x612696a8 nnotesws.CRWDocSelection::CommonCommand+5064 (65a62a8,13f22c,659dca8,0)

@[35] 0x6155db81 nnotesws.CROActionSetSelection::ExecuteScriptedObject+129 (77498f4,659dca8,0,d5)

@[36] 0x61569930 nnotesws.CROActionSelection::Execute+224 (659dca8,6302c4,77498f4,0)

@[37] 0x6155e180 nnotesws.CROActionSetSelection::CommonCommand+96 (77498f4,13f34c,13f3c0,6156eb20)

@[38] 0x6156ed47 nnotesws._ActionBarWndProc@16+551 (0,111,6002401d,d50544)

From the technote:

Notes crashes when calling Uidoc.Refresh from an embedded single category view’s action

A common crash traceback from an NSD file might show this on the crashing thread:

notesws.CLSUIDocument::RaiseEvent

nnotesws._DeskExecuteLotusScript

nnotesws.CViewSelection::CommonCommand

nnotesws.CROActionSetSelection::ExecuteScriptedObject

nnotesws.CROActionSelection::Execute

nnotesws.CROActionSetSelection::CommonCommand

nnotesws._ActionBarWndProc

Or this one

Calling the LotusScript EditDocument Method From a Form Action can Cause Notes to Crash

There is a few missing info, but it’s the only thing i’ve found.

JYR

Subject: RE: NotesUIWorkspace.Folder causes NSD

Jean-Yves

Thank yopu very much for your help…The second link on your response contained the solution and I have moved the code to an agent and am calling the agent from the form action and it works fine.

Many thanks

Alex