Weibin Sun - 2014-01-07

We have being using 7z.exe (command line) in many years starting from v5.X to recently v9.20 (7za.exe 32 bit). It has been working fine on Windows 2003 but started to fail on Windows 2008 (both 32 and 64 bit version) after ca. 8300 times executions.

7-Zip version and type (32-bit commandline)
Windows version and type (2008 32-bit and 64-bit)
CPU type (Intel Xeon X5677, ProLiant DL380 G7)
RAM size (24 GB)
Calling appplication: VBScript

I am stuck to 32-bit 7z version, because the calling application is 32 bit version running on Windows 2008 64 bit version.

I can simulate the error by creating a VBScript scheduled to run every minute.
There are consequences if this error occurs. I have experienced that WinScp won't work any longer and some of the Windows services can not be controlled any more by WMI functions.

Anybody else has the same experience and any solutions?