NetXMS Support Forum

Have an issue with configuring LDAP. I have downloaded the recent release 1.2.17 and unable to retrieve results from LDAP where we have more than 1000 objects in an OU.

Our environment runs on rhel 5.9 and interested in binding to Microsoft Active Directory. When I configure a test to bind to an OU with a small number of objects, I can successfully retrieve the objects and write them to the db.

[DEBUG] LDAPConnection::initLDAP(): Connecting to LDAP server
[DEBUG] LDAPConnection::syncUsers(): Found entry count: 48
[DEBUG] LDAPConnection::syncUsers(): Found dn: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[DEBUG] LDAPConnection::syncUsers(): Found dn: xxxxxxxxxxxxxxxxxxxx
[DEBUG] LDAPConnection::syncUsers(): User added: xxxxxxxxxxxxxxxxxxxxxxxxxxxx

However when I attempt to set the search scope to one of our larger OU and read in those objects, I receive an error Size Limit Exceed.
[DEBUG] LDAPConnection::syncUsers(): LDAP could not get search results. Error code: Size limit exceeded

Anyone have any suggestions or advice in reading and writing more than 1000 objects from an OU?
I have tried the below configuration along with many others with no luck.

(&(objectClass=*)(sizelimit=0)) or (&(objectClass=*)(sizelimit="none"))

Appreciate any input

I wanted to write a right-click object tool that we can use in the alarm browser. The idea is we would right-click the alarm and based on a script do the following:

-right-click alarm
-obtain alarmid and object name from row highlighted in alarm browser
-pass the 2 variables to a script
-execute call to api to get the alarm message, creationtime, etc
-take data retrieve from api and send email to recipient

FWIW... I searched some of the docs and have not been able to find any particular alarm variables. I use the %OBJECT_NAME%, %OBJECT_ID% and %OBJECT_IP_ADDRESS% wiht other tools with no problems.

Is there a list of variables available from the alarm browser... like %ALARM_ID%? or is there a better option to do what I am interested in doing?

Appreciate any advice

For testing the product I built and compiled the initial binaries using mysql. All works great and extremely happy with the  product and capabilities after demoing for one of our teams. To review and further prove out the product, we are interested in building the libraries to work with MS SQL server and hoping for some advice.

In the installation doc, ODBC is supported but read the unixODBC package is needed. One question I asked is... must I compile the source with unixodbc to work with MS SQL server backend?  Or will the product only work with Windows and ms sql server?

Additionally, I figured I would attempt to build the files using our DataDirect drivers as these are our firm standard. During the build I receive the following error, see below. 

make[5]: Entering directory `/logs/tmp/netxms/netxms-1.2.9/src/db/dbdrv/odbc'
  CXX    odbc_la-odbc.lo
odbc.cpp: In function 'void* DrvPrepare(ODBCDRV_CONN*, wchar_t*, DWORD*, wchar_t*)':
odbc.cpp:303: error: cannot convert 'short unsigned int*' to 'char*' in initialization
odbc.cpp: In function 'DWORD DrvQuery(ODBCDRV_CONN*, wchar_t*, wchar_t*)':
odbc.cpp:511: error: cannot convert 'short unsigned int*' to 'char*' in initialization
odbc.cpp: In function 'void* DrvSelect(ODBCDRV_CONN*, wchar_t*, DWORD*, wchar_t*)':
odbc.cpp:639: error: cannot convert 'short unsigned int*' to 'char*' in initialization
odbc.cpp: In function 'void* DrvAsyncSelect(ODBCDRV_CONN*, wchar_t*, DWORD*, wchar_t*)':
odbc.cpp:804: error: cannot convert 'short unsigned int*' to 'char*' in initialization
odbc.cpp: In function 'wchar_t* DrvGetFieldAsync(ODBCDRV_ASYNC_QUERY_RESULT*, int, wchar_t*, int)':
odbc.cpp:935: error: cannot convert 'char*' to 'const short unsigned int*' for argument '1' to 'size_t ucs2_to_ucs4(const short unsigned int*, int, wchar_t*, int)'
make[5]: *** [odbc_la-odbc.lo] Error 1


Here is my configure command line argument...
./configure --with-server --with-agent --with-odbc=/tp64/db/DD/7.0.1 --prefix=/opt/netxms-prod CPPFLAGS="-DODBC64 -I/tp64/db/DD/7.0.1/include" LDFLAGS="-L/tp64/db/DD/7.0.1/lib"


Any suggestions or possible options to try to get the files built with this driver? Or do I need to use unixodbc?

Appreciate your help in advance.

As in previous posts I am still learning the product but have stumbled on an issue and trying to understand the root cause of the error.

My installation is on Centos 5.8, NetXMS 1.2.9 compiled from source and running a jetty 7.6.9 instance from a compiled rpm.

Using the web console and connecting through chrome; logging in, actioning alarms and various other activities are fine. But when I attempt to create a new object tool or edit a tool, a window is presented to "run in background". Clicking run in background sits for some time and will eventually timeout.

Reviewing the jetty logs I see the following

2013-11-06 12:33:20.514:INFO:oejs.AbstractConnector:Started [email protected]:9090
Exception in thread "Thread-53" java.lang.IllegalStateException: No context available outside of the request processing.
        at org.eclipse.rap.rwt.internal.service.ContextProvider.getContext(ContextProvider.java:95)
        at org.eclipse.rap.rwt.internal.service.ContextProvider.getUISession(ContextProvider.java:183)
        at org.eclipse.rap.rwt.SingletonUtil.getSessionInstance(SingletonUtil.java:54)
        at org.eclipse.ui.internal.Workbench.getInstance(Workbench.java:652)
        at org.eclipse.ui.PlatformUI.getWorkbench(PlatformUI.java:94)
        at org.netxms.ui.eclipse.jobs.ConsoleJob.<init>(ConsoleJob.java:65)
        at org.netxms.ui.eclipse.objecttools.views.ObjectToolsEditor$9.<init>(ObjectToolsEditor.java:300)
        at org.netxms.ui.eclipse.objecttools.views.ObjectToolsEditor.refreshToolList(ObjectToolsEditor.java:300)
        at org.netxms.ui.eclipse.objecttools.views.ObjectToolsEditor.notificationHandler(ObjectToolsEditor.java:446)
        at org.netxms.client.NXCSession.sendNotification(NXCSession.java:1125)
        at org.netxms.client.NXCSession$ReceiverThread.processNotificationMessage(NXCSession.java:697)
        at org.netxms.client.NXCSession$ReceiverThread.run(NXCSession.java:564)


Any thoughts or suggestions on what I should look at and review to help resolve the issue. Plus once this event occurs, I lose connectivity to the server and need to restart my web session.

Lastly, is there a good reference to configure a tool (object tool) which can be called from a pop-up menu in the alarm browser?

First off I am a newbie to this product and still learning the ins and outs of what this tool can do. I recently downloaded and compiled v1.2.8 for CentOS 5.7/RHEL 5.7 and running the web ui in a jetty instance on the same host.

I am finding that when the web console is idle for more than a minute, the session will timeout and the web console will throw an error stating to restart. 

Having searched the forums for answers and or advice, I have not found anything related to this configuration.

anyone cna provide some advice or point me in the direction to find these options?

Appreciate your help