Hi
Every time I try to view an attachment, my Lotus 8.0.1 crashes.
Release 8.0.1_NL1
Revision 20080222.1900 (Release 8.0.1)
standar configuration
Windows Vista compilation 6001 Service Pack 1
(It happend also previous to SP1 patch)
Hi
Every time I try to view an attachment, my Lotus 8.0.1 crashes.
Release 8.0.1_NL1
Revision 20080222.1900 (Release 8.0.1)
standar configuration
Windows Vista compilation 6001 Service Pack 1
(It happend also previous to SP1 patch)
Subject: View an Attachment Crash Lotus Client 8.0.1 - Any NSD?
Hi
Can you post the FATAL THREAD section of the NSD files with the few lines under it
For example:
############################################################
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: Here is the part of the NSD requested
I will reproduce the error as an administrator so the NSD can collect all the information possible. If cant find more info in the forums and in the knowledge base, I will open a supoort ticket. Thanks
############################################################
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
[ 1] 0x053874be kvvapi.VAPI_MessageBoxPlus+16290 (c6e130,1,b0a26,2)
[ 2] 0x0538ae22 kvvapi.VAPIWndProc+815 (b0a26,2,0,0)
[ 3] 0x7792f8d2 USER32.GetMessageW+147 (538aaf3,b0a26,2,0)
[ 4] 0x7792f794 USER32.GetWindowLongW+277 (0,538aaf3,b0a26,2)
[ 5] 0x77930817 USER32.ReleaseDC+122 (e0ee38,2,0,0)
[ 6] 0x77930a65 USER32.GetWindowThreadProcessId+461 (12d330,18,12da84,777a9980)
[ 7] 0x777a99ce ntdll.KiUserCallbackDispatcher+46 (0,12d670,12d684,48000000)
[ 8] 0x77923cc3 USER32.CharNextW+970 (0,12d794,12d684,48000000)
[ 9] 0x77923d9a USER32.CreateWindowExW+51 (0,12d794,12d914,48000000)
@[10] 0x61690a48 nnotesws.NEMCreateWindow@48+152 (621743d4,621743dc,48000000,0,0,0,0,0,0,0,0,0)
@[11] 0x61ec4b9a nnotesws.CViewerSubprogram::InstanceInit+266 (91f9014,12df28,12e2d0,91f9014,0,0,0,0,0,0,0,0)
@[12] 0x616c83e5 nnotesws.CSubprogram::Create+2133 (1,12df28,0,0,0,0,0,0,0,0,0,0)
@[13] 0x61ec4552 nnotesws.ViewerNewSubprogram@52+450 (0,0,9f10014,12e1d0,0,0,0,0,0,0,0,0,0)
@[14] 0x61e67339 nnotesws.AttachManager::DocFileView+1177 (0,0,d13b214,12e544,0,0,0,0,0,0,0,0,0)
@[15] 0x61f554c9 nnotesws.CAttachmentSelection::Command+89 (b072438,12e530,0,d11b414,0,0,0,0,0,0,0,0,0)
@[16] 0x617d10ff nnotesws.CSelectionManager::ProcessCommand+1167 (1,40180004,0,0,0,0,0,0,0,0,0,0,0)
@[17] 0x617d1151 nnotesws.NEMProcessCommand@12+33 (40180004,0,0)
@[18] 0x61b7e3d6 nnotesws.ProcessWksMsgExt@32+4326 (22,16780000,20000,60e30000,0,0,0,0)
@[19] 0x61693f9c nnotesws.CheckWksMQ@4+220 (0)
@[20] 0x61686c00 nnotesws.CDeskSubprogram::SubMessageProc+5744 (3274614)
@[21] 0x61684d09 nnotesws.MainWndProc@16+7881 (104be,570,0,0)
[22] 0x7792f8d2 USER32.GetMessageW+147 (61682e40,104be,570,0)
[23] 0x7792f794 USER32.GetWindowLongW+277 (0,61682e40,104be,570)
[24] 0x77930008 USER32.PeekMessageW+617 (61682e40,0,12f79c,6171a0b6)
[25] 0x77930060 USER32.DispatchMessageW+15 (12f77c,1,1049e,61680000)
@[26] 0x6171a0b6 nnotesws.NEMMainLoop@4+742 (4013d0)
@[27] 0x0040197b nlnotes.WinMain@16+1451 (617595a0,0,2a5b50,0)
@[28] 0x00401e39 nlnotes.WinMainCRTStartup+389 (7ffd5000,12ffd4,7778e4b6,7ffd5000)
[29] 0x76594911 kernel32.BaseThreadInitThunk+18 (7ffd5000,7791f5f9,0,0)
[30] 0x7778e4b6 ntdll.RtlInitializeExceptionChain+99 (401cb4,7ffd5000,0,0)
[31] 0x7778e489 ntdll.RtlInitializeExceptionChain+54 (401cb4,7ffd5000,0,78746341)
Subject: Seems related to user privileges
Hi
I’ve tried a lot of combinations. Login to the machine as administrator generates the same error. But If I “Run as Administrator” the application, then the “View Attachement” works as expected. Seems like UAC is conspiring against the application again.
The Lotus client was installed using an Administrator user and is used by a User member of the Advanced Users group.