Guest LuisS Report post Posted 09/10/2005 10:02 PM After working right for some days, suddenly we get a tapiwrap.ocx error from VG. We're using 4 port analog Dialogic boards and VG with a TSP driver for our PBX. we didn't make any change to our config, what could be the problem? Tipo de suceso: Error Origen del suceso: Application Error Categoría del suceso: Ninguno Id. suceso: 1000 Fecha: 08/09/2005 Hora: 11:00:56 a.m. Usuario: No disponible Equipo: IVR Descripción: Aplicación con errores: vgmulti.exe, versión: 5.2.0.4023, módulo con error: tapiwrap.ocx, versión 1.84.0.0, dirección de error 0x00009612. Para obtener más información, vea el Centro de ayuda y soporte técnico en http://go.microsoft.com/fwlink/events.asp. Datos: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 76 67 6d ure vgm 0018: 75 6c 74 69 2e 65 78 65 ulti.exe 0020: 20 35 2e 32 2e 30 2e 34 5.2.0.4 0028: 30 32 33 20 69 6e 20 74 023 in t 0030: 61 70 69 77 72 61 70 2e apiwrap. 0038: 6f 63 78 20 31 2e 38 34 ocx 1.84 0040: 2e 30 2e 30 20 61 74 20 .0.0 at 0048: 6f 66 66 73 65 74 20 30 offset 0 0050: 30 30 30 39 36 31 32 0d 0009612. 0058: 0a . 0908vgm2.zip Share this post Link to post
SupportTeam Report post Posted 09/12/2005 12:48 AM We are still looking into what is actually causing the error - it is reported as generated by TapiWrap.ocx - but the actual error looks like is within the TAPI drivers - and is reported as generated by TapiWrap.ocx as that's what using the TAPI drivers... Still looking whether this is happening within the Panasonic PBX TAPI drivers or within Dialogic TAPI drivers. If it is within Dialogic TAPI drivers then we'd need to move this system to using "VG for Dialogic". (For benefit of other readers of this thread: This is a 12 line system which uses the TAPI CTI link to Panasonic as well as controling the 12 Dialoigc lines via the Dialogic's TAPI interface. The error occurs when the system has been working at full capacity for a while). Share this post Link to post
Guest LuisS Report post Posted 09/14/2005 02:17 AM We have a 16 line system running under Windows XP and TSP integration to a Panasonic switch. Our PBX is under more heavy load compare to previous weeks, when everything seemed to be working right, we think this load is affecting our CTI link which somehow fails and brings down VG, although we have seen some errors (below). We then restart the system and manage to work for several hours until next peek hour. What could we do to determine the cause and fix this issue? Best, Luis After we restart we see this Type Mismatch errors... 100149.05 0 init temp dir exists [C:\Archivos de programa\VoiceGuide\temp\] 100149.05 0 init clear settings on 16 devices. 100149.05 6 Initialising... 100149.06 7 Initialising... 100149.06 8 Initialising... 100149.08 9 Initialising... 100149.08 10 Initialising... 100149.09 11 Initialising... 100149.09 12 Initialising... 100149.09 13 Initialising... 100149.11 14 Initialising... 100149.11 15 Initialising... 100149.13 16 Initialising... 100149.13 17 Initialising... 100149.14 18 Initialising... 100149.14 19 Initialising... 100149.14 20 Initialising... 100149.16 21 Initialising... 100149.16 0 init attach vgs on 16 devices. 100149.16 0 Script Load C:\scripts\IVR_v1.2.vgs 100149.17 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.17 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.19 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.19 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.20 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.20 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.20 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.22 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.22 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.22 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.23 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.23 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.25 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.25 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.25 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.27 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.27 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.28 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.28 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.28 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.30 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.30 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.30 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.31 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.31 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.31 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] 100149.33 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] We got this before Tapiwrap.ocx crash 095659.39 6 linedevstate 2048 0 0 095659.41 6 callstate OFFERING 137574 0 4 095659.41 6 cti copying CallerID info from associated CTI line 095659.42 6 rv lg add [DNIS]{4616} 095659.44 6 callinfo CALLEDID 095659.44 6 callinfo ORIGIN 095659.44 6 ring 0 095659.45 6 rv clear 095659.45 6 Answer the call at 12/09/2005 09:56:59 a.m. 095659.45 6 lineAnswer(137574) => 137557 095659.89 6 timer fired EV_TIMEOUT_REPLAYMSG 095659.89 6 ScriptEventCode 9005 iLineState=1101 095659.89 6 LsPlayMsgFinished EV_TIMEOUT_REPLAYMSG 095659.89 6 [Entrega ID] Playing (C:\audio\deacuerdo_sino.wav) 095659.91 6 play set playid=206593 095700.98 6 PlaySoundStart err=[0 play PlaySoundStart ResetWavOutAndContinuePlay=>3,play waveOutWrite failed after LoadCurrFileToPlay_IntoOneMainBuffer [MMSYSERR_NOTENABLED]] [C:\audio\deacuerdo_sino.wav] 095700.98 6 play set playid=206593 095701.11 6 timer clear 095701.13 14 timer fired EV_TIMEOUT_REPLAYMSG 095701.13 14 ScriptEventCode 9005 iLineState=1101 095701.13 14 LsPlayMsgFinished EV_TIMEOUT_REPLAYMSG 095701.13 14 [Entrega ID] Playing (C:\audio\deacuerdo_sino.wav) 095701.14 14 play set playid=207828 095701.20 14 PlaySoundStart ok [C:\audio\deacuerdo_sino.wav] Just before crash > 095701.20 14 timer clear 100146.31 0 ApiMode=[TAPI] 100146.38 0 Tapi device 154 is: EXT1132 100146.39 0 Tapi device 153 is: EXT1161 100146.41 0 Tapi device 152 is: EXT1178 100146.42 0 Tapi device 151 is: EXT1160 100146.44 0 Tapi device 150 is: EXT1168 100146.47 0 Tapi device 149 is: EXT1206 100146.48 0 Tapi device 148 is: EXT1167 100146.50 0 Tapi device 147 is: EXT1205 100146.52 0 Tapi device 146 is: EXT1165 100146.53 0 Tapi device 145 is: EXT1204 100146.55 0 Tapi device 144 is: EXT1164 100146.56 0 Tapi device 143 is: EXT1203 100146.58 0 Tapi device 142 is: EXT1163 100146.59 0 Tapi device 141 is: EXT1202 100146.61 0 Tapi device 140 is: EXT1162 100146.63 0 Tapi device 139 is: EXT1201 100146.64 0 Tapi device 138 is: EXT2016 100146.66 0 Tapi device 137 is: EXT2008 100146.67 0 Tapi device 136 is: EXT2015 100146.69 0 Tapi device 135 is: EXT2007 100146.70 0 Tapi device 134 is: EXT2014 100146.72 0 Tapi device 133 is: EXT2006 100146.73 0 Tapi device 132 is: EXT2013 100146.75 0 Tapi device 131 is: EXT2005 100146.77 0 Tapi device 130 is: EXT2012 100146.78 0 Tapi device 129 is: EXT2004 100146.80 0 Tapi device 128 is: EXT2011 100146.81 0 Tapi device 127 is: EXT2003 100146.83 0 Tapi device 126 is: EXT2010 100146.84 0 Tapi device 125 is: EXT2002 100146.88 0 Tapi device 124 is: EXT2009 100146.89 0 Tapi device 123 is: EXT2001 100146.91 0 Tapi device 122 is: EXT1116 100146.92 0 Tapi device 121 is: EXT1016 100146.94 0 Tapi device 120 is: EXT1150 100146.95 0 Tapi device 119 is: EXT1015 100146.97 0 Tapi device 118 is: EXT1180 100146.98 0 Tapi device 117 is: EXT1014 100147.00 0 Tapi device 116 is: EXT1170 100147.02 0 Tapi device 115 is: EXT1013 100147.03 0 Tapi device 114 is: EXT1171 100147.05 0 Tapi device 113 is: EXT1012 100147.06 0 Tapi device 112 is: EXT1172 100147.08 0 Tapi device 111 is: EXT1011 100147.09 0 Tapi device 110 is: EXT1169 100147.11 0 Tapi device 109 is: EXT1010 100147.13 0 Tapi device 108 is: EXT1179 100147.14 0 Tapi device 107 is: EXT1112 100147.16 0 Tapi device 106 is: EXT1108 100147.17 0 Tapi device 105 is: EXT1200 100147.19 0 Tapi device 104 is: EXT1107 100147.20 0 Tapi device 103 is: EXT1007 100147.22 0 Tapi device 102 is: EXT1106 100147.23 0 Tapi device 101 is: EXT1006 100147.25 0 Tapi device 100 is: EXT1105 100147.27 0 Tapi device 99 is: EXT1005 100147.28 0 Tapi device 98 is: EXT1104 100147.30 0 Tapi device 97 is: EXT1004 100147.31 0 Tapi device 96 is: EXT1103 100147.33 0 Tapi device 95 is: EXT1003 100147.34 0 Tapi device 94 is: EXT1102 100147.36 0 Tapi device 93 is: EXT1002 100147.38 0 Tapi device 92 is: EXT1101 100147.39 0 Tapi device 91 is: EXT1001 100147.41 0 Tapi device 90 is: CO0054 100147.42 0 Tapi device 89 is: CO0053 100147.44 0 Tapi device 88 is: CO0052 100147.45 0 Tapi device 87 is: CO0051 100147.47 0 Tapi device 86 is: CO0050 100147.50 0 Tapi device 85 is: CO0049 100147.52 0 Tapi device 84 is: CO0048 100147.53 0 Tapi device 83 is: CO0047 100147.55 0 Tapi device 82 is: CO0046 100147.56 0 Tapi device 81 is: CO0045 100147.56 0 Tapi device 80 is: CO0044 100147.58 0 Tapi device 79 is: CO0043 100147.59 0 Tapi device 78 is: CO0042 100147.61 0 Tapi device 77 is: CO0041 100147.63 0 Tapi device 76 is: CO0040 100147.66 0 Tapi device 75 is: CO0039 100147.66 0 Tapi device 74 is: CO0038 100147.69 0 Tapi device 73 is: CO0037 100147.70 0 Tapi device 72 is: CO0036 100147.72 0 Tapi device 71 is: CO0035 100147.73 0 Tapi device 70 is: CO0034 100147.75 0 Tapi device 69 is: CO0033 100147.77 0 Tapi device 68 is: CO0032 100147.78 0 Tapi device 67 is: CO0031 100147.80 0 Tapi device 66 is: CO0030 100147.81 0 Tapi device 65 is: CO0029 100147.83 0 Tapi device 64 is: CO0028 100147.84 0 Tapi device 63 is: CO0027 100147.86 0 Tapi device 62 is: CO0026 100147.88 0 Tapi device 61 is: CO0025 100147.89 0 Tapi device 60 is: CO0012 100147.91 0 Tapi device 59 is: CO0011 100147.92 0 Tapi device 58 is: CO0010 100147.94 0 Tapi device 57 is: CO0009 100147.95 0 Tapi device 56 is: CO0008 100147.97 0 Tapi device 55 is: CO0007 100147.98 0 Tapi device 54 is: CO0006 100148.00 0 Tapi device 53 is: CO0005 100148.02 0 Tapi device 52 is: CO0004 100148.03 0 Tapi device 51 is: CO0003 100148.05 0 Tapi device 50 is: CO0002 100148.06 0 Tapi device 49 is: CO0001 100148.08 0 Tapi device 48 is: OUTPAGE0004 100148.09 0 Tapi device 47 is: OUTPAGE0003 100148.11 0 Tapi device 46 is: OUTPAGE0002 100148.13 0 Tapi device 45 is: OUTPAGE0001 100148.14 0 Tapi device 44 is: INPAGE0008 100148.16 0 Tapi device 43 is: INPAGE0007 100148.19 0 Tapi device 42 is: INPAGE0006 100148.20 0 Tapi device 41 is: INPAGE0005 100148.22 0 Tapi device 40 is: INPAGE0004 100148.23 0 Tapi device 39 is: INPAGE0003 100148.25 0 Tapi device 38 is: INPAGE0002 100148.27 0 Tapi device 37 is: INPAGE0001 100148.28 0 Tapi device 36 is: DISA0002 100148.30 0 Tapi device 35 is: DISA0001 100148.31 0 Tapi device 34 is: DOOR0004 100148.33 0 Tapi device 33 is: DOOR0003 100148.39 0 Tapi device 32 is: DOOR0002 100148.41 0 Tapi device 31 is: DOOR0001 100148.42 0 Tapi device 30 is: BV0002 100148.44 0 Tapi device 29 is: BV0001 100148.45 0 Tapi device 28 is: RM0001 100148.47 0 Tapi device 27 is: TR0001 100148.48 0 Tapi device 26 is: QIH0001 100148.50 0 Tapi device 25 is: QIO0001 100148.52 0 Tapi device 24 is: QH0001 100148.53 0 Tapi device 23 is: QO0001 100148.55 0 Tapi device 22 is: SYSTEM 100148.56 0 Tapi device 21 is: Analog Line 16(dxxxB4C4) 100148.56 0 Tapi device 20 is: Analog Line 15(dxxxB4C3) 100148.58 0 Tapi device 19 is: Analog Line 14(dxxxB4C2) 100148.59 0 Tapi device 18 is: Analog Line 13(dxxxB4C1) 100148.61 0 Tapi device 17 is: Analog Line 12(dxxxB3C4) 100148.61 0 Tapi device 16 is: Analog Line 11(dxxxB3C3) 100148.63 0 Tapi device 15 is: Analog Line 10(dxxxB3C2) 100148.64 0 Tapi device 14 is: Analog Line 9(dxxxB3C1) 100148.66 0 Tapi device 13 is: Analog Line 8(dxxxB2C4) 100148.66 0 Tapi device 12 is: Analog Line 7(dxxxB2C3) 100148.67 0 Tapi device 11 is: Analog Line 6(dxxxB2C2) 100148.69 0 Tapi device 10 is: Analog Line 5(dxxxB2C1) 100148.70 0 Tapi device 9 is: Analog Line 4(dxxxB1C4) 100148.70 0 Tapi device 8 is: Analog Line 3(dxxxB1C3) 100148.72 0 Tapi device 7 is: Analog Line 2(dxxxB1C2) 100148.73 0 Tapi device 6 is: Analog Line 1(dxxxB1C1) 100148.75 0 Tapi device 5 is: Línea H323 100148.75 0 Tapi device 4 is: IPCONF LINE 100148.77 0 Tapi device 3 is: LPT1T 100148.78 0 Tapi device 2 is: Minipuerto WAN (L2TP) 100148.80 0 Tapi device 1 is: Linea VPN para RAS 0 100148.80 0 Tapi device 0 is: RAS PPPoE Line0000 100148.86 0 init vgmulti ver 5.2.4023 100148.88 0 Inband Signaling Config file not specified 100148.88 0 Loading VMB data begin 100148.89 0 Loading VMB data - about to delete old entries 100149.00 0 vm sort start on 8 entries. 100149.00 0 vm sort end. 100149.00 0 Loading VMB data end 100149.05 0 init temp dir exists [C:\Archivos de programa\VoiceGuide\temp\] 100149.05 0 init clear settings on 16 devices. 100149.05 6 Initialising... 100149.06 7 Initialising... 100149.06 8 Initialising... 100149.08 9 Initialising... 100149.08 10 Initialising... 100149.09 11 Initialising... 100149.09 12 Initialising... 100149.09 13 Initialising... 100149.11 14 Initialising... 100149.11 15 Initialising... 100149.13 16 Initialising... 100149.13 17 Initialising... 100149.14 18 Initialising... 100149.14 19 Initialising... 100149.14 20 Initialising... 100149.16 21 Initialising... 100149.16 0 init attach vgs on 16 devices. 100149.16 0 Script Load C:\scripts\IVR_v1.2.vgs 100149.17 0 ERROR 5.2.4023 MemStructVgm_ClearVgm err[Type mismatch] Share this post Link to post
SupportTeam Report post Posted 09/14/2005 11:29 AM I understand that you were supplied with a newer version of Vgmulti which has extra debugging in it to determine cause of the MemStructVgm_ClearVgm errors. Please post trace from that new version and we would then be able to see the errors. Looks like you will be supplied with a "VG for Dialogic" version of the software as well. Share this post Link to post
Guest LuisS Report post Posted 09/17/2005 09:35 PM We're still getting the same error, with tapiwrap.ocx every day at peek hour. We have vgmulti version 5.2.0.4023 running in our system. Which version is the one with extra debugging features and what part of the logs do you need us to send? We're really concern about this issue, what can we do from our part to help solve this? LS Share this post Link to post
SupportTeam Report post Posted 09/18/2005 02:58 AM Following on from our last email: We are still looking into what is actually causing the error - it is reported as generated by TapiWrap.ocx - but the actual error looks like is within the TAPI drivers - and it is reported as generated by TapiWrap.ocx as that's what is using the TAPI drivers... Still looking whether this is happening within the Panasonic TAPI drivers or within Dialogic TAPI drivers. If it is within Dialogic TAPI drivers then we'll need to shift to using "VG for Dialogic". It looks like you will be supplied with a version of software which does the CTI integration to Panasonic not using TAPIWRAP.OCX - so we will be able to better determine where the problem lies. You should receive it within a couple of days. Share this post Link to post
Guest LuisS Report post Posted 09/22/2005 12:54 AM Hello, do you have any updates? Share this post Link to post
