• Crash

    By Alessandro Canedoli 9 years ago

    Hi Dominic, when i lauch mdigest, the server (9.0.1.) crash with nsd….
    Any ideas?

    Thanks!

    • By Dominic Porter 9 years ago

      Hi Alessandro,

      First off make sure you have installed Visual
      C++ Redistributable for Visual Studio 2015:
      https://www.microsoft.com/en-gb/download/details.aspx?id=48145

      You can also try running the add-in with the -d -S switches as this will skip most of the code and will just build a list of mail files to scan with debug enabled. If that is successful you can try -d -s as this will skip a detailed scan and gather basic database info with debug enabled.

      Just on the off chance it is a mail file which is causing the issue you could run a fixup -F on the mail directory or -J -F if you have transaction logging enabled.

      • By Alessandro Canedoli 9 years ago

        Hi Dominic,
        thanks for your response.

        C++ Redistributable is already installed.

        If I run -d -S it works, but if I run -d -s the server crash.
        Now i try the fixup.
        Thanks.

        • By Dominic Porter 9 years ago

          If you can get me the dump from the NSD maybe I can see what's triggering the crash.

          If you search the NSD for the word Fatal you should see something like this for nmdigest:

          (make sure you have nmdigest.pdb in the Domino program directory or it won't have much useful info)

          thread 1/5: [nmdigest: 3e34: 10f8] FATAL THREAD

          FP=0x60E58F3D48, PC=0x7FFD0CA76154, SP=0x60E58F3D48

          stkbase=0x60E5900000, total stksize=114688, used stksize=49848

          EAX=0x00005a4d, EBX=0x00000000, ECX=0x1D59B6F1E98, EDX=0x0008741c

          ESI=0x000927c0, EDI=0x000001f0, CS=0x1D500000033, SS=0x0000002b

          DS=0x00000000, ES=0x00000000, FS=0x1D500000000, GS=0x00000000 Flags=0x00000246

          [ 1] 0x7FFD0CA76154 ntdll.ZwWaitForSingleObject+20 (10,0,0,60E58F3E60)
          [ 2] 0x7FFD08ED75FF KERNELBASE.WaitForSingleObjectEx+143 (60E58F3EF4,60E58F4410,0,1f0)
          @[ 3] 0x7FFCD91EB1F2 nnotes.OSRunExternalScript+1666 (7,1,600000426,50)
          @[ 4] 0x7FFCD91EBE9A nnotes.OSFaultCleanupExt+362 (1,0,60E58FF840,0)
          @[ 5] 0x7FFCD91EC248 nnotes.OSRunNSD+40 (0,0,0,0)
          @[ 6] 0x7FFCD9250275 nnotes.OSNTUnhandledExceptionFilter+325 (60E58F5290,1,0,1)
          [ 7] 0x7FFD08F15FA7 KERNELBASE.UnhandledExceptionFilter+343 (7FF664C3839C,7FFD0CB01A70,0,7FF664C165F7)
          [ 8] 0x7FFD0CA7ED1B ntdll.memset+9115 (60E58FF120,60E58F5EF0,7FFD0BC08364,60E58FF7D0)
          [ 9] 0x7FFD0CA66BD6 ntdll.C_specific_handler+150 (0,60E58F5400,60E58F5A00,60E58F5400)
          [10] 0x7FFD0CA7AB9D ntdll.          chkstk+285 (7FFD0BCA34B0,60E58F5A00,0,0)
          [11] 0x7FFD0CA19913 ntdll.RtlImageNtHeaderEx+1155 (0,0,60E58FEB80,0)
          [12] 0x7FFD0CA79CBA ntdll.KiUserExceptionDispatcher+58 (1D5A3F019D8,7FFCD91F4458,7FF664C2CD18,60E58FEB80)
          @[13] 0x7FF664BF9F00 nmdigest.BaseNotesDocument::getItemValueString+192 (60E58FEC00,60E58FECB8,60E58FEB80,7FF664C12452) @basenotesdocument.cpp(520)
          @[14] 0x7FF664C0CA15 nmdigest.NotesDocument::getItemValueString+101 (1D59B73D5C0,60E58FEE40,60E58FEC68,7FF664C11EB4) @notesdocument.cpp(239)
          @[15] 0x7FF664C0B381 nmdigest.NotesDatabase::setIconFlags+321 (0,60E58FEEF0,60E58FEE40,60E58FEF78) @notesdatabase.cpp(307)
          @[16] 0x7FF664C0B8F4 nmdigest.NotesDatabase::newDatabase+276 (60E58FEE40,60E58FEF78,60E58FEEF0,1D59B70D6C0) @notesdatabase.cpp(396)
          @[17] 0x7FF664C0A0BC nmdigest.archiveScan+604 (60E58FEEF0,1D59B6E1400,4,0) @addinmain.cpp(301)
          @[18] 0x7FF664C08A64 nmdigest.AddInMain+1540 (1D59B839828,0,0,11aa0) @addinmain.cpp(94)
          @[19] 0x7FF664BF1247 nmdigest.NotesMain+55 (0,0,7FF664BF0000,60E58FF7B0)
          @[20] 0x7FF664BF117C nmdigest.main+380 (0,0,0,4)
          @[21] 0x7FF664BF1018 nmdigest.main+24 (0,0,0,0)
          @[22] 0x7FF664C1259C nmdigest.__tmainCRTStartup+324 (0,0,0,0) @crt0.c(255)
          [23] 0x7FFD0BC08364 KERNEL32.BaseThreadInitThunk+20 (0,0,0,0)
          [24] 0x7FFD0CA370D1 ntdll.RtlUserThreadStart+33 (0,0,0,0)

          • By Alessandro Canedoli 9 years ago

            Hi, here the stack :

            thread 1/7: [nmdigest: 0d7c: 0e78] FATAL THREAD

            FP=0x001b38b8, PC=0x7769bd7a, SP=0x001b38b8

            stkbase=0x001c0000, total stksize=73728, used stksize=51016

            EAX=0x70ed17af, EBX=0x00000000, ECX=0x001b2c00, EDX=0x00000020

            ESI=0x000927c0, EDI=0x0000041c, CS=0x00000033, SS=0x0000002b

            DS=0x00000000, ES=0x00000000, FS=0x00000000, GS=0x00000000 Flags=0x00000287

            [ 1] 0x7769bd7a ntdll.ZwWaitForSingleObject+10 (0,1b42d8,7FEF8597E38,ffffffff)
            [ 2] 0x7FEFD4810AC KERNELBASE.WaitForSingleObjectEx+156 (0,1b3a60,0,41c)
            @[ 3] 0x7FEF70D952A nnotes.FRSendCommandToService+1450 (1b42d8,1b42d8,258,7FEF70D7F00)
            @[ 4] 0x7FEF70DB0B6 nnotes.OSRunExternalScript+1334 (d7c,0,0,5)
            @[ 5] 0x7FEF70DBA4A nnotes.FRTerminateWindowsResources+1738 (0,5,1,347a80)
            @[ 6] 0x7FEF70DC1D9 nnotes.OSFaultCleanupExt+1177 (1,0,1bfea0,FFFFFFFFFFFFFFF)
            @[ 7] 0x7FEF70DC7D7 nnotes.OSFaultCleanup+23 (0,0,0,0)
            @[ 8] 0x7FEF7140067 nnotes.OSNTUnhandledExceptionFilter+423 (1b5ab0,0,1,776d2365)
            [ 9] 0x774cbc10 kernel32.UnhandledExceptionFilter+352 (1b5ab0,6,0,7FE00000001)
            [10] 0x776d0108 ntdll.EtwEventSetInformation+7688 (1b66f0,13F415607,1b6200,7FEEEF3F5D7)
            [11] 0x77667958 ntdll.C_specific_handler+156 (1c0000,1bfea0,1bfea0,7778f818)
            [12] 0x7767812d ntdll.RtlDecodePointer+173 (1c0000,7753dd88,127ec,3d7d50)
            [13] 0x7766855f ntdll.RtlUnwindEx+3007 (1b66f0,1b6200,0,0)
            [14] 0x7769bcb8 ntdll.KiUserExceptionDispatcher+46 (500,1,13F427118,1bf3e0)
            @[15] 0x13F401581 nmdigest.BaseNotesDocument::getItemValueString+193 (1bf3e0,1bf4e0,FFFFFFFFFFFFFFF,1bf4e0)
            @[16] 0x13F41AEAF nmdigest.NotesDocument::getItemValueString+47 (3e1420,FFFFFFFFFFFFFFF,1bf3e0,FFFFFFFFFFFFFFF)
            @[17] 0x13F40DCE3 nmdigest.DominoDirectory::getMailFiles+979 (0,0,1bf808,1bf798)
            @[18] 0x13F415BE7 nmdigest.buildWorkQueue+583 (3bd940,1,0,0)
            @[19] 0x13F415607 nmdigest.AddInMain+1559 (669608,0,0,441248)
            @[20] 0x13F3E1247 nmdigest.NotesMain+55 (0,0,13F3E0000,1bfe20)
            @[21] 0x13F3E117C nmdigest.main+380 (0,0,0,1)
            @[22] 0x13F3E1018 nmdigest.main+24 (0,0,0,0)
            @[23] 0x13F41E27F nmdigest.            tmainCRTStartup+271 (0,0,0,0)
            [24] 0x774459cd kernel32.BaseThreadInitThunk+13 (0,0,0,0)
            [25] 0x7767a561 ntdll.RtlUserThreadStart+33 (0,0,0,0)

            • By Dominic Porter 9 years ago

              Looks like one of the Person or Mail-In database documents maybe the cause.

              Do any of them have a blank entry for the mail file path?

              • By Dominic Porter 9 years ago

                Or in the FullName field

                • By Alessandro Canedoli 9 years ago

                  maybe the document with other internet address mail system?

                  • By Dominic Porter 9 years ago

                    Could be. I'll try and reproduce the issue and let you know.

                    • By Alessandro Canedoli 9 years ago

                      Ok, I try to identify this user and change the value of “mailserver” field.
                      Thanks!

                      • By Dominic Porter 9 years ago

                        Hi Alessandro,

                        I've tried to reproduce the issue but not had any luck so I'm thinking that it could be a corrupt document.

                        Try a null edit on all the Person docs or if there are a lot create a new Toolbar button which runs the code:
                        @Command([ToolsRefreshSelectedDocs])
                        Select all the docs and press the button.

                        • By Alessandro Canedoli 9 years ago

                          Hello Dominic,
                          I've done the refresh and I've found 2 person document with internet address malformed.
                          After I've resolved this, I've done the refresh correctly, but the server crash again, here the dump :

                          thread 1/7: [nmdigest: 2570: 2ac4] FATAL THREAD

                          FP=0x00293998, PC=0x775fbd7a, SP=0x00293998

                          stkbase=0x002a0000, total stksize=61440, used stksize=50792

                          EAX=0x7841ce6a, EBX=0x00000000, ECX=0x00292ce0, EDX=0x00000020

                          ESI=0x000927c0, EDI=0x000003f4, CS=0x00000033, SS=0x0000002b

                          DS=0x00000000, ES=0x00000000, FS=0x00000000, GS=0x00000000 Flags=0x00000287

                          [ 1] 0x775fbd7a ntdll.ZwWaitForSingleObject+10 (0,2943b8,7FEE5694F68,ffffffff)
                          [ 2] 0x7FEFD4F10AC KERNELBASE.WaitForSingleObjectEx+156 (0,293b40,0,3f4)
                          @[ 3] 0x7FEE41A96BA nnotes.FRSendCommandToService+1450 (2943b8,2943b8,258,7FEE41A8090)
                          @[ 4] 0x7FEE41AB246 nnotes.OSRunExternalScript+1334 (2570,0,0,5)
                          @[ 5] 0x7FEE41ABBDA nnotes.FRTerminateWindowsResources+1738 (0,5,1,77a80)
                          @[ 6] 0x7FEE41AC369 nnotes.OSFaultCleanupExt+1177 (1,0,29ff80,FFFFFFFFFFFFFFF)
                          @[ 7] 0x7FEE41AC967 nnotes.OSFaultCleanup+23 (0,0,0,0)
                          @[ 8] 0x7FEE4210397 nnotes.OSNTUnhandledExceptionFilter+423 (295b90,0,1,50)
                          [ 9] 0x7742bc10 kernel32.UnhandledExceptionFilter+352 (295b90,6,0,7FE00000001)
                          [10] 0x77630108 ntdll.EtwEventSetInformation+7688 (2967d0,13FCB5607,2962e0,7FEEFA2F5D7)
                          [11] 0x775c7958 ntdll.C_specific_handler+156 (2a0000,29ff80,29ff80,776ef818)
                          [12] 0x775d812d ntdll.RtlDecodePointer+173 (2a0000,7749dd88,127ec,0)
                          [13] 0x775c855f ntdll.RtlUnwindEx+3007 (2967d0,2962e0,0,0)
                          [14] 0x775fbcb8 ntdll.KiUserExceptionDispatcher+46 (500,1,13FCC7118,29f4c0)
                          @[15] 0x13FCA1581 nmdigest.BaseNotesDocument::getItemValueString+193 (29f4c0,29f5c0,FFFFFFFFFFFFFFF,29f5c0)
                          @[16] 0x13FCBAEAF nmdigest.NotesDocument::getItemValueString+47 (10c280,FFFFFFFFFFFFFFF,29f4c0,FFFFFFFFFFFFFFF)
                          @[17] 0x13FCADCE3 nmdigest.DominoDirectory::getMailFiles+979 (0,0,29f8e8,29f878)
                          @[18] 0x13FCB5BE7 nmdigest.buildWorkQueue+583 (eda30,1,0,0)
                          @[19] 0x13FCB5607 nmdigest.AddInMain+1559 (709608,0,0,1f0398)
                          @[20] 0x13FC81247 nmdigest.NotesMain+55 (0,0,13FC80000,29ff00)
                          @[21] 0x13FC8117C nmdigest.main+380 (0,0,0,1)
                          @[22] 0x13FC81018 nmdigest.main+24 (0,0,0,0)
                          @[23] 0x13FCBE27F nmdigest.                          tmainCRTStartup+271 (0,0,0,0)
                          [24] 0x773a59cd kernel32.BaseThreadInitThunk+13 (0,0,0,0)
                          [25] 0x775da561 ntdll.RtlUserThreadStart+33 (0,0,0,0)

                          • By Dominic Porter 9 years ago

                            Still looks like when the add-in is trying to access the field it's crashing. This will need more investigation.
                            Send me your email address here:
                            http://www.dbpsolutions.com/contact
                            and I will send you the latest alpha build and I will add in some more debug information so we can hunt down the document which is causing the crash.