Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Upgrade from 1.2.16 to 1.2.17 error

Upgrade from 1.2.16 to 1.2.17 error

Scheduled Pinned Locked Moved Support
10 Posts 4 Posters 62.0k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • U
    U
    Andreas@rc
    wrote on last edited by
    #1

    Hi,

    I just tried to update our NetXMS server from 1.2.16 to 1.2.17, but the updated version wont start.
    DB check was ok, installation went without problems, but after I tried to start the server, I got the error found in the attachment.

    Server is a Win 2003 R2.


    Upgrade_error.PNG

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      seems like some file(s) was not updated. Can you please find out what file in bin directory contains string "getKeyByIndex"?

      Best regards,
      Victor

      1 Reply Last reply
      0
      • U
        U
        Andreas@rc
        wrote on last edited by
        #3

        @victor said in Upgrade from 1.2.16 to 1.2.17 error:

        Hi,

        seems like some file(s) was not updated. Can you please find out what file in bin directory contains string "getKeyByIndex"?

        Best regards,
        Victor

        Hi,

        sure but how? ... MS search only looks into "readable" files (e.g *.txt, *.doc, ...) but as stated in the screenshot, "getKeyByIndex" is found in serveral DLL's (and *.pds's), "libnetxms.dll", "libnetxms.pdb" or "libnxsl.dll" to name some.
        Looking in all of them is kinda ... troublesome.

        1 Reply Last reply
        0
        • L
          L
          lindeamon
          wrote on last edited by
          #4

          you can use totalcommander.
          go into to the root directory of netxms, open the search dialog, search for all files by putting "*" and put the requested search string in the "find text"

          Lindeamon

          1 Reply Last reply
          0
          • U
            U
            Andreas@rc
            wrote on last edited by
            #5

            Hi,

            sorry for the late response.
            The error was most likely the some one start the install after this system was running and uncheck most of the components. And since I started the installation with /silent, most parts weren't installed.

            Now, I have the same problem as described here https://www.netxms.org/forum/general-support/error-while-upgrading-to-1-2-17/. The core service won't start, debug (per netxmsd.conf or command line) doesn't work (more precisely, no information are logged). Reboot didn't help.

            1 Reply Last reply
            0
            • T
              T
              tonyams
              wrote on last edited by
              #6

              Hi:

              I'm having the same problem as well. Using Windows Server 2003 R2. Netxms core service won't start.

              Regards,

              1 Reply Last reply
              0
              • V
                V
                Victor Kirhenshtein
                wrote on last edited by
                #7

                Hi,

                is there anything in log? If not, try to set logging to file in netxmsd.conf and run netxmsd from command line with full debug:

                netxmsd.exe -D9

                Best regards,
                Victor

                1 Reply Last reply
                0
                • U
                  U
                  Andreas@rc
                  wrote on last edited by
                  #8

                  @user55116 said in Upgrade from 1.2.16 to 1.2.17 error:

                  Hi,

                  sorry for the late response.
                  The error was most likely the some one start the install after this system was running and uncheck most of the components. And since I started the installation with /silent, most parts weren't installed.

                  Now, I have the same problem as described here https://www.netxms.org/forum/general-support/error-while-upgrading-to-1-2-17/. The core service won't start, debug (per netxmsd.conf or command line) doesn't work (more precisely, no information are logged). Reboot didn't help.

                  @victor said in Upgrade from 1.2.16 to 1.2.17 error:

                  Hi,

                  is there anything in log? If not, try to set logging to file in netxmsd.conf and run netxmsd from command line with full debug:

                  netxmsd.exe -D9

                  Best regards,
                  Victor

                  Hi,

                  as I said before, even with enabled debuging, no log is written. It looks like the programms hangs before writting anything to the log file is possible.

                  1 Reply Last reply
                  0
                  • V
                    V
                    Victor Kirhenshtein
                    wrote on last edited by
                    #9

                    How's your netxmsd.conf looks like? Can you run nxdbmgr.exe or any other command line tool?

                    Best regards,
                    Victor

                    1 Reply Last reply
                    0
                    • U
                      U
                      Andreas@rc
                      wrote on last edited by
                      #10

                      netxmsd.conf:

                      LogFile = E:\NetXMS\log\netxms.log
                      DBDriver = sqlite.ddr
                      DBName = E:\NetXMS\database\netxms_db
                      LogFailedSQLQueries = yes
                      DebugLevel = 9
                      

                      nxdbmgr is still working.

                      1 Reply Last reply
                      0

                      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                      With your input, this post could be even better 💗

                      Register Login
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      Powered by NodeBB Contributors
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Users
                      • Groups