Guest DiegoBellini Report post Posted 04/24/2008 05:33 AM I need urgent help with a problem of a client. For 4 days I am trying tests and not that happens. It is the VBS "SetupTransfer" that this in "TelecoopMain.vgs". I cannot change VG's version because it he belongs to my client, it is necessary to solve it without changing anything of configuration. Please help me, thanks Problems.zip Share this post Link to post
SupportTeam Report post Posted 04/24/2008 10:02 AM Have you tried just double clicking on the vbs_3_4.vbs file and seeing on what line the problem occurs? When ran directly like that the Windows scripting host will pop up a message box telling you on what line the problem with the VBScript is occurring. If the problem is with CreateObject("ADODB.Command") then you need to ensure that your system has the Microsoft's database components installed to let you create 'ADODB.Command' object. See: http://msdn2.microsoft.com/en-us/data/aa937729.aspx Microsoft Data Access Components (MDAC) 2.8 : http://www.microsoft.com/downloads/details...;displaylang=en Share this post Link to post
Guest DiegoBellini Report post Posted 04/24/2008 01:07 PM Have you tried just double clicking on the vbs_3_4.vbs file and seeing on what line the problem occurs? When ran directly like that the Windows scripting host will pop up a message box telling you on what line the problem with the VBScript is occurring. If the problem is with CreateObject("ADODB.Command") then you need to ensure that your system has the Microsoft's database components installed to let you create 'ADODB.Command' object. See: http://msdn2.microsoft.com/en-us/data/aa937729.aspx Microsoft Data Access Components (MDAC) 2.8 : http://www.microsoft.com/downloads/details...;displaylang=en When I do double clicking on the vbs_3_4.vbs file it works correctly without mistakes, the problem this one when I traverse it from VG. Share this post Link to post
SupportTeam Report post Posted 04/24/2008 07:59 PM To debug the VBScript while it is called from within VoiceGuide please place some calls to the Admin_TraceLogAdd COM function within the script. You will then be able to identify on which line the error occurs by looking at which calls are adding log entries to vgEngine log and which do not. Share this post Link to post