.net Runtime 2.0 Error

[mediasol]

Hi I'm getting a error when we are doing outbound calling.

Voice guide runs for about 25 mins and stops with the error message appearing in the event log

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 29/09/2009
Time: 1:33:07 PM
User: N/A
Computer: DIALER
Description:
Faulting application vgivrservice.exe, version 7.0.9.0, stamp 4ab2601d, faulting module msvcr90.dll, version 9.0.21022.8, stamp 47313dce, debug? 0, fault address 0x000538cc.

Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 76 00 67 00 69 00 .v.g.i.
0030: 76 00 72 00 73 00 65 00 v.r.s.e.
0038: 72 00 76 00 69 00 63 00 r.v.i.c.
0040: 65 00 2e 00 65 00 78 00 e...e.x.
0048: 65 00 20 00 37 00 2e 00 e. .7...
0050: 30 00 2e 00 39 00 2e 00 0...9...
0058: 30 00 20 00 34 00 61 00 0. .4.a.
0060: 62 00 32 00 36 00 30 00 b.2.6.0.
0068: 31 00 64 00 20 00 69 00 1.d. .i.
0070: 6e 00 20 00 6d 00 73 00 n. .m.s.
0078: 76 00 63 00 72 00 39 00 v.c.r.9.
0080: 30 00 2e 00 64 00 6c 00 0...d.l.
0088: 6c 00 20 00 39 00 2e 00 l. .9...
0090: 30 00 2e 00 32 00 31 00 0...2.1.
0098: 30 00 32 00 32 00 2e 00 0.2.2...
00a0: 38 00 20 00 34 00 37 00 8. .4.7.
00a8: 33 00 31 00 33 00 64 00 3.1.3.d.
00b0: 63 00 65 00 20 00 66 00 c.e. .f.
00b8: 44 00 65 00 62 00 75 00 D.e.b.u.
00c0: 67 00 20 00 30 00 20 00 g. .0. .
00c8: 61 00 74 00 20 00 6f 00 a.t. .o.
00d0: 66 00 66 00 73 00 65 00 f.f.s.e.
00d8: 74 00 20 00 30 00 30 00 t. .0.0.
00e0: 30 00 35 00 33 00 38 00 0.5.3.8.
00e8: 63 00 63 00 0d 00 0a 00 c.c.....

I have attached the log ... please help.

0929_1317_vgEngine.zip

0929_ktTts.zip

[SupportTeam]

The event log entry does not really give much details, but shows error is in msvcr90.dll - which is a Microsoft DLL, not a VoiceGuide DLL.

 

Last line in log shows:

 

133424.279 15 9 5 db oledb connection open call [Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\mediasol\Data\MBS-Data-VG.mdb]

 

so perhaps this is related to MSAccess database usage(?).

 

I understand that you have been using this system for a while to perform outbound dialing and fax broadcasts etc.

 

When did this problem begin? How many times have you seen this error?

Please .ZIP up and upload traces from the other times this error occurred.

 

Has anything changed on this system around that time or was the script used changed?

 

What other applications are running on this machine?

[mediasol]

The only change we have had in the last 24 hours is

 

We change from outbound faxing to outbound voice broadcasting.

 

I will arrange to do more testing on the faxing side on the next 24 hours and report back.

[mediasol]

OK we have any update. Outbound faxing is working fine.

I have been able to determine the error is when VG is recording the call on an outbound call.

Please note we are using VG version "VoiceGuide_7.1.0_090917.exe"

Please see the log and script (script password is dave1111).

The following step occured
- Vg dail the phone number correctly
- the script plays module intro-msg correclty
- VG accept phone button press 1
- VG correctly follows path 1 to module Body and plays message
- VG then follows on to module RecMsg this where the problem seems to start.

There is not beep and computer server hangs. I noticed a program running call dw20.exe for about 3 minus and VG stops and the event log show the follow errors.

Event View - Application Error

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 29/09/2009
Time: 9:20:15 PM
User: N/A
Computer: DIALER
Description:
Faulting application vgivrservice.exe, version 7.0.9.0, stamp 4ab2601d, faulting module msvcr90.dll, version 9.0.21022.8, stamp 47313dce, debug? 0, fault address 0x000538cc.

Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 76 00 67 00 69 00 .v.g.i.
0030: 76 00 72 00 73 00 65 00 v.r.s.e.
0038: 72 00 76 00 69 00 63 00 r.v.i.c.
0040: 65 00 2e 00 65 00 78 00 e...e.x.
0048: 65 00 20 00 37 00 2e 00 e. .7...
0050: 30 00 2e 00 39 00 2e 00 0...9...
0058: 30 00 20 00 34 00 61 00 0. .4.a.
0060: 62 00 32 00 36 00 30 00 b.2.6.0.
0068: 31 00 64 00 20 00 69 00 1.d. .i.
0070: 6e 00 20 00 6d 00 73 00 n. .m.s.
0078: 76 00 63 00 72 00 39 00 v.c.r.9.
0080: 30 00 2e 00 64 00 6c 00 0...d.l.
0088: 6c 00 20 00 39 00 2e 00 l. .9...
0090: 30 00 2e 00 32 00 31 00 0...2.1.
0098: 30 00 32 00 32 00 2e 00 0.2.2...
00a0: 38 00 20 00 34 00 37 00 8. .4.7.
00a8: 33 00 31 00 33 00 64 00 3.1.3.d.
00b0: 63 00 65 00 20 00 66 00 c.e. .f.
00b8: 44 00 65 00 62 00 75 00 D.e.b.u.
00c0: 67 00 20 00 30 00 20 00 g. .0. .
00c8: 61 00 74 00 20 00 6f 00 a.t. .o.
00d0: 66 00 66 00 73 00 65 00 f.f.s.e.
00d8: 74 00 20 00 30 00 30 00 t. .0.0.
00e0: 30 00 35 00 33 00 38 00 0.5.3.8.
00e8: 63 00 63 00 0d 00 0a 00 c.c.....

Event Viewer - System
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 29/09/2009
Time: 9:21:19 PM
User: N/A
Computer: DIALER
Description:
The VoiceGuide IVR service terminated unexpectedly. It has done this 1 time(s).

Any suggestions what to do next?

0929_2107_vgEngine.zip

[SupportTeam]

I noticed a program running call dw20.exe for about 3 minus and VG stops and the event log show the follow errors.

dw20.exe is a MS Office error gathering application.

If it is running before problems with VoiceGuide begins then this means that there is something else going wrong on this system already before VoiceGuide service encounters problems.

 

It sounds like you have suddenly started to experience this error on your system.

 

Were any changes made to the system just before this error started occurring?

 

What else is installed on this system apart from Windows+Dialogic+VoiceGuide ?

[mediasol]

Hi the server has the following software loaded since we did our last success voice broadcast.

 

- New install version of VG 7.1

- MYOB 18 (testing software)

- ACT 2009 (that installs MS Sql)

 

I have started to unstalled this software MYOB and ACT 2009

 

Any suggestion what to now???

[mediasol]

Ok new update.

 

I have unstalled MYOB, ACT 2009 and remove all software of MS Sql.

 

Uninstalled VG, deleted the database.

 

Re-installed VG using the VoiceGuide_7.1.0_090917.exe

 

And the problem continues. Please note the VG guide in not running script to record (script module RECMSG) and is NOT running any MS office function before VG hangs. So I not see now how this could be a MS Office error.

 

Could you please suggest what we should do next?

[SupportTeam]

Looks like something is broken on this system.

 

Maybe one of the other applications installed an older or incompatible version of the msvcr90.dll file that is now causing problems.

 

At this stage its probably best to first get back to a working system by reformatting the HD and then reinstalling Windows and then just installing the Dialogic drivers and VoiceGuide (and MySQL if you are using it from local system).

[jewillis]

I just posted similar issues with VG after installing VoiceGuide_7.1.0_090925.exe. Continual NET 2 run time errors

 

Reinstalling windows and all of VG is not a good solution, not an answer. I doubt is is a windows problem. I get the same issue on two separate servers, at two separate locations and the problem is experienced by others. It would be kinda of stramge that I and others have the same incompatible version of the msvcr90.dll all after upgrading

 

Jeff

[SupportTeam]

mediasol: Before installing the _090917 update, when was the last time you downloaded and installed VoiceGuide? ie. Approximatley how old was the version that you had running previously and that was working for you? We will take a close look at the changes made since that time to find a possible cause.

[SupportTeam]

We have now fixed an issue with the Record module.

From looking through the ktTel traces supplied it looks like this is the issue that was occurring on your system.

The version with this fix is available for download here: [old link removed]

Please update to this version and advise if this fixes the problem occurring on your system.