NetXMS Support Forum

I'm running NetXMS server on a Win2003Std box, and have the client on a SQL 2005 Cluster - also Win2003Std.
About every two weeks, the SQL server starts having problems - can no longer connect via RDP until after a reboot. The only thing I'm monitoring on that box is drive space on one drive at the moment.

Several other servers have the same NetXMS client installed, but don't show the same problem.
It just began happening on the SQL box after the NetXMS client install, though.
When logging in locally on the SQL cluster, it shows 'logging in using default profile, not enough resources' message at the time it's having the problem.
Disk space and memory were both fine at the time.

I have the NetXMS client disabled at the moment on that SQL cluster node.
Any suggestions on what to look at to see why it will no longer take the RDP connection after a couple weeks?

Greg

I have a new install with v1.0.11.
Console and NetXMS server are on a WinXP 32bit.
I have a 64bit SQL box with Win32 Enterprise, so I put the 32bit NetXMS agent on there.
I'm checking disk space using FileSystem.Free(S:)
Also tried Disk.Free(S:) -but no difference there.
I have it looking for anything less than threshold of 12000000000 (roughly 11gb).
The drive has a bit over 9gb available - and right-clicking on the node and displaying Last DCI Values shows a value of 9455075328 for that DCI.
But it never triggers the status change.
I'm doing this using the cluster alias, but have tried also on the active physical node, and no change there either.
The performance graph does show the space under the threshhold level.
All the polling frequency settings are set to default settings.