MannyTC Report post Posted 10/03/2005 05:17 PM We are using VG versin 5.2.3063. Our system hung on a vbscript on Friday and VG waited about 14 for the vbscript to complete and none of our other calls were completed. The system ended up doing a crash dump and reboot on Saturday morning. The system was functional for 4 months straight without a reboot which is a pretty good run. Anyways, after looking at things this morning to try and figure out what went wrong I noticed that there are well over 500 vbs files in the VG data folder that seem to be temporary copies of the vbscript that runs when an OnNotConnected event occurs. This is an example of one of the files: vbs_5_OnNotConnected_050923195920. Is this normal or am I running a version that has some extra debug code in it that is creating these and leaving them behind? Share this post Link to post
SupportTeam Report post Posted 10/03/2005 10:46 PM Our system hung on a vbscript What was the VBScript on which it hung? Do you know why the VBScript hung? VBScripts are basically programs in themselves - so as much care should be taken with writing them as you would with a program - if they are not coded right you will get bugs and problems with them... They run separate to VoiceGuide in their own individual script interpreter so in theory if one hangs or gives errors then others should still run. Maybe the problem was with a resource your scripts access - like a database for example? The system was functional for 4 months straight without a reboot which is a pretty good run. With Windows systems in general we'd probably recommend scheduling a reboot once a week - just in case... The OnNotConnected files should be cleaned out periodically - the latest v.5.2.5 does that - maybe that still was not done in v5.2.3063 Regardless of that, 500 files is a pretty small number and should not have caused anything. Share this post Link to post
MannyTC Report post Posted 10/03/2005 11:58 PM The vbscript was a simple SQL database update query to send the results of the call to a different system. This script has been functioning fine for over a year now. I noticed in the Windows Event log that there were a bunch of errors with the Srv service that started about 6 hours before this issue occured. The two errors that repeated over and over again were: The server was unable to allocate from the system nonpaged pool because the pool was empty. and The server was unable to allocate a work item 3 times in the last 60 seconds. After rebooting these errors went away. Could have just been a memory issue due to the fact the system was running for 4 months straight. The numbers in the outdialqueue were set to just use one line so that is why the rest of the calls probably got backed up. Will let you know if we have any more issues with this. Share this post Link to post
SupportTeam Report post Posted 10/04/2005 12:50 AM The error "The server was unable to allocate from the system nonpaged pool because the pool was empty" is pointing to a memory related problem. Hard to say what is causing it though... If it is a memory reated problem then rebooting the server on a regular basis should help to manage it. Share this post Link to post
