I have recently inspected a small network who has been having issues with an application written in V9.
Intermittently the application would freeze, throwing up a script message.
If the operator closed the application and then reopened it, the script would work as expected.
After all if you click a button and the script doesn�t execute and throws out an error message that hints at lack of resources. Closing the V9 application and then reopening it and clicking the same button sees the script work as intended. That tells me that it must be an environmental factor.
Initially there wasn�t the recommended ram in either the server or the workstations, and we thought this was where the fault lay.
However, even when upgrading the 2003 Server to 4 gig and putting 2 gig of ram in everyone�s machine, the problem still persisted.
The operators were understandably becoming increasingly frustrated.
I subsequently did a site visit and using standard diagnostic tools here is what I found.
In a six user network, the workstations were running a mixture of XP SP2 and SP3.
Some machines had more than one Anti Virus software running. Whilst everyone had AVG, one workstation was also running Symantec Antivirus, and another had remnants of Spyware Protection from AOL.
Running a Registry Checker revealed in excess of 1200 issues on each and every workstation. The lowest being 1247, the highest 1690 with an average of around 1400.
Further tests revealed in excess of over 200 megabytes of temp files on each workstation. The highest had 943 megabytes of temp files with the others having a range between 240 to 477 megabytes.
Because the V9 application froze the client�s frustration was vented towards Alpha and ultimately ourselves because we built it.
And this would happen on different workstations at different times.
The V9 development engine used is the current as indeed is the runtime.
Throughout this painful process I have defended Alpha because everything told me it was the network environment rather than bugs in V9.
Would someone like to comment on my conclusion?
Intermittently the application would freeze, throwing up a script message.
If the operator closed the application and then reopened it, the script would work as expected.
After all if you click a button and the script doesn�t execute and throws out an error message that hints at lack of resources. Closing the V9 application and then reopening it and clicking the same button sees the script work as intended. That tells me that it must be an environmental factor.
Initially there wasn�t the recommended ram in either the server or the workstations, and we thought this was where the fault lay.
However, even when upgrading the 2003 Server to 4 gig and putting 2 gig of ram in everyone�s machine, the problem still persisted.
The operators were understandably becoming increasingly frustrated.
I subsequently did a site visit and using standard diagnostic tools here is what I found.
In a six user network, the workstations were running a mixture of XP SP2 and SP3.
Some machines had more than one Anti Virus software running. Whilst everyone had AVG, one workstation was also running Symantec Antivirus, and another had remnants of Spyware Protection from AOL.
Running a Registry Checker revealed in excess of 1200 issues on each and every workstation. The lowest being 1247, the highest 1690 with an average of around 1400.
Further tests revealed in excess of over 200 megabytes of temp files on each workstation. The highest had 943 megabytes of temp files with the others having a range between 240 to 477 megabytes.
Because the V9 application froze the client�s frustration was vented towards Alpha and ultimately ourselves because we built it.
And this would happen on different workstations at different times.
The V9 development engine used is the current as indeed is the runtime.
Throughout this painful process I have defended Alpha because everything told me it was the network environment rather than bugs in V9.
Would someone like to comment on my conclusion?
Comment