" /> -----FAULT------Exception:5 (0xc0000005) ACCESS_VIOLATION - Genesys CTI User Forum

Poll

Question:When a phone with ANI='000' ,then meet this error.

ANI=000
0 (0%)
Tserver Restart
0 (0%)

Total Members Voted: 0

« previous next »
Pages: [1]   Go Down

Author Topic: -----FAULT------Exception:5 (0xc0000005) ACCESS_VIOLATION  (Read 5715 times)

Offline letmedo

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
-----FAULT------Exception:5 (0xc0000005) ACCESS_VIOLATION
« on: April 02, 2009, 03:25:40 AM »
Advertisement
Genesys Tserver 6.6.001.42
PBX:Nortel Meridian

Question:When a phone with ANI='000' ,then meet this error.

04/01/09 17:12:55.656   Standard   cti1   T-Server_Symposium   GCTI-00-02024   OS signal 0xC0000005 received
@17:12:55.6560 [2024] Signal 0xC0000005 received
...exception in block [main]

----FAULT----04/01/09@17:12:55.6560----
Exception: 5 (0xc0000005) ACCESS_VIOLATION
AddrPC:    0041bd7e
AddrFrame: 00d62e0c
AddrStack: 00d62df4

0041bd7e symposium_server:?mlink_msg_add_call_info@@YAXPAUmessage@@PAUcall_info@@@Z+278(1aa3ff0,55f61c,21,d62e40..)
0041bcf6 symposium_server:?mlink_msg_add_call_info@@YAXPAUmessage@@PAUcall_info@@@Z+142(1aa3ff0,1aeaf50,737300,d62e44..)
00428e78 symposium_server:?msg_add_call_info@@YAXPAUmessage@@PAUcall_info@@@Z+352(1aa3ff0,1aeaf50,1,1..)
0041db0c symposium_server:?call_release_party_ex@@YAHPAUcall_info@@PAUparty_info@@PAUrequest_info@@H@Z+564(1aeaf50,1aee0b0,0,0..)
0041d8d3 symposium_server:?call_release_party@@YAHPAUcall_info@@PAUparty_info@@PAUrequest_info@@@Z+22(1aeaf50,1aee0b0,0,0..)
00402461 symposium_server:?ml_dta_retain_one@@YAXPAUdtaddress@@K@Z+86(1aa2840,1e8b,49d33017,4..)
004091b0 symposium_server:?process_decoded_message@@YAXPAEH@Z+26363(80f,d636f4,414ea9,1aa04b1..)
00402cba symposium_server:?process_decoded_message@@YAXPAEH@Z+517(1aa04b1,3c,77e6e592,80f..)
00414ea9 symposium_server:?process_device_message@FSM@@QAEXPAEH@Z+1320(1aa04b1,3c,0,924210..)
00414913 symposium_server:?input_handler@FSM@@QAEXHPAEH@Z+940(0,1aa0480,8a,924210..)
00414559 symposium_server:?device_input_handler@@YAXHHPAEH@Z+51(1,0,1aa0480,8a..)
0043a472 symposium_server:?tcp_start@@YAHPAUlink_info@@@Z+418(93cce0,2,490766,7b..)
00494d08 symposium_server:_conn_multi_scan+3316(3,1,0,0..)
004948ff symposium_server:_conn_multi_scan+2283(0,ffffffff,790,ffffffff..)
004951d7 symposium_server:_conn_main_loop+78(d6f900,136e54,b64a10,7..)
00430651 symposium_server:?real_main_thru_nco@@YAHHQAPAD0@Z+2564(b,b639a8,b62768,1c..)
0048bf41 symposium_server:?NCO_exec@@YAHPAUNCO_descriptor_@@ZZ+1041(d6f930,0,d6f9b8,d6fad4..)
0048bcd7 symposium_server:?NCO_exec@@YAHPAUNCO_descriptor_@@ZZ+423(d6fad4,b,b639a8,b62768..)
0048ad85 symposium_server:?NCO_main@@YAHHQAPAD0P6AHH00@Z@Z+741(b,b639a8,b62768,42fc95..)
0042fc90 symposium_server:?real_main_thru_nco@@YAHHQAPAD0@Z+67(b,b639a8,b62768,d6ff80..)
004314fa symposium_server:?g_run_app@@YAHHQAPADPAU_TGStartupInfo@@@Z+38(b,b639a8,d6fb60,b64a10..)
0046c219 symposium_server:?main_thread@@YAXPAX@Z+600(0,1c,0,b64a10..)
.. file gntservice.cpp, line 872 (disp=26)
0051c948 symposium_server:__beginthread+206(b64a10,1c,0,b64a10..)
77e6438b KERNEL32:RegisterWowExec+2042(51c8f1,b64a10,0,c8..)
-----------END-OF-FAULT-INFO-----------
(conn_cleanup) clearing connections...
0) fd=392 Sync: remote=134.100.194.125:2020, socket=2075, RX=368902 TX=1242 qi-x--
1) fd=436 SERVER: port=3000 "TLib:6.5.201.02" q-nx-r
2) fd=444 SERVER: port=5555 "MngmLib:6.5.200.01" q-nx-r
3) fd=452 Async: remote=134.100.193.137:3000, socket=2078, RX=3191193 TX=474389 q--xcr
4) fd=464 Async: remote=134.100.194.125:4999, socket=2079, RX=36 TX=300 qi-xc-
5) fd=476 Async: socket=3000, remote=134.100.194.125:2084, RX=22736 TX=23969912 q--x-r
6) fd=484 Async: socket=3000, remote=134.100.194.125:2085, RX=22735 TX=23969912 q--x-r
7) fd=1804 Async: socket=3000, remote=134.100.194.121:3517, RX=181329 TX=966947 q--x-r
8) fd=500 Async: socket=3000, remote=134.100.194.125:2086, RX=2576715 TX=11929554 q--x-r
9) fd=1384 Async: socket=3000, remote=134.100.194.202:3367, RX=5561 TX=57527 q--x-r
10) fd=520 SERVER: port=4444 "TLib:6.5.201.02" q-nx-r
11) fd=596 Async: socket=3000, remote=134.100.194.196:1557, RX=18128 TX=204386 q--x-r
12) fd=532 Async: socket=3000, remote=134.100.193.18:1072, RX=18293 TX=3010833 q--x-r
13) fd=540 Async: socket=3000, remote=134.100.194.14:3770, RX=23518 TX=259628 q--x-r
14) fd=1720 Async: socket=3000, remote=134.100.194.32:1445, RX=8695 TX=92370 q--x-r
15) fd=556 Async: socket=3000, remote=134.100.193.19:1071, RX=46771 TX=2224202 q--x-r
16) fd=564 Async: socket=3000, remote=134.100.193.19:1070, RX=598 TX=1466 q--x-r
17) fd=676 Async: socket=3000, remote=134.100.194.13:1592, RX=9692 TX=107300 q--x-r
18) fd=584 Async: socket=3000, remote=134.100.194.113:4135, RX=2645 TX=26087 q--x-r
19) fd=984 Async: socket=3000, remote=134.100.194.43:3484, RX=12683 TX=143998 q--x-r
20) fd=608 Async: socket=3000, remote=134.100.194.199:4995, RX=4901 TX=56522 q--x-r
21) fd=844 Async: socket=3000, remote=134.100.194.108:2269, RX=1633 TX=15256 q--x-r
22) fd=1176 Async: socket=3000, remote=134.100.194.35:1821, RX=7690 TX=83038 q--x-r
23) fd=624 Async: socket=3000, remote=134.100.194.23:2642, RX=18273 TX=199934 q--x-r
24) fd=1792 Async: socket=3000, remote=134.100.194.206:4580, RX=2217 TX=21492 q--x-r
25) fd=640 Async: socket=3000, remote=134.100.194.114:3248, RX=18896 TX=208231 q--x-r
26) fd=616 Async: socket=3000, remote=134.100.194.201:3281, RX=2213 TX=22488 q--x-r
27) fd=1172 Async: socket=3000, remote=134.100.194.34:4696, RX=2220 TX=22527 q--x-r
28) fd=1780 Async: socket=3000, remote=134.100.194.112:1598, RX=2619 TX=27349 q--x-r
29) fd=672 Async: socket=3000, remote=134.100.194.12:3574, RX=11856 TX=125457 q--x-r
30) fd=1776 Async: socket=3000, remote=134.100.194.198:2061, RX=2217 TX=22241 q--x-r
31) fd=1296 Async: socket=3000, remote=134.100.194.195:3879, RX=1825 TX=16864 q--x-r
33) fd=704 Async: socket=3000, remote=134.100.194.107:1588, RX=19448 TX=204276 q--x-r
35) fd=716 Async: socket=3000, remote=134.100.194.25:2980, RX=15626 TX=175902 q--x-r
36) fd=724 Async: socket=3000, remote=134.100.194.197:1617, RX=20211 TX=223809 q--x-r
41) fd=764 Async: socket=3000, remote=134.100.194.205:4971, RX=22534 TX=248052 q--x-r
42) fd=776 Async: socket=3000, remote=134.100.194.204:3808, RX=20780 TX=228444 q--x-r
45) fd=796 Async: socket=3000, remote=134.100.194.105:1832, RX=16898 TX=174641 q--x-r
55) fd=876 Async: socket=3000, remote=134.100.193.21:1581, RX=3479 TX=1978954 q--x-r
57) fd=892 Async: socket=3000, remote=134.100.193.27:4132, RX=1769 TX=1019337 q--x-r
65) fd=960 Async: socket=3000, remote=134.100.194.111:1142, RX=15386 TX=161143 q--x-r
69) fd=988 Async: socket=3000, remote=134.100.193.16:4453, RX=121268 TX=2976240 q--x-r obuf=1
72) fd=1016 Async: socket=3000, remote=134.100.194.21:4046, RX=24466 TX=270292 q--x-r
89) fd=1152 Async: socket=3000, remote=134.100.193.25:1314, RX=55891 TX=1363696 q--x-r
97) fd=1212 Async: socket=3000, remote=134.100.194.50:1138, RX=18890 TX=211417 q--x-r
99) fd=1232 Async: socket=3000, remote=134.100.194.55:4274, RX=18692 TX=209274 q--x-r
122) fd=1412 Async: socket=3000, remote=134.100.194.110:3745, RX=17664 TX=193237 q--x-r
(addp-dispose) fd=484
(conn_cleanup) clearing timers...
...6 timer(s) cleared
...0 background timer(s) cleared
@17:12:55.6870 [ISCC] Debug: Location object URS:00070004@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:000d0008@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:00150006@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:0026001e@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:002c0024@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object IVRCTILIB:004b0040@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:002d0025@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:0027001f@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:00200018@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:002f0027@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:00560043@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:00d00014@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:0024001c@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:00d50012@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:011f005b@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:0122005e@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:0045003c@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object IVRCTILIB:00db0054@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object StatusQuery:017300a6@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:01410075@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:01740070@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:0177009b@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:0178003f@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:01750019@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:017a0057@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:017c0011@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:017e00a5@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:017f000d@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:018100a4@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:01800010@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:018300a2@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:018200a3@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:0184002e@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object Michelle:01850066@/0/0/0 is removed
@17:12:55.6870 [ISCC] Debug: Location object ISCC:00010000@/0/1/0 is removed
Logged

Offline kowari

  • Jr. Member
  • **
  • Posts: 53
  • Karma: 0
Re: -----FAULT------Exception:5 (0xc0000005) ACCESS_VIOLATION
« Reply #1 on: April 03, 2009, 02:18:45 AM »
6.6 or 7.6?

If 7.6 I would be taking that to genesys tech support and asking "Please explain!"  That is a seg fault in the code.
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: -----FAULT------Exception:5 (0xc0000005) ACCESS_VIOLATION
« Reply #2 on: April 03, 2009, 02:34:10 AM »
Don't see in the logs that ANI...can you post complete trace and exact version? 6.X is so old it doesn't even has support.
Logged

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Re: -----FAULT------Exception:5 (0xc0000005) ACCESS_VIOLATION
« Reply #3 on: April 03, 2009, 04:31:00 AM »
I did not get a chance to test it on Symposium, but tested it on SIP T-Server and AES and could not reproduce this error. I have never seen T-Server 6.6 :) I assume it is 7.6 :)
Logged
Pages: [1]   Go Up
« previous next »