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?
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?