NetXMS Support Forum

NETXMS CONSOLE CRASH DUMP
Mon May 07 14:06:52 2012

EXCEPTION: C0000005 (Access violation) at 004121D8

NetXMS Console Version: 1.2.0
OS Version: Windows NT 6.1 Build 7601 Service Pack 1
Processor architecture: AMD64 (Intel EM64T)

Call stack:
  [libnxclw:00000000004121D8]: NXCLoadAllAlarms
  [nxcon:0000000140014099]: (function-name not available)
  [kernel32:0000000076EA652D]: BaseThreadInitThunk
  [ntdll:000000007759C521]: RtlUserThreadStart


How can i fix this thing ?
I've noticed this after i updated from 1.1.10 to 1.2.0
But i think this proble was erlier.
Thanks

Hi!

Yes, it's problem in version 1.2.0. It is fixed in upcoming 1.2.1 release.

Btw, why you still using legacy console?

Best regards,
Victor

One reason to use the old Alarm Viewer is the fact that it can log in automatically. We use it to display the alarm status in displays around our office and the computer that runs the Alarm Viewer is set to automatically restart every morning and make an automatic login and because of that we never have to touch it.

And yes, we have the same crash-problem since the last upgrade.

Thanks for respond =)
I've totally reinstall server and agents already 

I am having the same problem and I still use the legacy console as it is a very useful utility.

Can Victor indicate when version 1.2.1 will be ready.

Thanks,

Gary Jameson

Is this solved? We still cant use our Alarm Browser. If it's solved and should work in 1.2.1 I'll have to investigate more on our side.

It should be resolved already in 1.2.1. I'll double check this.

Best regards,
Victor

I don't think this is solved. We're migrating to new hardware and I just installed both server, databas (empty) and client tools on a new server and the Alarm Browser crashed there too.

New clean install with 1.2.2 and the Alarm Viewer still crashes.

Hi!

Finally I've fixed that. Attached is patched 32 bit nxav.exe - replace existing with this one and it should work. If you need 64bit nxav.exe, let me know.

Best regards,
Victor

Thank a lot! Works fine. No need for 64-bit for the moment.

Sorry to disturb once again but the update worked with 1.2.1, not the most recent version.

Binary was built for version 1.2.2, but it will work with earlier client library versions too.

Best regards,
Victor