We are receiving the following errors when running the SNMP service.
TMSSnmpService faults with error posted to the application event log: Event ID 1000
Faulting application name: TMSSNMPService.exe, version: 220.127.116.11, time stamp: 0x50e4166c
Faulting module name: mscorlib.ni.dll, version: 4.0.30319.296, time stamp: 0x50483a22
Exception code: 0xc0000005
Fault offset: 0x00000000003c94ea
Faulting process id: 0xb00
Faulting application start time: 0x01ce237d35e764c8
Faulting application path: C:\Program Files (x86)\TANDBERG\TMS\Services\TMSSNMPService.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\4f52500ab48877b85e71430f4f46670f\mscorlib.ni.dll
Report Id: ae3693ad-8fab-11e2-9fbc-005056a90100
Java version 6 has been installed and tested on the server but same error occurs. Java version 7 was also intalled but same issue occured.
Any assistance would be greatly appreciated.
Solved! Go to Solution.
Can we use TMS 14.1.1 now without runned TMSSNMPService till 14.2 comes? What problems it may brings to us?
Or we should rollback to 13.6?
If you are not running any old classic systems (which operates with SNMP traps) I would not worry about it. SNMP is used mostly for faster system discovery in the newer version. Traps are sent over HTTP(S) now. It won't affect the other TMS functionalies.
In an effort to get folks looking at our new Cisco TMS Admin Guide, what the TMSSnmpService does (as well as the other the TMS services), see page 18 of the new Cisco TMS Admin Guide:
On behalf of hard working technical writers, I strongly encourage all to familiarize yourselves with our documentation. You may be surprised to what you find out
Hi Dale and Magnus,
I am not currently using Scan SNMP Capable Systems To Allow Quick Discovery of Inaccessibility: and have very less snmp only systems to manage.
Do you see any other impact of snmp service not running.
As discussed in my earlier post, reference the Cisco TMS Admin Guide on what the TMSSnmpService does and what you lose with having it disabled...which I would only recommend in the interim...meaning this issue is fixed in 14.2. Therefore, upgrade to 14.2 so has to resolve the issue, when it's released. And before you ask, TMS 14.2 should be out by the end of this month
I dont see the call status of the Endpoint to change, until i do a force refresh.
I see that TMS would scan the Managed devices only every 15 minuts - So, this is an impact for my TMS monitoring.
This scanner service checks the connection status, call status, and system configuration of existing
systems. It pauses for 15 minutes after a scan has finished
That's a separate bug in TMS 14.1.x you are describing - CSCue94672. It has been resolved in TMS 14.2, which was released earlier today.