Discussion:
Tapisrv crashes
(too old to reply)
Claire Grube
2013-12-06 00:37:51 UTC
Permalink
The following (well known ;-) configuration makes tapisrv crash about once a month:

TAPI Application
Microsoft Tapi (tapisrv running/crashing in cvshost)
TSP
I
somePBX

There is an NULL_POINTER_WRITE in the 'SPEventHandlerThread+95'.
I've peeked around but no one lets me have a look to the Microsoft TAPI sources of Win 2k8R2.
(and surely I gave up long ago waiting for Apache taking over MS ;-)

Probably one stumbled into a similar problem and has some hints for me where to go on searching...

Some thoughts and questions:
Everything is an event. But which kind of events are handled by SPEventHandlerThread?
- The LineEvents by Tsp? (SPEvent=ServiceProvider..?)
- The requests of the TapiApp?
- Or even the replies from MS TAPI layer?
How can an EventHandlerThread write to NULL? (As long as all lists/maps/collections are O.K.) Shouldn't it only receive and hand over/distribute events?
A reference to a deceased call?

Any hints appreciated!

Regards
C.
Claire Grube
2013-12-09 20:41:02 UTC
Permalink
Post by Claire Grube
Any hints appreciated!
Folks,
Is this topic too compex or too simple?
It's not easy to carry on with this matter. Unfortunately Microsoft seems to have eliminated the TAPI tracing mechanism, described by Andreas Marschall here:
http://www.i-b-a-m.de/Andreas_Marschall%27s_TAPI_and_TSPI_FAQ.htm#_Q:_Is_there_10
Or do we have to access it 'nowadays' (e.g. @ 2008R2) a different way?

There was a similar error in method DequeueSPEvent in SPEventHandlerThread some years ago where Andreas could crosscheck a callstack at Win source code!?

Have all the wizards already retired?

Regards

C.
Andreas Marschall [exMVP TAPI]
2014-02-05 08:24:09 UTC
Permalink
Claire,
as you may know, almost all TAPISRV crashes are caused by a TSP...
Post by Claire Grube
TAPI Application
Microsoft Tapi (tapisrv running/crashing in cvshost)
TSP
...so, what TSP are you using?
Post by Claire Grube
somePBX
...and what PBX are you using?
Post by Claire Grube
There is an NULL_POINTER_WRITE in the 'SPEventHandlerThread+95'.
I've peeked around but no one lets me have a look to the Microsoft TAPI sources of Win 2k8R2.
Do the issue still occur on current server OS ?
Post by Claire Grube
Probably one stumbled into a similar problem and has some hints for me where to go on searching...
Everything is an event. But which kind of events are handled by SPEventHandlerThread?
- The LineEvents by Tsp? (SPEvent=ServiceProvider..?)
Yes, AFAIK SPEventHandler within TAPISRV handles the events sent by TSP.
And again, most TAPISRV crashes are caused by a TSP...
Post by Claire Grube
How can an EventHandlerThread write to NULL? (As long as all lists/maps/collections are O.K.) Shouldn't it only receive and hand over/distribute events?
Maybe by writing to memory reference that had been allocated by TSP but has been released by TSP before TAPISRV has finished writing to it.
BTW did I already mention that most TAPISRV crashes are caused by a TSP...

Did you encounter the issue with different TSPs or just a specific one?
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK / Visual C++ 2003-2008
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My Toto® Tools (a collection of free, mostly TAPI related tools):
http://www.I-B-A-M.de/Andreas_Marschall's_Toto_Tools.htm
* Please post all messages and replies to the group / forum so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.
Loading...