Voiceguide 5.2.2 Is Crashing Under XP

[Guest tmm]

Hi team,

 

Few days ago, we put in production an IVR application based in VoiceGuide 5.2.2. Application works well, but we have a little "big" problem: between 24 and 48 hours, VoiceGuide executable is crashing. My system configuration is:

 

1.- Windows XP Professional (without service packs)

2.- Intel Dialogic System Release 5.1.1.

3.- D/160SC-LS (ISA) (only for 4 ports)

4.- VoiceGuide 5.2.2 application (150 modules aprox)

5.- Verbio TTS (compiled under SAPI 5)

6.- MS Access XP database (c:\...\netvru.mdb)

7.- SQL Server Database (vía ODBC drivers)

8.- PC Anywhere XP (waiting by modem)

 

Hardware platform is:

 

1.- Compaq DeskPro EP: Intel Pentium III, 500 Mhz, 8 Gb, 512 Mb

 

Please, could you help with this issue? Why VoiceGuide executable is crashing between 24 hours and 48 hours?

 

Thanks in advance,

Toni.

[SupportTeam]

What is actually crashing? Are you seeing any errors displayed on the screen?

Could you please .ZIP up and post copy of VoiceGuide's Trace Logs (from VG's \log\ subdirectory) which capture what was happening on the system up to the point of the crash. This will allow us to see what is going wrong.

[Guest tmm7405]

Good morning,

 

Attached you can find log files requested. This time, we had a physical problem with the adaptor of Dialogic, however is usual find a Windows XP error and VGMulti.exe (common Windows XP error window... send report to Microsoft...).

 

Thanks in advance for your support,

Toni.

Logs.zip

[SupportTeam]

We had a look through the traces.

 

Trace from 16th July looks all OK.

 

Trace from 17th July looks OK and then no more calls were received after 12:15am - although VoiceGuide itself kept on working - you can see it's 'housekeeping cleanup' messages in the log every 30 minutes.

 

Trace from 18th July shows that no calls were received during all day - although VoiceGuide itself kept on working - you can see it's 'housekeeping cleanup' messages in the log every 30 minutes.

 

Trace from 17th July looks OK with cleanup messages logged every 30 minutes and the a call arriving at about 10am, followed by more calls afterwards.

 

So overall traces show that VG did not stop working, did not crash and was not even restarted between 17th and 19th of July.

 

This makes us curious as to what is the actual problem here... could you please post a screenshots of any errors that you are seeing and please advise what actions were taken to recover from the error state.