NetXMS Support Forum

I have to start by saying that this has been an extremely frustrating and disappointing exercise.

The NetXMS website holds such promise but faced with the reality of being unable to get a system installed and started leaves one to wonder if anyone is actually using it.

This product appealed because it purports to support MSSQL and we are SEQUEL programmers with nearly 20 years experience.  We have attempted to install on MS Server versions 2003 and 2008R2 using MSSQL Enterprise 2000, SQLEXPRESS 2005 and 2008.  The results have been fairly consistant!  The installation locks the system and only the power button will cure it.

The fundamental problem with this program would appear to be a distinct lack of meaningful error messages.  Generally one is left with nothing or a very obstruse error message.

I have, naturally, scanned the forums for solutions but none of those found have assisted me greatly in achieving anything meaningful.

Being MSSQL aware, we have been able to resolve the various issues with the RDBMS in order to move forward but there are a number of frustrating points with this part of the procedure that would leave the inexperienced high and dry.

Points to note:-
   # We have never been able to connect to a database using the native driver - it is apparently a credentials problem but independent testing of the credentials   confirms that they are correct.  The only workable solution was achieved using ODBC with manual database and security creation.
   # There is an error on line 486 of the dbinit_mssql.sql initialization script file - a CREATE INDEX statement has an illegal WHERE condition appended to it.  This is very effective in bringing the database initialization to a halt with a meaningless error message.

Following various suggestions from the forum we have done the command line checks to confirm the efficacy of the database, but when we attempt to start the daemon with debugging, it just goes into the abyss without further comment.

At this point it is no longer possible to uninstall the program either.  At this point we resort to vmWare's wonderful 'Delete from Disk' command and start with a new VM. We're on to #6 now!

Are we the only people on the planet attempting this combination?  Is it worth wasting any more time on this?

Quote from: ReddeNet on November 21, 2015, 12:45:22 AM
Are we the only people on the planet attempting this combination?  Is it worth wasting any more time on this?

Hi,

I'm using NetXMS on Windows Box with MSSQL since 2008. During the past years I migrated various combination of MSSQL (from 2005 to 2012) and Windows Server (from 2003 to 2012 R2) both on real servers and on virtual machines. The current install runs on a VM with Windows 2012 R2 Standard edition with MSSQL 2012 Standard edition hosted on a Proxmox virtual environment; I use it to monitor about 220 nodes with more than 5000 DCI.

I'm sure that I had some problem in the past (but nothing unsolvable), the real problem is that I really don't remember precisely what's gone wrong because it's a long time since a fresh install...

Best regards,
Marco

Quote from: ReddeNet on November 21, 2015, 12:45:22 AM
Are we the only people on the planet attempting this combination?  Is it worth wasting any more time on this?

Don't know if it's "worth" wasting time, but we're using a W2008R2 for the NetXMS server and a MSSQL2008R2 with ~440 nodes and ~ 3550 DCIs.

So, as Marco Incalcaterra already posted, it's possible to run the product purly on Windows.

Hi,

sounds quite strange to me - as already mentioned there are perfectly working installations on MS SQL. CREATE INDEX with WHERE clause (which will create filtered index) supported from SQL Server 2008 onwards, so yes, that can cause problems on very old SQL Server versions (but SQL Server 2005 will go out of support next year anyway).

Are you using full or minimal installer? Full installer will bring SQL Server Native client (if checked during installation). If you have installed SQL Server native client yourself - what version?

Try to run server in console with maximum debug (ensure that you have logging set to file in netxmsd.conf):

netxmsd -D9

and post output here.

Best regards,
Victor