Vg Crashing With Windows 7

[invoso.com]

WINDOWS show:

 

Nazwa aplikacji powodującej błąd: vgIvrService.exe, wersja: 7.4.2.0, sygnatura czasowa: 0x52fcfd01
Nazwa modułu powodującego błąd: unknown, wersja: 0.0.0.0, sygnatura czasowa: 0x00000000
Kod wyjątku: 0xc0000005
Przesunięcie błędu: 0x007b3863
Identyfikator procesu powodującego błąd: 0x440
Godzina uruchomienia aplikacji powodującej błąd: 0x01cf3263c7c55a62
Ścieżka aplikacji powodującej błąd: C:\Program Files (x86)\VoiceGuide\vgIvrService.exe
Ścieżka modułu powodującego błąd: unknown
Identyfikator raportu: 864b6514-ba61-11e3-9f8f-24be051afaf3

 

 

VG crashed and Windows restart (announced).

 

0402_1458_vgEngine_01.zip

0402_ktTel.zip

[SupportTeam]

Was any more information saved by Windows Error Reporting?

 

You can use some 3rd party tool to retrieve WER information.

[invoso.com]

 

wer.txt

Edited 04/04/2014 08:58 PM by SupportTeam
posted WER text moved into attached file

[SupportTeam]

Looks like the wrong Dialogic drivers are installed on this system. Please install the Dialogic drivers that are available for Downlaod from our WWW Downloads page.

 

Also can you advise the exact time when the issue occurred? ktTel trace shows a number of restarts. Were some of those intentional? Can you please advise in more detail about the other service restarts that are showing in the ktTel trace.

 

Also it looks like this system is a 60 line system. Please note that for those size systems we recommend using a Server class OS (Windows 2008)

[SupportTeam]

To see what happened on the system we would need to see the FULL dump generated by Windows Error Reporting.

 

Please post the Full dump that would be created in the directory specified by the DumpFolder parameter.

[SupportTeam]

Also please .ZIP up and post the vgEngine trace preceeding the one posted.

 

The issue occurred at 1304091652 42384688 'ticks' ie: at 14:48:44.423

 

The vgEngine trace posted starts at 14:58:25

[SupportTeam]

Also please update VoiceGuide to the latest version as well. Latest version is available for Download from our WWW Downloads page.

 

The version installed on the system now is not the latest version.

[SupportTeam]

Looking through the 0402_1458_vgEngine trace (which is not the trace during which the error ocurred) we can see that the script used makes a number of calls to various Database Query type modules which are not set up to connect to a databse, or the connection specification is invalid.

 

We had a closer look at the error handling within VoiceGuide that would handle cases where the database connection specification is missing or invalid, and found there may have been situations encountered in those error handling routines which may lead to a System.NullReferenceException error that was encountered here.

 

Those error handling routines were updated and a new version of VoiceGuide that includs those changes can be downloaded here:

 

 

[removed]

 

If the right vgEngine trace is provided we should be able to confirm the likely cause of error that occurred at 14:48:44.423