Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Error Message from VM TMS 13.0

Dear all,

 

We have receive some error message from the VM TMS 13.0, that is installed a month ago.

 

<ErrorCode 1000>

Message="Faulting application name: TMSSNMPService.exe, version: 1.0.4008.29206, time stamp: 0x4d12159c Faulting module name: mscorlib.ni.dll, version: 4.0.30319.18444, time stamp: 0x52717d7e Exception code: 0xc0000005 Fault offset: 0x0000000000cd5bf7 Faulting process id: 0x116c Faulting application start time: 0x01cf68076319516f Faulting application path: C:\\Program Files (x86)\\TANDBERG\\TMS\\Services\\TMSSNMPService.exeFaulting module path: C:\\Windows\\assembly\\NativeImages_v4.0.30319_64\\mscorlib\\abf62e6545d2802fc60286678a67e6bf\\mscorlib.ni.dll Report Id: 371654ff-d3fb-11e3-98ea-005056b1027a"

 <ErrorCode 1026>

Message="Application: TMSSNMPService.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException Stack: at System.Runtime.InteropServices.Marshal.ReadInt64(IntPtr, Int32) at Tandberg.CommLib.SnmpLib.TrapHandling.SnmpTrapHandler.VbToObject(Tandberg.CommLib.SnmpLib.WinSnmp.SMIVALUE ByRef) at Tandberg.CommLib.SnmpLib.TrapHandling.SnmpTrapHandler.VblToHashtable(IntPtr) at Tandberg.CommLib.SnmpLib.TrapHandling.SnmpTrapHandler.OnSnmpMessage(IntPtr, IntPtr, Int32, UInt32, UInt32, IntPtr)"

 <ErrorCode 7031>

Message="The TMSSnmpService service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds:

Any comments on the above error?

 

Best Regards,

Ben Lai

 

Everyone's tags (1)
2 ACCEPTED SOLUTIONS

Accepted Solutions
VIP Green

Hi Ben,Is there any reason

Hi Ben,

Is there any reason why you're running such an old version of TMS on your "new" installation?

TMS 13.0 doesn't support many of the newer versions of software on other components nor the newer devices - if they're present in your environment, TMS could be having issues with those and hence why it is having unhandled exceptions.

Is it possible for you to upgrade to a more recent version of TMS (ie 13.2 if you have to stay in the TMS 13 release train, or to one of the more recent 14.x versions - the latest being TMS 14.4)?

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
Cisco Employee

Hi,You are seeing defect

Hi,

You are seeing defect CSCue00028, which was resolved in 14.2. Apart from upgrading TMS, a possible workaround could be to move your TMS 13.0 to a 32 bit operating system, as the error is specific to 64 bit installations.

Regards,
Kjetil

6 REPLIES
VIP Green

Hi Ben,Is there any reason

Hi Ben,

Is there any reason why you're running such an old version of TMS on your "new" installation?

TMS 13.0 doesn't support many of the newer versions of software on other components nor the newer devices - if they're present in your environment, TMS could be having issues with those and hence why it is having unhandled exceptions.

Is it possible for you to upgrade to a more recent version of TMS (ie 13.2 if you have to stay in the TMS 13 release train, or to one of the more recent 14.x versions - the latest being TMS 14.4)?

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
New Member

Dear Wayne, TMS 13.0 is

Dear Wayne,

 

TMS 13.0 is installed on the VM with Window Server 2008 R2 SP1, and .net framework 4.

 

We have checked the TMS 13.0 administrator guide, and confirmed it is compatible with above VM specification. It is shocked receive the error message from TMS. By the way, how the error message affect the TMS performance?

Is there any solution except upgrading the TMS version?

Best Regards,

Ben

 

VIP Green

The above errors will stop

The above errors will stop the TMS SNMP Service - all the rest should still run OK.  I've seen this happen a few times on older versions of TMS.  You can just keep an eye on it and manually restart the service each time it stops - but it'd be so much easier to upgrade TMS from the old (January 2011) software to something more recent.

If you read the Release Notes for your other components (VCS, etc) you may notice that the minimum TMS software version required for those may be higher than what you are currently running.  This may also be the cause of the exceptions.

What other hardware and software versions are you using with your TMS (VCS, Endpoints, Content Servers, Consuctors, MCUs, etc)?

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
New Member

Dear Wayne,Thank for your

Dear Wayne,

Thank for your comment.

The client focus on management and phonebook function of the TMS, so there is MXP , C-series endpoints. 

I have suggested the client to upgrade the TMS to 14.

Anyway, Thank for your support.

 

Best Regards,

Benjamin

Cisco Employee

Hi,You are seeing defect

Hi,

You are seeing defect CSCue00028, which was resolved in 14.2. Apart from upgrading TMS, a possible workaround could be to move your TMS 13.0 to a 32 bit operating system, as the error is specific to 64 bit installations.

Regards,
Kjetil

This seems to be happening on

This seems to be happening on 14.2.2 as well.

 

 Component: Application Error
  Severity: Warning
  Event class: /App/Failed
  Device class: /Server/Windows/WMI/TMS
  Systems: None
  Summary: Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794
Faulting module name: ole32.dll, version: 6.1.7600.16624, time stamp: 0x4c2984e3
Exception code: 0xc0000005
Fault offset: 0x00000000000393a9
Faulting process id: 
  Message:
  Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794
Faulting module name: ole32.dll, version: 6.1.7600.16624, time stamp: 0x4c2984e3
Exception code: 0xc0000005
Fault offset: 0x00000000000393a9
Faulting process id: 0x39c4
Faulting application start time: 0x01d04d36eb9b6c36
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\ole32.dll
Report Id: e334bd6f-b990-11e4-aa1d-842b2b6be310

 

 

http://tools.cisco.com/security/center/viewAlert.x?alertId=29142

 

194
Views
15
Helpful
6
Replies