Jump to content


< Back to Forum


 

Not Closed Wscript.exe In


  • Please log in to reply

#1 Maciej 20 November 2015 - 06:56 PM

from several days we recive in log files:

092733.305  25  19   7 ERROR v7.5.5785.40849 (03-Nov-15 22:41:38.24) Run_VBS_main_catchall : W magazynie brak miejsca dla wykonania tego polecenia (not enough space)
 
   at MS.Win32.UnsafeNativeMethods.RegisterClassEx(WNDCLASSEX_D wc_d)
   at MS.Win32.HwndWrapper..ctor(Int32 classStyle, Int32 style, Int32 exStyle, Int32 x, Int32 y, Int32 width, Int32 height, String name, IntPtr parent, HwndWrapperHook[] hooks)
   at System.Windows.Threading.Dispatcher..ctor()
   at System.Windows.Threading.Dispatcher.get_CurrentDispatcher()
   at Microsoft.ClearScript.Windows.WindowsScriptEngine..ctor(String progID, String name, WindowsScriptEngineFlags flags)
   at Microsoft.ClearScript.Windows.VBScriptEngine..ctor(String progID, String name, WindowsScriptEngineFlags flags)
   at Microsoft.ClearScript.Windows.VBScriptEngine..ctor()
 
and using Process Explorer we found about 170 not closed wscript.exe
 
 
on other server with version v7.5.5669.23446 (10-Jul-15 12:01:32.48) it not happen, on other servers we haven't open wscripts.


#2 SupportTeam 20 November 2015 - 07:57 PM

This problem with WScript interpreter is the reason why we recommend that WScript approach is not used.

 

This issue occasionally occurs on systems that make intensive use of VBScript modules and regularly have a number of WScript interpreters running simultaneously.

 

We recommend that the default way of running VBScript modules is kept, and not changed to the WScript/CScript approach.

 

There are some anecdotal reports that this WScript problem occurs less on Server class systems with more memory (8GB+), but ultimately our recommendation is not to change the default way that VoiceGuide runs the VBScript modules.



#3 Maciej 20 November 2015 - 08:05 PM

Sorry, I don't understand.

 

In Juli version WScript interpreter not leaving opened vbscripts threats. Only in november version.

 

 

Can You fix it?



#4 SupportTeam 20 November 2015 - 08:27 PM

There is no difference between the November version and the July version in that area. The both start the WScript process in the same way.

 

What you are seeing is a WScript related problem.

 

The problem seems to occur occasionally on systems that make intensive use of WScript processes and regularly have a number of WScript interpreters running simultaneously.

 

Reducing the intensity at which the system runs multiple WScript processes simultaneously my reduce the occurrence of this problem.

Other system-related parameters may reduce incidence as well (more memory, faster CPU, Server version of Windows, no other high CPU/Memory using processes running on system, etc).

 

As mentioned previously, we recommend that WScript processes are not used.



#5 Maciej 23 November 2015 - 07:35 PM

Hi,

 

Problem is because VB script not closing as need. 

 

On other servers it not happen. (not this kind of problems) using Process Explorer we see no VBS threads hanging, so it's maybe windows problem.

 

As we describe in other VBS case in forum, after factory default Windows installation without updates VBS in VG working properly.

 

Suggesting not using VBS is curios. Why is available functionality when you so suggest? We need several functionalities like call recording, PBX functions as Bridge connect and disconnect exactly declared channels and others. 

 

How to reach this without VBS?



#6 SupportTeam 23 November 2015 - 08:34 PM

 

Problem is because VB script not closing as need.

 

It is the Wscript.exe that is not closing. If you look though the traces you will see that the VBScript ran by Wscript is actually completing - but WScript is not losing afterwards.

 

 

Suggesting not using VBS is curios.

 

It was never suggested not use 'Run VBScript' modules.

 

We recommend to not change the default way that VoiceGuide runs the VBScript modules, so the default way of running VBScript modules is kept, and not changed to the WScript/CScript approach.

 

 

ie. the VG.INI setting "Engine" in section [moduleRunScript] is not modified.

 

If the system is using WScript.exe to process 'Run VBScript' modules then that "Engine" entry would have been modified on this system after installation.



#7 Maciej 24 November 2015 - 07:26 PM

After restart windows to factory settings without any updates VB scripts processes not hanging up.



#8 SupportTeam 24 November 2015 - 07:45 PM

The WScript issue is not related to any Windows updates as far as we can tell. It manifested itself on various versions of Windows for may years.