Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - DH

#1
Thanks for the reply, I had seen your post and tried that but it did not work in this instance. I've checked the permissions on the NextXMS folder structure and the account running the service should have access so I don't think the file it can't find is in there. I've re-installed the WebUI a couple of times now, still no joy, the server appears to be running OK, using the java console appears to work and no info is missing, currently at a loss as to what the problem is.

DH
#2
Further info:
Windows event ID: 7024
Description:
  The NetXMS WebUI service terminated with service-specific error The system cannot open the file..

Unfortunately it doesn't tell me which file :-(
#3
Running on Windows server 2008 R2 here and after upgrade to 3.8.226 (from 3.7.95) the WebUI will not start, which is our only method of access.
#4
General Support / Re: Unknown error
December 24, 2020, 12:41:37 PM
Thanks Alex,

It has been chugging along nicely for years and I'm sure there is more old stuff in there that I have long forgotten about.

Regards, David
#5
General Support / Unknown error
December 24, 2020, 11:53:12 AM
Hi all,

Since updating to 3.6.300 (Windows x64 server) we'vw been getting the following two errors repeatedly:

Script (EPP::3) execution error: Error 11 in line 3: Function not found
Script (EPP::5) execution error: Error 11 in line 3: Function not found

The event name is SYS_SCRIPT_ERROR.

Any ideas on where I start looking?

Regards, David
#6
General Support / Re: Unmanage setting cleared
November 29, 2018, 04:45:57 PM
Hi Victor,

The object ID remains the same.

Regards, DH
#7
General Support / Re: Unmanage setting cleared
November 14, 2018, 01:41:21 PM
How do I tell if they are being re-created?
#8
General Support / Unmanage setting cleared
November 12, 2018, 04:03:08 PM
Hi,

Unmanage settings on interfaces keeps being cleared by something and I have to set them again. It does not happen to all interfaces at the same time, however sooner or later they all seem to get cleared/set back to managed.
Has anyone seen this behaviour and do you know how to stop so that unmanaged interfaces stay unmanaged?

DH
#9
It would be nice to be able to right click on an alrm in the alarm browser and have the option of moving the focus to the object in the Object Browser tree. We have a lot of zoned objects behind NAT which can, and often do, have the same private IPv4 address and unless we name them all uniquely it is not immediately obvious which network and containe they are from.

Regards,
David
#10
Hi Alex,

Thanks, that seems to have worked.

Regards,
David
#11
Hi Alex,

Thanks for the very quick response but how do I use the code on that page, I'm using a Windows 2008 R2 host and I don't have the ability or the tools to recompile anything?

Regards,
David
#12
 After upgrading to M4 all my HTTP monitors are failing, has something changed and I need to alter my configuration?

Regards,
David
#13
General Support / Re: v1.2.17 Android Console problem
December 15, 2014, 11:32:13 AM
The console here frequently loses the connection and closes, it also has a habit of timing out when looking up historical data, it then loses the connection and closes. This only starting happening after upgrading to 1.2.17

Regards,
David
#14
General Support / Re: Errors since 1.2.17 upgrade
November 27, 2014, 03:10:55 PM
Anyone else experienced this?
#15
General Support / Errors since 1.2.17 upgrade
November 21, 2014, 01:21:31 PM
Hi,

I'm getting sporadic communication errors between the java console and server since upgrading to 1.2.17.

Platforms:

Console on Windows 7 (64bit) machine
Server on Windows 2008 R2 (64bit) machine
Both machines are on the same local network (100Mbps switched)

There are a few errors appearing in the event log on the server:

Event: 40
Source: NetXMSCore
Level: Warning
Description:
Client session closed due to communication error (An existing connection was forcibly closed by the remote host.)

Event: 39
Source: NetXMSCore
Level: Error
Description:
Thread "Syncer Thread" does not respond to watchdog thread

Regards,
David