I have a windows server that has been running NetXMS 5.02 fine for some time, and I attempted an install ( upgrade ) to 7.0.2, and once upgraded the core services will not start.  Can someone please assist me in getting this running again, I have restored from backup and tried several times with the same results.

I receive a error in the windows log below:

Log Name:      Application
Source:        Application Error
Date:          11/4/2026 7:03:26 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER-MONITOR2.arapahoe.internal
Description:
Faulting application name: prunsrv.exe, version: 1.3.1.0, time stamp: 0x6271349d
Faulting module name: prunsrv.exe, version: 1.3.1.0, time stamp: 0x6271349d
Exception code: 0xc0000005
Fault offset: 0x0000000000007130
Faulting process id: 0xe14
Faulting application start time: 0x01dd6c6542bc4ed1
Faulting application path: C:\NetXMS\bin\prunsrv.exe
Faulting module path: C:\NetXMS\bin\prunsrv.exe
Report Id: 81fdebe0-80ec-4cc5-ba52-857bed319fc8
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2026-11-04T14:03:26.571015700Z" />
    <EventRecordID>12128</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER-MONITOR2.arapahoe.internal</Computer>
    <Security />
  </System>
  <EventData>
    <Data>prunsrv.exe</Data>
    <Data>1.3.1.0</Data>
    <Data>6271349d</Data>
    <Data>prunsrv.exe</Data>
    <Data>1.3.1.0</Data>
    <Data>6271349d</Data>
    <Data>c0000005</Data>
    <Data>0000000000007130</Data>
    <Data>e14</Data>
    <Data>01dd6c6542bc4ed1</Data>
    <Data>C:\NetXMS\bin\prunsrv.exe</Data>
    <Data>C:\NetXMS\bin\prunsrv.exe</Data>
    <Data>81fdebe0-80ec-4cc5-ba52-857bed319fc8</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Hi,

The crash in prunsrv.exe is the Reporting Server service ("NetXMS Reporting Server"), not the core. The NetXMS Core service is netxmsd.exe and gets its own service entry. The reporting server needs a 64-bit Java 11 or later, where 5.0 ran on Java 8. If you don't use reports, set that service to Disabled for now.

For the core itself, what is in DBDriver in C:\NetXMS\etc\netxmsd.conf? I suspect it's mysql.ddr. In 7.0 the separate MySQL driver was removed and MySQL is served by the MariaDB driver. The upgrade keeps your old config and leaves the old 5.0 mysql.ddr in place, and that driver can't be loaded by 7.0. The server stops at startup, and the database upgrade step in the installer fails silently for the same reason. If that's the case, change the line in netxmsd.conf to DBDriver = mariadb, then run:

cd C:\NetXMS\bin
nxdbmgr -c C:\NetXMS\etc\netxmsd.conf upgrade
net start netxmsd

A direct upgrade from 5.0.2 to 7.0.2 is fine. nxdbmgr goes through all the intermediate versions itself.

If your database isn't MySQL, or it still won't start, please attach the last 50-100 lines of C:\NetXMS\log\netxmsd.log.

Thank you for the information, in this case the server uses a Postgre database, I presume because that database was already on that server.  The config file does call out the appropriate database driver, and is shown below.  I stopped the reporting service for now, and the prunsrv.exe error did go away, however when I attempt to login via the local client I get a "Connection refused getsockopt" error...  I don't know of any conflicts where can I look to find info on this if you don't know the answer?  Most googling only refers to Minecraft serving...



#
# Configuration file generated on Wed Nov  5 11:42:51 2025
#

DBDriver=pgsql.ddr
DBServer=localhost
DBName=netxms_db
DBLogin=techdept
DBPassword=...
LogFile=C:\NetXMS\log\netxmsd.log

I've removed the database password from your post. It was public for a while, so please change it anyway.

"Connection refused" means the core service still isn't running, so the client has nothing to connect to. The most likely reason is that the database schema wasn't upgraded. The installer runs the upgrade hidden, so if it fails you see nothing, and netxmsd refuses to start on an old schema. Please run this from an elevated command prompt:

cd C:\NetXMS\bin
nxdbmgr upgrade
netxmsd -D 4

The first command shows any upgrade error directly. The second runs the server in the foreground with debug output, so you can see where it stops. If either one fails, post the output here, or the end of C:\NetXMS\log\netxmsd.log.