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

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

For an introduction to the new site, click here. And see here for current known issues.

New Member

Explanation of Windows Event log Messages from AvCiscoTsp

Does anyone know where to find a listing and explanation of the error messages that the TSP posts to the Windows Event and Application error logs?

The specific one that I am looking for is: (This is a cut and past from the NT Event Log)

Type Date Time Source Category Event User Computer

Warning 8/14/2002 5:17:56 PM AvCiscoTsp_MC None 111 N/A DPSUM01

New Member

Re: Explanation of Windows Event log Messages from AvCiscoTsp

Can you double-click on the event in the event log to get a more descriptive text and paste that in here? Then we'll tell you what it means....

(Depending on the version of the TSP, event # 111 might mean different things.)

Michael Kale,

New Member

Re: Explanation of Windows Event log Messages from AvCiscoTsp

you can press the little copy button below the up down arrows on the events properties to paste the event how it actually appears.

New Member

Re: Explanation of Windows Event log Messages from AvCiscoTsp

What version of Unity and TSP are you using? When are you getting this? Is this during startup? After unity comes all the way up, can you call in and leave and retrieve messages? Most versions of Unity (up to 3.1.3 I think, but I could be wrong) post TSP warnings as Unity is starting as part of the normal startup process. The TSP comes up, connects to Call Manager to make sure it's there, disconnects, and then when more Unity components come online, it reregisters and begins taking calls. Warning messages about the TSP ports disconnecting are sent up during that disconnect. So, in a nutshell, it's supposed to do that.

If you're not able to call into Unity after it starts up, or you're getting those errors while Unity has been running normally, then we should look into this.

Also a thing to note is that when Unity does that initial connection, if Call Manager isn't to be found (say Call Manager and Unity were rebooted at the same time and Unity came up faster), the TSP ports competely disable themselves and the whole box needs to be rebooted to get everything rolling again. This is a bug (CSCdy10803) that you should write your congressman and TAC engineer about.